From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH v2 06/20] kvm: Install optimized interrupt handler Date: Tue, 15 Mar 2011 14:10:11 -0300 Message-ID: <20110315171011.GA25624@amt.cnet> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55858 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757762Ab1CORYU (ORCPT ); Tue, 15 Mar 2011 13:24:20 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Mar 15, 2011 at 12:26:17PM +0100, Jan Kiszka wrote: > KVM only requires to set the raised IRQ in CPUState and to kick the > receiving vcpu if it is remote. > > Signed-off-by: Jan Kiszka > --- > kvm-all.c | 11 +++++++++++ > 1 files changed, 11 insertions(+), 0 deletions(-) > > diff --git a/kvm-all.c b/kvm-all.c > index 226843c..25ab545 100644 > --- a/kvm-all.c > +++ b/kvm-all.c > @@ -650,6 +650,15 @@ static CPUPhysMemoryClient kvm_cpu_phys_memory_client = { > .log_stop = kvm_log_stop, > }; > > +static void kvm_handle_interrupt(CPUState *env, int mask) > +{ > + env->interrupt_request |= mask; > + > + if (!qemu_cpu_is_self(env)) { > + qemu_cpu_kick(env); > + } > +} > + Not sure its worthwhile to allow different handlers. The advantage over tcg version is that its shorter, without cpu_unlink_tb and icount handler?