From: "Jürgen Groß" <jgross@suse.com>
To: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
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>
Subject: Re: [Xen-devel] dom0less + sched=null => broken in staging
Date: Wed, 25 Sep 2019 17:41:22 +0200 [thread overview]
Message-ID: <2cae8d55-beb6-1f39-a4d4-7b7a36cec0c1@suse.com> (raw)
In-Reply-To: <bf8bafc2-01b4-2847-56f1-cd1121d181a8@arm.com>
On 25.09.19 17:39, Julien Grall wrote:
> Hi,
>
> On 25/09/2019 16:34, Dario Faggioli wrote:
>> On Wed, 2019-09-25 at 16:19 +0100, Julien Grall wrote:
>>> (+Juergen)
>>>
>>> Hi Dario,
>>>
>> Hi,
>>
>>> On 11/09/2019 14:53, Dario Faggioli wrote:
>>>> On Fri, 2019-08-23 at 18:16 -0700, Stefano Stabellini wrote:
>>>> Ok, thanks again for testing, and good to know.
>>>>
>>>> I'm still catching up after vacations, and I'm traveling next week.
>>>> But
>>>> I'll submit a proper patch as soon as I find time.
>>>
>>> Just wanted to follow-up on this. Do you have an update for the fix?
>>>
>>> I would rather not want to see Xen 4.13 released with this. So I have
>>> CCed
>>> Juergen to mark it as a blocker.
>>>
>> Yep, I spoke with Juergen about this last week (in person). Basically,
>> since we decided to try to push core-scheduling in, I'm focusing on
>> that series right now.
>>
>> In fact, this fix can go in after code-freeze as well, since it's,
>> well, a fix. :-)
>>
>> After code freeze, I'll prepare and send the patch (and if core-
>> scheduling would have gone in, I'll rebase it on top of that, of
>> course).
>
> Make sense. I just wanted to make sure this is tracked by Juergen :).
It is. :-)
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-25 15:41 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
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ß [this message]
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=2cae8d55-beb6-1f39-a4d4-7b7a36cec0c1@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dfaggioli@suse.com \
--cc=julien.grall@arm.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).