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: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 18 Mar 2010 09:50:27 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Mar 2010 09:51:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1003181331150.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>
References: <alpine.DEB.2.00.1003101457100.28412@kaball-desktop> <201003171718.37598.sheng@xxxxxxxxxxxxxxx> <alpine.DEB.2.00.1003171100310.23661@kaball-desktop> <201003180935.23645.sheng@xxxxxxxxxxxxxxx> <alpine.DEB.2.00.1003181331150.23661@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.3
On 03/18/2010 07:22 AM, Stefano Stabellini wrote:
Also XEN_HVM_PV_EVTCHN_ENABLED is not a good name for it because we'll
be able to receive evtchns anyway using xen platform device interrupts.

I'm OK with the original name. The point is not that we're getting events from evtchns, but that the mechanism allows us to receive them without having to touch the APICs and suffer the vmexits. To the rest of the kernel, events delivered via the platform device are really just ordinary interrupts from an ordinary device which happens to have a particularly elaborate "interrupt source" register.


Xen-devel mailing list