xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: osstest-admin@xenproject.org
Subject: Re: [xen-4.6-testing bisection] complete test-xtf-amd64-amd64-5
Date: Tue, 4 Apr 2017 19:23:45 +0200	[thread overview]
Message-ID: <1491326625.18721.3.camel@citrix.com> (raw)
In-Reply-To: <58E21DBB020000780014BE92@prv-mh.provo.novell.com>


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

On Mon, 2017-04-03 at 02:02 -0600, Jan Beulich wrote:
> > > > On 03.04.17 at 00:44, <osstest-admin@xenproject.org> wrote:
> >   commit 7ff6d9fc19ef88d2ca3304a312c0e8a46b61f546
> >   Author: Dario Faggioli <dario.faggioli@citrix.com>
> >   Date:   Fri Mar 31 09:03:32 2017 +0200
> >   
> >       xen: sched: don't call hooks of the wrong scheduler via
> > VCPU2OP
> 
> I must have completely screwed up on this backport, so I've simply
> reverted it for now. I didn't look closely yet whether this is some
> trivial oversight of mine, or whether perhaps it shouldn't have been
> backported that far back in the first place.
> 
I had a look. The backport looks fine in itself to me.

If I'm not mistaken, this is not in staging-4.6:

 f3d47501db2b7bb8dfd6a3c9710b7aff4b1fc55b
 xen: fix a (latent) cpupool-related race during domain destroy

I can't be positive this is what's missing, but it's my best guess. :-)

I also haven't tried backporting it, but I'm happy to. Let me know if I
should.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

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

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

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

  reply	other threads:[~2017-04-04 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02 22:44 [xen-4.6-testing bisection] complete test-xtf-amd64-amd64-5 osstest service owner
2017-04-03  8:02 ` Jan Beulich
2017-04-04 17:23   ` Dario Faggioli [this message]
2017-04-05  6:54     ` Jan Beulich
2017-04-05 16:53       ` Dario Faggioli

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=1491326625.18721.3.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=osstest-admin@xenproject.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).