From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: [PATCH][v2] Hybrid extension support in Xen Date: Tue, 2 Feb 2010 22:39:10 +0800 Message-ID: <201002022239.10384.sheng@linux.intel.com> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Eddie Dong , Jun Nakajima List-Id: xen-devel@lists.xenproject.org On Tuesday 02 February 2010 22:32:09 Keir Fraser wrote: > On 02/02/2010 14:08, "Sheng Yang" wrote: > >> Okay, so that leads to the obvious next question: why do you want to > >> avoid using INIT-SIPI-SIPI? > > > > Because we don't have IOAPIC/LAPIC... > > Is it necessary to remove the LAPICs completely? If you go very far down > the route of ripping emulated stuff out of HVM, it starts to feel like > starting with a pure PV guest and HVMing it up is closer in spirit to what > you might be aiming for. The performance of interrupt delivery is what we care about. The IOAPIC/LAPIC don't work well now, so we want event channel to eliminate their overhead, notably EOI in LAPIC. And you know, start from a PV guest is another story... -- regards Yang, Sheng