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

[Xen-devel] Cpupools and pdata_alloc

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Mon, 10 May 2010 12:47:51 -0500
  • Cc:
  • Delivery-date: Mon, 10 May 2010 10:48:28 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=VHhzkXMkOYa/oXfL2SQ3WzWiGBpEKw5Nl1hXcug8r99EjX9OF5kox50Gk3O4Sw95X4 rIxPCgEPuessWf85z+lR1nIi/PJkxr5OadY6nlVxuz+QaXYiiceCjQSXN56F+AwWnfBg 3a/Y0L9XPcW9qBY8u9mG5dz6Y7D3oD+eyNjBk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

It appears that in the new cpupools code:
* pdata_allocate is called from alloc_vcpu() with that cpu for the first time.
* this happens usually when dom0's cpus are allocated, as it cycles
through all of the cpus

This seems a bit strange to me.  Wouldn't it make more sense to pass,
or to make available, a cpumask of the cpus in a pool to the init

Also, is there documentation of the cpupool lifecycle anywhere, to
help scheduler writers understand what's going on?


Xen-devel mailing list



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