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: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 18 Sep 2007 15:18:01 +0100
Cc: Guy Zana <guy@xxxxxxxxxxxx>
Delivery-date: Tue, 18 Sep 2007 07:19:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <13A2F7DE1BAEA345A61DD40F303ED7A67C4D77@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfvUP/V2RoylwXMQm6N0Av9il/s3AKJmCkAACHV60M=
Thread-topic: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode for PCI passthrough
User-agent: Microsoft-Entourage/11.3.6.070618
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



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