From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Fri, 06 Dec 2013 14:58:45 +0000 [thread overview]
Message-ID: <52A1F435020000780010AF06@nat28.tlf.novell.com> (raw)
In-Reply-To: <52A1CC06.30508@eu.citrix.com>
>>> On 06.12.13 at 14:07, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> On 12/06/2013 09:07 AM, Jan Beulich wrote:
>>>>> On 05.12.13 at 17:34, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>>> On 05/12/13 16:09, George Dunlap wrote:
>>>> * Supposed regression from a3513737 ("x86: allow guest to set/clear
>>>> > MSI-X mask bit (try 2)"), as per
>>>> > http://lists.xenproject.org/archives/html/xen-devel/2013-09/msg01589.html.
>>> There was no followup on that, so is possibly stale.
>>>
>>> There has been a more recent commit
>>> (http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=74fd0036deb585a139b
>>> 63b26db025805ecedc37a)
>>> which fixes up a Xen-Qemu communication error when unmasking MSI-X
>>> interrupts which might be related?
>> That's not just related, that _is_ the one fixing the regression.
>
> So I can mark this one as fixed then?
Yes.
Jan
next prev parent reply other threads:[~2013-12-06 14:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34 ` Wei Liu
2013-12-05 16:39 ` George Dunlap
2013-12-05 16:48 ` Wei Liu
2013-12-05 16:59 ` Ian Campbell
2013-12-05 17:06 ` Wei Liu
2013-12-05 17:16 ` Ian Campbell
2013-12-05 17:34 ` Wei Liu
2013-12-05 17:53 ` George Dunlap
2013-12-05 18:03 ` Wei Liu
2013-12-06 9:27 ` Ian Campbell
2013-12-06 10:51 ` Wei Liu
2013-12-05 16:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41 ` George Dunlap
2013-12-05 16:42 ` Roger Pau Monné
2013-12-05 16:51 ` George Dunlap
2013-12-05 17:01 ` Lars Kurth
2013-12-05 17:04 ` George Dunlap
2013-12-05 20:06 ` Russell Pavlicek
2013-12-05 23:54 ` Sander Eikelenboom
2013-12-06 9:39 ` Lars Kurth
2013-12-06 12:14 ` George Dunlap
2013-12-05 16:59 ` David Vrabel
2013-12-05 17:05 ` George Dunlap
2013-12-05 17:40 ` Dario Faggioli
2013-12-05 17:07 ` George Dunlap
2013-12-05 17:01 ` Olaf Hering
2013-12-05 17:06 ` David Vrabel
2013-12-05 17:32 ` Dario Faggioli
2013-12-06 13:30 ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper
2013-12-06 9:07 ` Jan Beulich
2013-12-06 13:07 ` George Dunlap
2013-12-06 14:58 ` Jan Beulich [this message]
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50 ` Lars Kurth
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=52A1F435020000780010AF06@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--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 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.