WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Cpupools and pdata_alloc

To: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Cpupools and pdata_alloc
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=tF2APtK2nGA9ZebLaxAEGXophFd7gjJjdbz/ROl/uJ0=; b=S4p7Z9S9PraD9hQq2rPwIljq/SjOR9MV1V+xnS6c1R2qrDQNLd86s6UzvWAgYZuLva gT7h4AE5sLB/3Val6kKY82JZ8Od9d2Xk6spYv31NydQn4I47Z4ncG8OJnNtpDRnP79R8 yU02ZsVugmFmPljpBvqH3zguDNXgLnhOjzPcY=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
function?

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

 -George

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

<Prev in Thread] Current Thread [Next in Thread>