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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
From: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Date: Tue, 18 Sep 2007 13:41:32 -0700
Cc: Guy Zana <guy@xxxxxxxxxxxx>
Delivery-date: Tue, 18 Sep 2007 13:42:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3159CA9.15A8C%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: <13A2F7DE1BAEA345A61DD40F303ED7A67C4D77@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3159CA9.15A8C%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfvUP/V2RoylwXMQm6N0Av9il/s3AKJmCkAACHV60MABY05cA==
Thread-topic: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
Gnntab_transfer changes were originally made by one of my colleagus for
supporting PV guest in another configuration.  We will resubmit this in
the future after we clean this up.

The reason we are checking for !hvm_domain in page_alloc() is for
setting up vt-d page tables for dom0 and PV domain.  Note that once vt-d
DMA translation is enabled, it applies to all domains.

VT-d page table for HVM domain is shared with p2m table.  It is setup by
vtd/intel-iommu.c/iommu_set_pgd() - call from p2m.c.  This is the reason
we don't need to do anything from hvm domain in page_alloc.c.

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.

I have split the remaining xen_misc.patch into following two pieces:

- io.patch      : ioport handling and 2 trivial header file changes
- xen_misc.patch: the remaining misc. xen changes.


Signed-off-by: Allen Kay <allen.m.kay@xxxxxxxxx>
Signed-off-by: Guy Zana <guy@xxxxxxxxxxxx>

>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
>Sent: Tuesday, September 18, 2007 7:18 AM
>To: Kay, Allen M; xen-devel@xxxxxxxxxxxxxxxxxxx
>Cc: Guy Zana
>Subject: Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel 
>VT-d/Neocleus 1:1 mregedcode for PCI passthrough
>On 17/9/07 23:17, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote:
>> These two patches contains miscellaneous xen and interrupt handling
>> changes contains in previous xen.patch.
>> xen_misc.c: miscellaneous collection of xen changes
>The changes to common code reference an x86-specific variable. 
>Also I don't
>see how the changes make sense. Gnttab_transfer is deprecated 
>so why would
>you care about modifying that path?  The changes in page_alloc.c are
>dependent on !hvm_domain(), but I thought the iommu changes were
>specifically to support PCI passthru for HVM domains?
> -- Keir

Attachment: io.patch
Description: io.patch

Attachment: xen_misc.patch
Description: xen_misc.patch

Xen-devel mailing list