From: Stefano Stabellini <sstabellini@kernel.org>
To: George Dunlap <george.dunlap@citrix.com>
Cc: George.Dunlap@eu.citrix.com, xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
dfaggioli@suse.com
Subject: Re: [Xen-devel] dom0less + sched=null => broken in staging
Date: Thu, 8 Aug 2019 13:44:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1908081342390.22196@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <35a1ab11-5bba-866c-40fc-6366c65317f0@citrix.com>
On Thu, 8 Aug 2019, George Dunlap wrote:
> On 8/7/19 7:22 PM, Stefano Stabellini wrote:
> > Hi Dario, George,
> >
> > Dom0less with sched=null is broken on staging, it simply hangs soon
> > after Xen is finished loading things. My impression is that vcpus are
> > not actually started. I did a git bisection and it pointed to:
> >
> > commit d545f1d6c2519a183ed631cfca7aff0baf29fde5 (refs/bisect/bad)
> > Author: Dario Faggioli <dfaggioli@suse.com>
> > Date: Mon Aug 5 11:50:55 2019 +0100
> >
> > xen: sched: deal with vCPUs being or becoming online or offline
>
> That's Dario's patch -- Dario, can you take a look?
>
> Stefano, how urgent is it for things to work for you -- i.e., at what
> point do you want to consider reverting the patch?
Of course, we cannot make a release with this issue. I can live with it
for now because I have a revert for
d545f1d6c2519a183ed631cfca7aff0baf29fde5 at the top of all my working
branches and the production branches at Xilinx are based on the last
release.
_______________________________________________
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-08 20: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 [this message]
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
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=alpine.DEB.2.21.1908081342390.22196@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=dfaggioli@suse.com \
--cc=george.dunlap@citrix.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).