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 0/6] Intel VT-d/Neocleus 1:1 mreged code

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 11 Sep 2007 14:04:47 +0100
Cc: Guy Zana <guy@xxxxxxxxxxxx>
Delivery-date: Tue, 11 Sep 2007 06:05:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C30C4D7E.1562B%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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfvUPA+fwPVGW6LTE+QIE4aSL5IWQFIU1UoAACFqk4=
Thread-topic: [Xen-devel] [VTD-NEO][patch 0/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
User-agent: Microsoft-Entourage/11.3.6.070618
On 11/9/07 13:49, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:

> Haven't looked any further at the Xen parts, but I'll take a look at the
> tools patch...

Looking at the tools patch, I see strange interfaces like
HVMOP_copy_nativedom_e820_map:
 1. Why is this an hvm_op unlike other added domctls?
 2. Why is it needed at all? Can't xc_hvm_build.c work out the memory map
for itself? It seems like more than necessary is being done in Xen.

Looks like splitting solely pt and solely vtd code into separate patches
would be a good idea, so the more acdeptable chunks can slide straight in
without delay.

 -- Keir



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