From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Fri, 24 Feb 2012 23:33:58 +0000 Subject: Re: [PATCH 35/37] KVM: PPC: booke: Support perfmon interrupts Message-Id: <4F481E66.8010408@freescale.com> List-Id: References: <1330093591-19523-1-git-send-email-agraf@suse.de> <1330093591-19523-36-git-send-email-agraf@suse.de> In-Reply-To: <1330093591-19523-36-git-send-email-agraf@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alexander Graf Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org On 02/24/2012 08:26 AM, Alexander Graf wrote: > When during guest context we get a performance monitor interrupt, we > currently bail out and oops. Let's route it to its correct handler > instead. > > Signed-off-by: Alexander Graf > --- > arch/powerpc/kvm/booke.c | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/arch/powerpc/kvm/booke.c b/arch/powerpc/kvm/booke.c > index 7adef28..423701b 100644 > --- a/arch/powerpc/kvm/booke.c > +++ b/arch/powerpc/kvm/booke.c > @@ -677,6 +677,10 @@ int kvmppc_handle_exit(struct kvm_run *run, struct kvm_vcpu *vcpu, > r = RESUME_GUEST; > break; > > + case BOOKE_INTERRUPT_PERFORMANCE_MONITOR: > + r = RESUME_GUEST; > + break; > + > case BOOKE_INTERRUPT_HV_PRIV: > r = emulation_exit(run, vcpu); > break; Why do we need to call timer_interrupt() explicitly, but can rely on automatic retriggering for perfmon? -Scott