From: George Dunlap <George.Dunlap@eu.citrix.com>
To: xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>
Subject: Cpupools and pdata_alloc
Date: Mon, 10 May 2010 12:47:51 -0500 [thread overview]
Message-ID: <AANLkTin3dC9sCDP1-zwKog6BZtwaHAmkt53NqwAZtiNw@mail.gmail.com> (raw)
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
next reply other threads:[~2010-05-10 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 17:47 George Dunlap [this message]
2010-05-11 4:48 ` Cpupools and pdata_alloc Juergen Gross
2010-05-11 17:25 ` George Dunlap
2010-05-11 18:41 ` Keir Fraser
2010-05-11 18:52 ` George Dunlap
2010-05-11 18:55 ` Keir Fraser
2010-05-12 4:52 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin3dC9sCDP1-zwKog6BZtwaHAmkt53NqwAZtiNw@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).