From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.4 development update: RC0 imminent Date: Fri, 06 Dec 2013 09:07:45 +0000 Message-ID: <52A1A1F1020000780010AC21@nat28.tlf.novell.com> References: <52A0AAF9.9080309@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VorO1-0007d7-Ci for xen-devel@lists.xenproject.org; Fri, 06 Dec 2013 09:07:49 +0000 In-Reply-To: <52A0AAF9.9080309@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , George Dunlap Cc: xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 05.12.13 at 17:34, Andrew Cooper 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. Jan