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>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-4.6-testing bisection] complete test-xtf-amd64-amd64-5
Date: Wed, 5 Apr 2017 18:53:00 +0200	[thread overview]
Message-ID: <1491411180.18721.7.camel@citrix.com> (raw)
In-Reply-To: <58E4B0D8020000780014CF6C@prv-mh.provo.novell.com>


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

On Wed, 2017-04-05 at 00:54 -0600, Jan Beulich wrote:
> > > > On 04.04.17 at 19:23, <dario.faggioli@citrix.com> wrote:
> > 
> > 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.
> 
> I think we could leave 4.6 alone in this regard, unless you see a
> strong need for the fix there, or unless anyone's aware of
> someone having actively encountered the problem there. 
>
I agree. And no, I'm not aware of anyone having run into the issue on
4.6.x.

> Or in
> other words - if you feel like making sure we know of all prereqs
> (and providing backports if those won't apply as is), I'd happily
> apply them, but I don't think you absolutely need to.
> 
I actually tried backporting the above commit. It's not just a matter
of cherry picking, but it's trivial. I could not test the result,
though, because I can't build the tools from 4.6 with my gcc (6.3.0),
without backporting some toolstack patches too.

I can look into which ones are needed, but not right now. So I'm going
to put this on hold.

Thanks and 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-05 16:53 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
2017-04-05  6:54     ` Jan Beulich
2017-04-05 16:53       ` Dario Faggioli [this message]

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=1491411180.18721.7.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).