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] Can I expose a pci device to HVM domU?

To: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Can I expose a pci device to HVM domU?
From: Daniel Stodden <stodden@xxxxxxxxxx>
Date: Tue, 19 Feb 2008 23:01:32 +0100
Delivery-date: Tue, 19 Feb 2008 14:02:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <78C9135A3D2ECE4B8162EBDCE82CAD77030E2C00@nekter>
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>
Organization: Fakultät für Informatik I10, Technische Universität München
References: <6bc632150802191238v19371a70ha60ee5950c027c06@xxxxxxxxxxxxxx> <78C9135A3D2ECE4B8162EBDCE82CAD77030E2B83@nekter> <1203456947.5870.2.camel@xxxxxxxxxxxxxxxxxxxx> <78C9135A3D2ECE4B8162EBDCE82CAD77030E2C00@nekter>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2008-02-19 at 16:51 -0500, Caitlin Bestler wrote:
> > > >
> > > > PS:- NIC Is does not have Intel's VT-d.
> > > >
> > >
> > > If the Guest is HVM, how would it know how to give usable
> > > DMA addresses to the NIC? (Whether it should be trusted to
> > > in the absence of an Address Translation Service is the next
> > > question, but first is whether it could even do it at all).
> > >
> > > A PV Guest, by contrast, would know the distinction between
> > > GPAs and SPAs (not that it makes it any more trustworthy).
> > 
> > VT-d / IO-MMUs fixes that.
> > 
> If you interpret the problem as being that the NIC is not
> itself aware of VT-d (or other IOMMU), but that there is an
> IOMMU active, then that would be true.
> 
> My interpretation of "does not have VT-d" is that there is
> no IOMMU active in the target platform at all.

It was meant as a rather general reply (I thought yours was as well). I
simply overlooked the no-VTd statement above. Sorry, you're certainly
right.

greetings,
daniel

-- 
Daniel Stodden
LRR     -      Lehrstuhl für Rechnertechnik und Rechnerorganisation
Institut für Informatik der TU München             D-85748 Garching
http://www.lrr.in.tum.de/~stodden         mailto:stodden@xxxxxxxxxx
PGP Fingerprint: F5A4 1575 4C56 E26A 0B33  3D80 457E 82AE B0D8 735B



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