From: Julien Grall <julien.grall@arm.com>
To: Dario Faggioli <dfaggioli@suse.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>
Cc: "George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] dom0less + sched=null => broken in staging
Date: Tue, 13 Aug 2019 19:43:52 +0100 [thread overview]
Message-ID: <fdbf9a17-acbf-3402-6b69-d1af0193df53@arm.com> (raw)
In-Reply-To: <6f44856f428c936f9c1913f3f35196dff6044509.camel@suse.com>
On 8/13/19 6:34 PM, Dario Faggioli wrote:
> On Tue, 2019-08-13 at 17:52 +0100, Julien Grall wrote:
>> Hi Dario,
>>
> Hello!
>
>> On 8/13/19 4:27 PM, Dario Faggioli wrote:
>>> On Fri, 2019-08-09 at 11:30 -0700, Stefano Stabellini wrote:
>>>>
>>> In my (x86 and "dom0full") testbox, this seems to come from
>>> domain_unpause_by_systemcontroller(dom0) called by
>>> xen/arch/x86/setup.c:init_done(), at the very end of __start_xen().
>>>
>>> I don't know if domain construction in an ARM dom0less system works
>>> similarly, though. What we want, is someone calling either
>>> vcpu_wake()
>>> or vcpu_unpause(), after having cleared _VPF_down from pause_flags.
>>
>> Looking at create_domUs() there is a call to
>> domain_unpause_by_controller for each domUs.
>>
> Yes, I saw that. And I've seen the one done don dom0, at the end of
> xen/arch/arm/setup.c:start_xen(), as well.
>
> Also, both construct_dom0() (still from start_xen()) and
> construct_domU() (called from create_domUs()) call construct_domain(),
> which does clear_bit(_VPF_down), setting the domain to online.
>
> So, unless the flag gets cleared again, or something else happens that
> makes the vCPU(s) fail the vcpu_runnable() check in
> domain_unpause()->vcpu_wake(), I don't see why the wakeup that let the
> null scheduler start scheduling the vCPU doesn't happen... as it
> instead does on x86 or !dom0less ARM (because, as far as I've
> understood, it's only dom0less that doesn't work, it this correct?)
Yes, I quickly tried to use NULL scheduler with just dom0 and it boots.
Interestingly, I can't see the log:
(XEN) Freed 328kB init memory.
This is called as part of init_done before CPU0 goes into the idle loop.
Adding more debug, it is getting stuck when calling
domain_unpause_by_controller for dom0. Specifically vcpu_wake on dom0v0.
The loop to assign a pCPU in null_vcpu_wake() is turning into an
infinite loop. Indeed the loop is trying to pick CPU0 for dom0v0 that is
already used by dom1v0. So the problem is in pick_cpu() or the data used
by it.
It feels to me this is an affinity problem. Note that I didn't request
to pin dom0 vCPUs.
Cheers,
--
Julien Grall
_______________________________________________
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-13 18:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 18:22 [Xen-devel] dom0less + sched=null => broken in staging Stefano Stabellini
2019-08-08 8:04 ` George Dunlap
2019-08-08 20:44 ` Stefano Stabellini
2019-08-09 7:40 ` Dario Faggioli
2019-08-09 17:57 ` Dario Faggioli
2019-08-09 18:30 ` Stefano Stabellini
2019-08-13 15:27 ` Dario Faggioli
2019-08-13 16:52 ` Julien Grall
2019-08-13 17:34 ` Dario Faggioli
2019-08-13 18:43 ` Julien Grall [this message]
2019-08-13 22:26 ` Julien Grall
2019-08-13 22:34 ` Dario Faggioli
2019-08-13 23:07 ` Julien Grall
2019-08-13 21:14 ` Stefano Stabellini
2019-08-14 2:04 ` Dario Faggioli
2019-08-14 16:27 ` Stefano Stabellini
2019-08-14 17:35 ` Dario Faggioli
2019-08-21 10:33 ` Dario Faggioli
2019-08-24 1:16 ` Stefano Stabellini
2019-09-11 13:53 ` Dario Faggioli
2019-09-25 15:19 ` Julien Grall
2019-09-25 15:34 ` Dario Faggioli
2019-09-25 15:39 ` Julien Grall
2019-09-25 15:41 ` Jürgen Groß
2019-10-28 5:35 ` Dario Faggioli
2019-10-28 18:40 ` Stefano Stabellini
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=fdbf9a17-acbf-3402-6b69-d1af0193df53@arm.com \
--to=julien.grall@arm.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dfaggioli@suse.com \
--cc=sstabellini@kernel.org \
--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).