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] RE: [PATCH][VTD] force boot to fail if interrupt remapping c

To: Keir Fraser <keir.xen@xxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH][VTD] force boot to fail if interrupt remapping cannot be enabled when iommu=force
From: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>
Date: Thu, 28 Apr 2011 11:58:46 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc: Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 28 Apr 2011 12:00:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C9DF5CCF.16F23%keir.xen@xxxxxxxxx>
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: <987664A83D2D224EAE907B061CE93D5301C51BE9D8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C9DF5CCF.16F23%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwFNNYW4YeEKo21TgqWL8v00UgwwAAkZQZ1AAEZJhA=
Thread-topic: [PATCH][VTD] force boot to fail if interrupt remapping cannot be enabled when iommu=force
> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx]
> Sent: Thursday, April 28, 2011 10:05 AM
> On 28/04/2011 00:42, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote:
> > Force Xen boot to fail if interrupt remapping fails to enable and the
> > following are true: iommu=force is set as xen boot parameter, VT-d
> > engine HW is interrupt remapping capable, DMAR_INTR_REMAP bit is set in 
> > DMAR flags.
> > This forces iommu=force boot instances has interrupt remapping enabled
> > if HW and BIOS supports it.
> If HW and BIOS support it, why would it fail to be enabled? This doesn't look 
> like a particularly
> useful panic() path. If interrupt remapping is so important, perhaps 
> iommu=force should
> unconditionally require it, and panic in its absence regardless of platform 
> features? As it is,
> this looks like a panic that is never realistically going to trigger.

There are ways that malicious SW, running before the TXT launch of Xen, can 
alter the DMAR ACPI tables such that Xen will fail to enable interrupt 
remapping (IR).

Since not all platforms support IR, we certainly don't want to fail Xen on 
those platforms.  We simply want to ensure that if the HW does support IR that 
Xen can't be "tricked" into not using it.


Xen-devel mailing list