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 5] PV on HVM Xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Fri, 12 Mar 2010 16:00:42 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Delivery-date: Fri, 12 Mar 2010 07:56:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1003121024590.27222@kaball-desktop>
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.1003101457100.28412@kaball-desktop> <201003121123.33935.sheng@xxxxxxxxxxxxxxx> <alpine.DEB.2.00.1003121024590.27222@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Fri, 12 Mar 2010, Stefano Stabellini wrote:
> My intentions are true so my proposal of working on a common tree is
> still valid, just let me know when you are interested.
> 

The last versions of our patch series are quite similar, I think at this
point we can really merge them into one.
If you take the time to read the last version of my patch series I
think you'll be able to see it by yourself (missing From: line aside,
again sorry for that).
I looked at the last version of yours and I listed the changes I would
like to be made on top of it, if you and Jeremy agree:


PATCH 1
fine as it is;

PATCH 2
fine as it is;

PATCH 3
I would remove it altogether because I would like to make pv drivers
work on HVM, but considering that at the moment they wouldn't work,
it makes sense to apply it for now;

PATCH 4
I would remove HVMOP_enable_pv, xen_hvm_pv_clock_enabled and the
pvclock for the moment;

PATCH 5
I would change the entry point because I think the one I use in my
patch series is less controversial and probably easier to get accepted
upstream: look at the first part of my second patch;

PATCH 6
I would remove this patch and talk about pv clocksource again when we
do the interrupt remapping work.

Jeremy, what do you think about it?
If we agree on these few basic patches, I'll wait for Jeremy to apply
them in a topic branch and then I'll send my changes on top of them,
adding PV on HVM support (I mean the xen pci platform device driver,
blkfront and netfront) and everybody will be happy.

After this is done we can calmly discuss about how to proceed with the
interrupt remapping stuff.


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