xen-devel
Re: [Xen-devel] upstream merge status for 2.6.35, .36?
On Fri, Jun 04, 2010 at 05:20:06PM -0700, Jeremy Fitzhardinge wrote:
> On 06/04/2010 03:39 PM, Josip Rodin wrote:
> > What about the future? I saw Konrad's applied his swiotlb tree with the
> > right acks for inclusion into linux-next, so that looks like it's planned
> > to be ready to go in when the .36 merge window opens, right?
> >
>
> Yes, and I'm hoping we can get pcifront and pvhvm lined up for .36; with
> those in place, its a short jump to full dom0 functionality (which, no
> promises, might also get into .36 on their tails).
>
swiotlb seems to be in linux-next now.. Congratulations!
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] upstream merge status for 2.6.35, .36?, Josip Rodin
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?, Jeremy Fitzhardinge
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?,
Pasi Kärkkäinen <=
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?, Josip Rodin
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?, Konrad Rzeszutek Wilk
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?, Jeremy Fitzhardinge
- [Xen-devel] Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0, Boris Derzhavets
- [Xen-devel] Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0, Jeremy Fitzhardinge
- Re: [Xen-devel] upstream merge status for 2.6.35, .36?, Jeremy Fitzhardinge
|
|
|