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


Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 19 Sep 2007 07:24:33 +0100
Cc: Guy Zana <guy@xxxxxxxxxxxx>
Delivery-date: Tue, 18 Sep 2007 23:20:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <13A2F7DE1BAEA345A61DD40F303ED7A67C542B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfvUP/V2RoylwXMQm6N0Av9il/s3AKJmCkAACHV60MABY05cAAcNENn
Thread-topic: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
User-agent: Microsoft-Entourage/
On 18/9/07 21:41, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote:

> I was checking for vtd_enabled in common/page_alloc.c.  What is the
> proper place to define this?   I will defer submission of common changes
> until we reach an agreement on this.

Since this initial patchset is about translation (for HVM guests) rather
than security, you could have a global iommu table for all PV guests that
1:1 maps everything. That can be set up at start-of-day with no common-code

 -- Keir

Xen-devel mailing list