From: George Dunlap <dunlapg@umich.edu>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Dario Faggioli <dfaggioli@suse.com>
Subject: Re: [Xen-devel] [PATCH 1/3] xen/sched: populate cpupool0 only after all cpus are up
Date: Wed, 14 Aug 2019 17:15:11 +0100 [thread overview]
Message-ID: <CAFLBxZa=ymiPSQP+Z8_3+6UFnt1eu15Wv5Km-xpShwB=Mpx0MA@mail.gmail.com> (raw)
In-Reply-To: <20190802130730.15942-2-jgross@suse.com>
On Fri, Aug 2, 2019 at 2:08 PM Juergen Gross <jgross@suse.com> wrote:
>
> With core or socket scheduling we need to know the number of siblings
> per scheduling unit before we can setup the scheduler properly. In
> order to prepare that do cpupool0 population only after all cpus are
> up.
>
> With that in place there is no need to create cpupool0 earlier, so
> do that just before assigning the cpus. Initialize free cpus with all
> online cpus at that time in order to be able to add the cpu notifier
> late, too.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> V1: new patch
> ---
> xen/common/cpupool.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/xen/common/cpupool.c b/xen/common/cpupool.c
> index f90e496eda..caea5bd8b3 100644
> --- a/xen/common/cpupool.c
> +++ b/xen/common/cpupool.c
> @@ -762,18 +762,28 @@ static struct notifier_block cpu_nfb = {
> .notifier_call = cpu_callback
> };
>
> -static int __init cpupool_presmp_init(void)
> +static int __init cpupool_init(void)
> {
> + unsigned int cpu;
> int err;
> - void *cpu = (void *)(long)smp_processor_id();
> +
> cpupool0 = cpupool_create(0, 0, &err);
> BUG_ON(cpupool0 == NULL);
> cpupool_put(cpupool0);
> - cpu_callback(&cpu_nfb, CPU_ONLINE, cpu);
> register_cpu_notifier(&cpu_nfb);
> +
> + spin_lock(&cpupool_lock);
> +
> + cpumask_copy(&cpupool_free_cpus, &cpu_online_map);
> +
> + for_each_cpu ( cpu, &cpupool_free_cpus )
> + cpupool_assign_cpu_locked(cpupool0, cpu);
> +
> + spin_unlock(&cpupool_lock);
Just to make sure I understand what's happening here -- cpu_callback()
now won't get called with CPU_ONLINE early in the boot process; but it
will still be called with CPU_ONLINE in other circumstances (e.g.,
hot-plug / suspend / whatever)?
If not, then it's probably best to remove CPU_ONLINE from that switch statement.
Sorry that's an overly-basic question; I don't have a good picture for
the cpu state machine.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-14 16:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 13:07 [Xen-devel] [PATCH 0/3] xen/sched: use new idle scheduler for free cpus Juergen Gross
2019-08-02 13:07 ` [Xen-devel] [PATCH 1/3] xen/sched: populate cpupool0 only after all cpus are up Juergen Gross
2019-08-13 16:07 ` Dario Faggioli
2019-08-26 8:35 ` Juergen Gross
2019-08-14 16:15 ` George Dunlap [this message]
2019-08-14 16:58 ` Dario Faggioli
2019-08-02 13:07 ` [Xen-devel] [PATCH 2/3] xen/sched: remove cpu from pool0 before removing it Juergen Gross
2019-08-13 17:11 ` Dario Faggioli
2019-08-26 8:37 ` Juergen Gross
2019-08-02 13:07 ` [Xen-devel] [PATCH 3/3] xen/sched: add minimalistic idle scheduler for free cpus Juergen Gross
2019-08-13 17:07 ` Dario Faggioli
2019-08-09 9:47 ` [Xen-devel] [PATCH 0/3] xen/sched: use new " Juergen Gross
2019-08-09 10:35 ` Dario Faggioli
2019-08-13 15:51 ` Dario Faggioli
2019-08-26 8:34 ` 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='CAFLBxZa=ymiPSQP+Z8_3+6UFnt1eu15Wv5Km-xpShwB=Mpx0MA@mail.gmail.com' \
--to=dunlapg@umich.edu \
--cc=dfaggioli@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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).