xen-devel

[Top] [All Lists]

Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git)

from [Andy Burns]

[Permanent Link][Original]

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git)
From:	Andy Burns <xen.lists@xxxxxxxxxxx>
Date:	Sun, 29 Mar 2009 21:15:27 +0100
Delivery-date:	Sun, 29 Mar 2009 13:15:57 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=j9pyP2nAqDe8LCVaLePnK7UxxWHOMVMrxEKyKbcQfgU=; b=WaIXUX3rm2uOFGrnnfncbMqActLQNvKFmdRyu8ao1Z8bRb0yni8hoAwAE8wvihIHfu qEfiUrsb7Y4akZFcr9zAsrzwtfT0GGTBh72ClYMv4dKpn2XQ9FqPwl1pihXrINRxtLla 5iBlmfhTi3VjwHX5hUEVFz+glaXjMCki5jvgM=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=o/et94qqJg78V/Dz3w0c+Bvj6b2LpXSfk2AKYlCnLhzFP4yIO5Bb9xuziq0jFS56YS Uusj25Zkg+7aXz6IaY2i8tK32ADrvveor7kaGs1VlhHJg9FFgvN+y9MYpCoEN1ZRZWTf K3dOw8TB1oe9+4RCND0uClJMOqGOstnOZkkTg=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<49C915A3.3020809@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<49C915A3.3020809@xxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

2009/3/24 Jeremy Fitzhardinge <jeremy@xxxxxxxx>:

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

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [GIT PULL] xen.git 2.6.30: push2/x86/paravirt: preemption in lazy mmu updates, (continued) [Xen-devel] [GIT PULL] xen.git 2.6.30: push2/x86/paravirt: preemption in lazy mmu updates, Jeremy Fitzhardinge [Xen-devel] [GIT PULL] xen.git 2.6.30: core Xen updates, Jeremy Fitzhardinge [Xen-devel] [GIT PULL] xen.git 2.6.30: usermode control interfaces, Jeremy Fitzhardinge [Xen-devel] [GIT PULL] xen.git 2.6.30: xen dom0 core support, Jeremy Fitzhardinge [Xen-devel] [GIT PULL] xen.git 2.6.30: xen dom0 apic changes, Jeremy Fitzhardinge [Xen-devel] [GIT PULL] xen.git 2.6.30: xen dom0 PCI device support, Jeremy Fitzhardinge [Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git), Ingo Molnar [Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge Message not available [Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge [Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git), Andy Burns <= Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge

Previous by Date:	[Xen-devel] crash while booting latest hackery kernel, M A Young
Next by Date:	Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge
Previous by Thread:	[Xen-devel] Re: 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge
Next by Thread:	Re: [Xen-devel] 2.6.30 Xen merge plan (what's in xen.git), Jeremy Fitzhardinge
Indexes:	[Date] [Thread] [Top] [All Lists]