xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
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>
Subject: Re: [Xen-devel] dom0less + sched=null => broken in staging
Date: Wed, 11 Sep 2019 15:53:21 +0200	[thread overview]
Message-ID: <1afcf0e569f68dbfe2c79668f17e1846a7dc3a1b.camel@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1908231722430.26226@sstabellini-ThinkPad-T480s>


[-- Attachment #1.1: Type: text/plain, Size: 860 bytes --]

On Fri, 2019-08-23 at 18:16 -0700, Stefano Stabellini wrote:
> On Wed, 21 Aug 2019, Dario Faggioli wrote:
> > 
> > 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!
> 
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.

Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-09-11 13: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
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 [this message]
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=1afcf0e569f68dbfe2c79668f17e1846a7dc3a1b.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=George.Dunlap@eu.citrix.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).