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-users

Re: [Xen-users] IOMMU Domain for Dom0

To: Todd Deshane <todd.deshane@xxxxxxx>
Subject: Re: [Xen-users] IOMMU Domain for Dom0
From: Alex Merritt <merritt.alex@xxxxxxxxx>
Date: Thu, 23 Jun 2011 09:47:39 -0600
Cc: sploving <sploving1@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jun 2011 08:49:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=w4vniNid290fts+82PDZblhe+p0ljQvvd7odVBzP+wg=; b=svPgwX5337jQe7rmvCO6wVTSMU5GYj/JreW7dTybTfHaoUSIykzG9gcH81HEEPeO9Y ObnbU70pDbxO0FhFfE3UxuXcK2fV1okW/8M+eyEn4Kyh/aAcWRY+O9+mKm/so4tlLVX6 63wj60KHyw1hdTYS5HTHARZWunu8V+vtrbGm0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=N/STD8EUg5Kf6cT9DsdB3VZ6c+sXqmvw0kDhvb0A3vEJytrUXLkbHXYLQ2s9UnyGzw mdTkgs7Ke5VRcCEkZdAYnw+uSIFqMNaozRyc4hLOVNzumklYDCkvAgGvluOBna/IOrbW 8AlbpseERGEa9fv0GAFfs9/N0NjjFtICdhftk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTin7riOpwoS5=QTof45UVFxAD24wJA@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTimZFPCst7uZNgBwJ++nm9Wzk31Peg@xxxxxxxxxxxxxx> <a96be2c.199e9.130b64eafea.Coremail.sploving1@xxxxxxx> <BANLkTin9i+dOHdTT+6vEF7bR95goESY-GA@xxxxxxxxxxxxxx> <BANLkTin7riOpwoS5=QTof45UVFxAD24wJA@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Jun 22, 2011 at 21:48, Todd Deshane <todd.deshane@xxxxxxx> wrote:
> On Wed, Jun 22, 2011 at 1:20 PM, Alex Merritt <merritt.alex@xxxxxxxxx> wrote:
>> Hi,
>>
>> 2011/6/22 sploving <sploving1@xxxxxxx>:
>>>
>>>
>>>
>>> At 2011-06-21 12:17:56,"Alex Merritt" <merritt.alex@xxxxxxxxx> wrote:
>>>
>>>>Hello,
>>>>
>>>>I've been experimenting with VT-d supported PCI-passthrough in Xen for
>>>>HVM guests, and was wondering if it is possible to create an IOMMU
>>>>domain for Dom0 as well. I'm not sure if I'm asking the question
>>>>correctly, but to avoid changing a bare-metal driver for an I/O device
>>>>to translate system memory addresses used by a DMA engine, would I
>>>>instead be able to allow the IOMMU to transparently translate
>>>>addresses just like for guest VMs, but within Dom0?
>>> why put the IOMMU within Dom0? not in the driver domain?
>>
>> I'm using research code, which currently requires the management
>> extension and driver to exist within the same domain. IOMMUs are meant
>> for guest VMs as far as I can tell. They can be used as driver
>> domains, too, but (unless I'm mistaken) cannot use the management
>> interfaces available in Dom0.
>>
>
> To me, this research sounds similar to "InDriver: Using In-VM
> Isolation to Implement Drivers" that is going to be presented at the
> upcoming Xen Summit
>
> see: http://xen.org/community/xensummit.html
>
> I could be wrong about the relationship, but it does sound like
> similar concepts are being explored.

Hm, there doesn't seem to be a link describing the talk/work in more
detail. I'm attempting to just give the NVIDIA driver an IOMMU domain
in Dom0 for accessing the GPUs within a machine. There's been a lot of
frustration over the years trying to get CUDA to work on Dom0 as well
as 3D support. I'm attempting to determine if this is at all possible
using VT-d.

>
>
>> My driver domain is also Dom0 at the moment.
>>
>>>  Some searching and
>>>>reading of the wiki pages on xen.org tells me the answer is "no". But
>>>>I cannot determine if this is purely because the implementation within
>>>>the VMM doesn't exist, or because it is that Dom0 is para-virtualized
>>>>and thus cannot use VT-d without VT-x. I'm suspecting it is not the
>>>>latter, as the VTdHowTo wiki page hints PV guests may use VT-d and the
>>>>Intel manual for VT-d describes OS developers may take advantage of
>>>>this extension.
>>>>
>>>>My immediate interest is more to see if it "can be done" via a hack or
>>>>something, not necessarily whether it would make sense
>>> for Xen to
>>>>support this in the future.
>>>>
>>> You should ask this question in xen-dev list.
>>
>> Okay, I'll do that. I'm new to these mailing lists, and wasn't sure
>> where to start. Thanks.
>>
>>>>I'm using Xen 4.1.1 and pv-ops linux (not upstream) 2.6.32.40 on an
>>>>Intel X5660 with a
>>> Tylersburg chipset.
>>>>
>>>>Thanks!
>>>>Alex
>>>>
>>>>_______________________________________________
>>>>Xen-users mailing list
>>>>Xen-users@xxxxxxxxxxxxxxxxxxx
>>>>http://lists.xensource.com/xen-users
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>
>
>
> --
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://www.xen.org/products/cloudxen.html
> http://runningxen.com/
>

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

<Prev in Thread] Current Thread [Next in Thread>