xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Cpupools and pdata_alloc
Date: Tue, 11 May 2010 19:55:30 +0100	[thread overview]
Message-ID: <C80F66B2.1C1D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <AANLkTimPGdrlSU0ly9Pg6VB1izSPEvn22Sx-XVmkSsdB@mail.gmail.com>

On 11/05/2010 19:52, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:

> On Tue, May 11, 2010 at 1:41 PM, Keir Fraser <keir.fraser@eu.citrix.com>
> wrote:
>> Well, once secondary CPUs are fully up they are of course running their
>> respective idle VCPUs, so we can't call schedule_init() very late. The right
>> thing to do is dynamically allocate state as CPUs are brought online -- and
>> potentially free that state when CPUs are taken offline. Which is pretty
>> much the direction the code points in already.
> 
> Except that it's done a little indirectly, via initializing the idle
> vcpu, rather than calling something like sched_init_pcpu() when the
> cpu is brought up before creating an idle vcpu for it. :-)  Anyway,
> maybe once I get the credit2 stuff working again, I may think about
> writing a patch to clean it up a bit... mostly so that it's easier to
> follow what's going on.

Splitting it into an explicit separate call into the scheduling subsystem
would be acceptable, I think.

 -- Keir

  reply	other threads:[~2010-05-11 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 17:47 Cpupools and pdata_alloc George Dunlap
2010-05-11  4:48 ` 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 [this message]
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=C80F66B2.1C1D%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=juergen.gross@ts.fujitsu.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).