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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 5] PV on HVM Xen
From: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Date: Thu, 18 Mar 2010 10:19:42 +0800
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 17 Mar 2010 19:20:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1003171047230.23661@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>
Organization: Intel Opensource Technology Center
References: <alpine.DEB.2.00.1003101457100.28412@kaball-desktop> <201003171738.37830.sheng@xxxxxxxxxxxxxxx> <alpine.DEB.2.00.1003171047230.23661@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; )
On Wednesday 17 March 2010 23:21:08 Stefano Stabellini wrote:
> On Wed, 17 Mar 2010, Sheng Yang wrote:
> > I would like to work on the PIRQ porting upstream Linux
> I am glad to hear that!
> > A simple version would be just using PIRQ instead of VIRQ in my
> > patches, but PIRQ is flexible, I would see if I can do more with it
> After the first part of your series gets applied, I'll rebase my pirq
> remapping patches on top of it, then you can tell me what's wrong so I
> can change it. I am very open to critics or suggestions.
> I would also prefer that you take my pirq remapping patches, you make
> any change you like, then you send your work to the list, rather than
> reinventing the wheel.

Yeah, I'd like to take your patch and modify it as much as possible, which 
would be more efficient. Of course, with your signed-off hold. :)

Yang, Sheng

> I value your contributions so I would be happy if you could work on my
> series, that even though is working still misses MSI support and I am
> sure you'll be able to make many other important improvements.
> > And we may not get a version exactly the same as pv_ops dom0 code in
> > the end... I would try to make them similar and make the HVM part
> > small enough, then reduce Jeremy's maintain effort.
> As pointed out before by Jeremy and Konrad, the best starting point is
> probably Konrad's pv/pcifront-2.6.31 tree: it contains most of the pirq
> stuff, ready to be upstreamed.
> AFAICT the only things required to make pirq mappings work (as in
> my series) that are missing are:
> - xen_register_gsi
> - xen_setup_pirqs
> - the xen_register_gsi hook in acpi_register_gsi
> the first two should be easy to port because they don't require any
> change but the last one definitely needs modifications in order to be
> accepted upstream.
> I didn't include MSI support because is not required, but that is
> another area that needs changes.

Xen-devel mailing list

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