This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH V3] AMD IOMMU: Fix an interrupt remapping issue

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] [PATCH V3] AMD IOMMU: Fix an interrupt remapping issue
From: Wei Wang2 <wei.wang2@xxxxxxx>
Date: Mon, 11 Apr 2011 12:31:23 +0200
Cc: "Ostrovsky, Boris" <Boris.Ostrovsky@xxxxxxx>, "Huang2, Wei" <Wei.Huang2@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 Apr 2011 03:34:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DA2C89A020000780003AD92@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201104081335.36718.wei.wang2@xxxxxxx> <201104081852.20738.wei.wang2@xxxxxxx> <4DA2C89A020000780003AD92@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 20070904.708012)
This patch is the latest. Should have addressed all of your concerns. Please 
take a look.

Signed-off-by: Wei Wang <wei.wang2@xxxxxxx>

On Monday 11 April 2011 09:23:38 Jan Beulich wrote:
> >>> On 08.04.11 at 18:52, Wei Wang2 <wei.wang2@xxxxxxx> wrote:
> >
> > Jan, How dose this one look like to you?
> Much better, but still not quite there: The unmasking must happen
> *after* the writing of the upper half (if that's what is being modified).
> You could also skip the unmasking altogether if saved_mask == 1.
> And if you start using __io_apic_write() (which I find very desirable)
> is there a reason not to use it (and __io_apic_read()) in all of the
> other places you touch anyway, too?
> Jan

Attachment: fix_intremap_v3.patch
Description: fix_intremap_v3.patch

Xen-devel mailing list