From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: about vEOI optimization Date: Thu, 25 Aug 2011 07:39:16 +0300 Message-ID: <4E55D1F4.4050904@redhat.com> References: <625BA99ED14B2D499DC4E29D8138F150630051F1F5@shsmsx502.ccr.corp.intel.com> <4E54CBAB.5070401@redhat.com> <625BA99ED14B2D499DC4E29D8138F150630051FB74@shsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" , "Nakajima, Jun" To: "Tian, Kevin" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39954 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751229Ab1HYEjU (ORCPT ); Thu, 25 Aug 2011 00:39:20 -0400 In-Reply-To: <625BA99ED14B2D499DC4E29D8138F150630051FB74@shsmsx502.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/25/2011 05:24 AM, Tian, Kevin wrote: > > > > Another option is the hyper-V EOI support, which can also eliminate the > > EOI exit when no additional interrupt is pending. This can improve EOI > > performance even more. > > > > yes, and this is an orthogonal option. > > So if you agree, I'll send out an updated patch atop their work. > > Thanks. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.