From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Bastian Blank <waldi@debian.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 13:40:24 -0700 [thread overview]
Message-ID: <4BB3B338.50000@goop.org> (raw)
In-Reply-To: <C7D95069.F5E4%keir.fraser@eu.citrix.com>
On 03/31/2010 11:18 AM, Keir Fraser wrote:
> Ah right. Well, looks a bit scary this close to release and not clear to me
> that it's a regression. I suggest re-submit to xen-devel for inclusion in
> xen-unstable and possible backport for 4.0.1.
>
I think it's fairly safe. From a quick poke about, it appears to only
affect guests which are using PHYSDEVOP_setup_gsi, which is only new
2.6.32+-based ones.
J
next prev parent reply other threads:[~2010-03-31 20:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54 ` Keir Fraser
2010-03-31 11:00 ` Joanna Rutkowska
2010-03-31 11:13 ` Keir Fraser
2010-03-31 12:38 ` Ian Pratt
2010-03-31 14:20 ` Dan Magenheimer
2010-03-31 14:32 ` Keir Fraser
2010-03-31 14:44 ` Ian Pratt
2010-03-31 19:55 ` Grant McWilliams
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09 ` Keir Fraser
2010-03-31 15:44 ` Bastian Blank
2010-03-31 16:38 ` Keir Fraser
2010-03-31 18:03 ` Konrad Rzeszutek Wilk
2010-03-31 18:18 ` Keir Fraser
2010-03-31 20:40 ` Jeremy Fitzhardinge [this message]
2010-03-31 19:10 ` Konrad Rzeszutek Wilk
2010-03-31 19:33 ` Keir Fraser
2010-03-31 19:52 ` Konrad Rzeszutek Wilk
2010-03-31 20:07 ` Keir Fraser
2010-03-31 21:07 ` Konrad Rzeszutek Wilk
2010-05-19 12:10 ` Keir Fraser
2010-05-26 15:02 ` Konrad Rzeszutek Wilk
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=4BB3B338.50000@goop.org \
--to=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=waldi@debian.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.