From: Keir Fraser <keir.xen@gmail.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Subject: Re: Xen 4.3 development update RC2 imminent
Date: Mon, 20 May 2013 18:12:47 +0100 [thread overview]
Message-ID: <CDC0181F.5348C%keir.xen@gmail.com> (raw)
In-Reply-To: <CAFLBxZb5vpwsQAcYhm_zbt582+ec6mw_0TSkagXSYTEne6RQ8w@mail.gmail.com>
On 20/05/2013 11:36, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
>> * Windows 2003 fails to install in Xen-unstable tip
>>> Narrowed down to c/s 2fe82ac11fd078485388fe7c5e8bc3b6ac9185b0
>> owner: Jan Beulich
>> status: Patches posted
>
> Jan,
>
> Given that Keir hasn't weighed in on this, and you are the RTC
> maintainer, can you please make an executive decision and check in a
> fix of some kind -- either reverting RTC or applying the recent patch
> series fixes?
>
> Whatever the solution is we need to start to get it tested as early as
> possible.
I'm not strongly opinionated on this one, but agree that either way it has
to be before RC2. I suspect that either way, revert or push forward with
more patches, a bunch of somewhat complex code gets churned and it's late to
be doing that, but unavoidable.
-- Keir
>> * XSA-46 regression in PV pass-through?
>>> Seems to be a xend issue; therefore not a 4.3 blocker
>> owner: Jan Beulich
>> status: patch posted (libxc enforces 1:1 mapping of pirqs)
>
> Is your 1:1 pirq mapping patch suitable for 4.3, do you think?
>
> -George
next prev parent reply other threads:[~2013-05-20 17:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 10:33 Xen 4.3 development update RC2 imminent George Dunlap
2013-05-20 10:36 ` George Dunlap
2013-05-20 17:12 ` Keir Fraser [this message]
2013-05-21 8:13 ` Tim Deegan
2013-05-21 10:22 ` Jan Beulich
2013-05-21 8:19 ` Jan Beulich
2013-05-21 8:22 ` George Dunlap
2013-05-21 8:25 ` Jan Beulich
2013-05-20 10:51 ` Wei Liu
2013-05-20 11:09 ` George Dunlap
2013-05-20 11:16 ` Ian Campbell
2013-05-20 11:32 ` George Dunlap
2013-05-20 11:46 ` Ian Campbell
2013-05-20 13:42 ` George Dunlap
2013-05-20 11:15 ` Ian Campbell
2013-05-20 11:22 ` George Dunlap
2013-05-20 11:26 ` Ian Campbell
2013-05-20 11:28 ` George Dunlap
2013-05-20 11:48 ` Ian Campbell
2013-05-21 14:06 ` Anthony PERARD
2013-05-21 14:31 ` Andrew Cooper
2013-05-21 14:49 ` George Dunlap
2013-05-21 14:55 ` Jan Beulich
2013-05-21 14:58 ` Andrew Cooper
2013-05-21 15:07 ` Jan Beulich
2013-05-21 16:13 ` George Dunlap
2013-05-21 16:16 ` George Dunlap
2013-05-22 12:49 ` Fabio Fantoni
2013-05-22 12:58 ` Andrew Cooper
2013-05-22 15:05 ` George Dunlap
2013-05-22 16:30 ` Pasi Kärkkäinen
2013-05-22 16:54 ` George Dunlap
2013-05-23 7:39 ` Jan Beulich
2013-05-23 10:36 ` Fabio Fantoni
2013-05-23 10:39 ` Andrew Cooper
2013-05-23 10:54 ` George Dunlap
2013-05-23 14:17 ` Fabio Fantoni
2013-05-23 14:26 ` George Dunlap
2013-05-23 14:35 ` George Dunlap
2013-05-23 14:58 ` Fabio Fantoni
2013-05-23 15:10 ` Pasi Kärkkäinen
2013-05-23 16:10 ` George Dunlap
2013-05-23 16:07 ` George Dunlap
2013-05-24 13:56 ` Fabio Fantoni
2013-05-24 13:59 ` George Dunlap
2013-05-24 14:53 ` Fabio Fantoni
2013-05-24 15:52 ` George Dunlap
2013-05-23 14:32 ` George Dunlap
2013-05-23 10:48 ` Jan Beulich
2013-05-23 10:31 ` Fabio Fantoni
2013-05-23 14:01 ` Pasi Kärkkäinen
2013-05-22 12:48 ` Fabio Fantoni
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=CDC0181F.5348C%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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.