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 17:52:48 +0100 [thread overview]
Message-ID: <bfcd8473-a73b-932c-3cdf-7ad41c14e4c0@arm.com> (raw)
In-Reply-To: <6bc0e21d79c4f02ad89c94fa732a32a57bdc8521.camel@suse.com>
Hi Dario,
On 8/13/19 4:27 PM, Dario Faggioli wrote:
> On Fri, 2019-08-09 at 11:30 -0700, Stefano Stabellini wrote:
>> On Fri, 9 Aug 2019, Dario Faggioli wrote:
>>> Can you help me with this, e.g., by providing some more info and,
>>> if
>>> possible, logs?
>>
>> I am attaching the logs.
>>
> Thanks!
>
>> Interestingly, I get a bunch of:
>>
>> (XEN) *** LOADING DOMU cpus=1 memory=40000KB ***
>> (XEN) sched_null.c:458: Not inserting d2v0 (not online!)
>>
>> Maybe we are missing a call to online the vcpus somewhere in
>> xen/arch/arm/domain_build.c:construct_domain?
>>
> Actually, those lines are normal, because vCPUs are created offline.
> (see the set_bit(_VPF_down) in vcpu_create()).
>
> The problem is why aren't they coming up. Basically, you're missing a
> call to vcpu_wake().
>
> 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.
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 16:53 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 [this message]
2019-08-13 17:34 ` Dario Faggioli
2019-08-13 18:43 ` Julien Grall
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=bfcd8473-a73b-932c-3cdf-7ad41c14e4c0@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).