[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] tmem and construct_dom0 memory allocation race


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Fri, 18 Jun 2010 16:10:06 -0700
  • Delivery-date: Fri, 18 Jun 2010 16:11:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=w9V2L4Oy77QIJny1LbcY9tHsQHkiwWAptiyjmlULCm6bAkfzil/0H0pQJXpPdqD5Re u/2bx4TAzRv3lVD45xRYNzzH/kgyvgdNGVE/gzcO1ibJfPDvagHX5ozdNoJqwOS371JM N/h3tgeB3Bx5WD2LWNASQ7sQlvGv6cC4N/Ytw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

tmem could cause Dom0 allocation to fail with error "Not enough RAM
for DOM0 reservation", particularly when used without dom0_mem option.

Following is the sequence :
- init_tmem allocates a set of pages and sets up dstmem and workmem to
alloc pages in MP case (with cpu notifiers)
- construct_dom0 estimates nr_pages by calling avail_domheap_pages
- On other CPUs, tmem cpu_notifier gets called and allocates pages
from domheap, making the construct_dom0's estimate stale.
- construct_dom0 fails

tmem=off or dom0_mem=xxx both solve the problem for now.

-dulloor

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.