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 7/7] xen: Enable event channel of PV extension of

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 7/7] xen: Enable event channel of PV extension of HVM
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 9 Mar 2010 09:48:05 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Konrad, Ingo Molnar <mingo@xxxxxxx>, Wilk <kliw@xxxxxxxxxx>, Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Delivery-date: Tue, 09 Mar 2010 01:48:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B95F224.3060205@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>
Organization: Citrix Systems, Inc.
References: <1268032732-8025-1-git-send-email-sheng@xxxxxxxxxxxxxxx> <1268032732-8025-8-git-send-email-sheng@xxxxxxxxxxxxxxx> <alpine.DEB.2.00.1003081701160.16237@kaball-desktop> <201003090953.16985.sheng@xxxxxxxxxxxxxxx> <4B95F224.3060205@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2010-03-09 at 07:00 +0000, Jeremy Fitzhardinge wrote:
> On 03/08/2010 05:53 PM, Sheng Yang wrote:
> > On Tuesday 09 March 2010 01:10:56 Stefano Stabellini wrote:
> >    
> >> I think that mapping interrupts into VIRQs is a bad idea: you should map
> >> interrupts into pirqs instead, the code exists already on the kernel
> >> side so we don't need to do any (ugly) change ther.
> >>      
> > The code existed in the pv_ops dom0 side, but not in the upstream Linux. The
> > latter is our target. We want this work to be accepted by upstream Linux 
> > soon.

>    2. It has significant overlaps with the current xen.git development
>       which is also targeted for upstream.  There's no point in creating
>       an unnecessary duplicate mechanism when the infrastructure will be
>       in place anyway.

There's also nothing stopping us from upstreaming portions of the "dom0"
patchset ahead of full dom0 support if it is useful for some domU


Xen-devel mailing list

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