From: "David S. Ahern" <daahern@cisco.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: KVM: PIC: enhance IPI avoidance
Date: Tue, 23 Sep 2008 21:05:44 -0600 [thread overview]
Message-ID: <48D9AE88.7060603@cisco.com> (raw)
In-Reply-To: <20080922165749.GA18733@dmt.cnet>
This patched worked very nicely for me -- about an 8% performance
improvement for my workload.
david
Marcelo Tosatti wrote:
> KVM: PIC: enhance IPI avoidance
>
> The PIC code makes little effort to avoid kvm_vcpu_kick(), resulting in
> unnecessary guest exits in some conditions.
>
> For example, if the timer interrupt is routed through the IOAPIC, IRR
> for IRQ 0 will get set but not cleared, since the APIC is handling the
> acks.
>
> This means that everytime an interrupt < 16 is triggered, the priority
> logic will find IRQ0 pending and send an IPI to vcpu0 (in case IRQ0 is
> not masked, which is Linux's case).
>
> Introduce a new variable isr_ack to represent the IRQ's for which the
> guest has been signalled / cleared the ISR. Use it to avoid more than
> one IPI per trigger-ack cycle, in addition to the avoidance when ISR is
> set in get_priority().
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
>
> Index: kvm/arch/x86/kvm/i8259.c
> ===================================================================
> --- kvm.orig/arch/x86/kvm/i8259.c
> +++ kvm/arch/x86/kvm/i8259.c
> @@ -33,6 +33,7 @@
> static void pic_clear_isr(struct kvm_kpic_state *s, int irq)
> {
> s->isr &= ~(1 << irq);
> + s->isr_ack |= (1 << irq);
> }
>
> /*
> @@ -213,6 +214,7 @@ void kvm_pic_reset(struct kvm_kpic_state
> s->irr = 0;
> s->imr = 0;
> s->isr = 0;
> + s->isr_ack = 0xff;
> s->priority_add = 0;
> s->irq_base = 0;
> s->read_reg_select = 0;
> @@ -444,10 +446,14 @@ static void pic_irq_request(void *opaque
> {
> struct kvm *kvm = opaque;
> struct kvm_vcpu *vcpu = kvm->vcpus[0];
> + struct kvm_pic *s = pic_irqchip(kvm);
> + int irq = pic_get_irq(&s->pics[0]);
>
> - pic_irqchip(kvm)->output = level;
> - if (vcpu)
> + s->output = level;
> + if (vcpu && level && (s->pics[0].isr_ack & (1 << irq))) {
> + s->pics[0].isr_ack &= ~(1 << irq);
> kvm_vcpu_kick(vcpu);
> + }
> }
>
> struct kvm_pic *kvm_create_pic(struct kvm *kvm)
> Index: kvm/arch/x86/kvm/irq.h
> ===================================================================
> --- kvm.orig/arch/x86/kvm/irq.h
> +++ kvm/arch/x86/kvm/irq.h
> @@ -42,6 +42,7 @@ struct kvm_kpic_state {
> u8 irr; /* interrupt request register */
> u8 imr; /* interrupt mask register */
> u8 isr; /* interrupt service register */
> + u8 isr_ack; /* interrupt ack detection */
> u8 priority_add; /* highest irq priority */
> u8 irq_base;
> u8 read_reg_select;
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-09-24 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 16:57 KVM: PIC: enhance IPI avoidance Marcelo Tosatti
2008-09-24 3:05 ` David S. Ahern [this message]
2008-09-24 12:19 ` Avi Kivity
2008-09-24 14:40 ` Marcelo Tosatti
2008-09-24 14:49 ` Avi Kivity
2008-09-24 23:28 ` Marcelo Tosatti
2008-09-25 10:18 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D9AE88.7060603@cisco.com \
--to=daahern@cisco.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).