[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfvUP/V2RoylwXMQm6N0Av9il/s3AKJmCkAACHV60MABY05cAAcNENn
  • Thread-topic: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough

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
hooks.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.