From: Stefano Stabellini <sstabellini@kernel.org>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: "George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] dom0less + sched=null => broken in staging
Date: Fri, 23 Aug 2019 18:16:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1908231722430.26226@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <197c435e78f47b0deb376493911abdc0922863b4.camel@suse.com>
On Wed, 21 Aug 2019, Dario Faggioli wrote:
> On Wed, 2019-08-14 at 19:35 +0200, Dario Faggioli wrote:
> > On Wed, 2019-08-14 at 09:27 -0700, Stefano Stabellini wrote:
> > > On Wed, 14 Aug 2019, Dario Faggioli wrote:
> > > > On Tue, 2019-08-13 at 14:14 -0700, Stefano Stabellini wrote:
> > > > Now, while staring at the code of that loop, I've seen that
> > > > pick_cpu()
> > > > may mess up with the scratch cpumask for the CPU, which I don't
> > > > think
> > > > is a good thing.
> > > >
> > > > So, can you also try this third debug-patch?
> > >
> > > Yep, see attached
> > >
> > Ok, thanks again. So, cpumask_scratch() being mishandled was part of
> > the problem, but not the root-cause.
> >
> > Well, it was worth a shot. :-P
> >
> > I think we need to get rid of the loop in which we're stuck.
> >
> Hey, Stefano, Julien,
>
> Here's another patch.
>
> Rather than a debug patch, this is rather an actual "proposed
> solution".
>
> Can you give it a go? If it works, I'll spin it as a proper patch.
Yes, this seems to solve the problem, thank you!
_______________________________________________
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-24 1:17 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
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 [this message]
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.1908231722430.26226@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=dfaggioli@suse.com \
--cc=julien.grall@arm.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).