WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
From: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Date: Wed, 19 Sep 2007 08:26:10 +0200
Cc: Guy Zana <guy@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Delivery-date: Tue, 18 Sep 2007 23:27:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3167F31.DB03%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <13A2F7DE1BAEA345A61DD40F303ED7A67C542B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3167F31.DB03%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Wed, Sep 19, 2007 at 07:24:33AM +0100, Keir Fraser wrote:
> 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.

Since VT-d has a per BDF translation table, why does enabling
translation for some BDF's require enabling it for everyone else too?

Cheers,
Muli

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