From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: 2.6.30 Xen merge plan (what's in xen.git)
Date: Sun, 29 Mar 2009 13:51:29 -0700
Message-ID: <49CFDF51.2010706@goop.org>
References: <49C915A3.3020809@goop.org>
	<b4057d410903291315j2f4d5170red569e9d3534078c@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <b4057d410903291315j2f4d5170red569e9d3534078c@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Andy Burns <xen.lists@burns.me.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Andy Burns wrote:
> 2009/3/24 Jeremy Fitzhardinge <jeremy@goop.org>:
>
>   
>> push2/xen/dom0/apic
>> push2/xen/dom0/pci
>>     
>
> Does it mean that if these patchsets make it into 2.6.30 there will be
> paravirt_ops dom0 that supports PCI passthrough?
>   

No, those are just the changes necessary to have native device drivers 
in dom0 work at all.  In fact, I'm not proposing any backend device 
support for mainline in this merge window, so you'll still need some out 
of tree changes to get a useful system.  But these changes do have a 
fair amount in common with what's needed for pci passthrough, so there 
is some progress (albeit abstract).

    J