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] [PATCH 0 of 6] PV on HVM Xen

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 6] PV on HVM Xen
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Fri, 23 Apr 2010 18:41:18 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 23 Apr 2010 10:41:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BD0DF13.10001@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: <alpine.DEB.2.00.1004221519440.11380@kaball-desktop> <4BD0DF13.10001@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Fri, 23 Apr 2010, Jeremy Fitzhardinge wrote:
> On 04/22/2010 08:15 AM, Stefano Stabellini wrote:
> > Hi all,
> > this is an incremental update on my last PV on HVM series, including
> > many bug fixes.
> >   
> 
> Thanks!
> 
> > In particular multivcpu guests, suspend\resume, the unplug of
> > emulate devices and receving evtchns as interrupts from the platform pci
> > device should all work correctly now.
> > However the new pv clocksource is still missing, and also I left the
> > xen_guest_init code in enlighten.c for the moment.
> >
> > This series is based on Jeremy's pvops kernel tree, branch name
> > stable-2.6.33.x.
> >   
> 
> I still prefer patches to be based on an upstream kernel version if at
> all possible (ideally 2.6.32).  If you depend on something that's not in
> mainline, then merge the specific branch for that feature into your
> pvhvm branch (IOW, it would help if you used a git-based workflow).
> 

it doesn't depend on anything in pvops; I have rebased my series on 2.6.32,
I setup a git tree here:

git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git

branch name 2.6.32-pvhvm


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

<Prev in Thread] Current Thread [Next in Thread>