From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: avoid taking ioapic mutex for non-ioapic EOIs
Date: Mon, 28 Dec 2009 18:37:57 -0200 [thread overview]
Message-ID: <20091228203757.GA20508@amt.cnet> (raw)
In-Reply-To: <1262002110-4240-1-git-send-email-avi@redhat.com>
On Mon, Dec 28, 2009 at 02:08:30PM +0200, Avi Kivity wrote:
> When the guest acknowledges an interrupt, it sends an EOI message to the local
> apic, which broadcasts it to the ioapic. To handle the EOI, we need to take
> the ioapic mutex.
>
> On large guests, this causes a lot of contention on this mutex. Since large
> guests usually don't route interrupts via the ioapic (they use msi instead),
> this is completely unnecessary.
>
> Avoid taking the mutex by introducing a handled_vectors bitmap. Before taking
> the mutex, check if the ioapic was actually responsible for the acked vector.
> If not, we can return early.
Can't you skip IOAPIC EOI for edge triggered interrupts (in the LAPIC
code), instead?
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> virt/kvm/ioapic.c | 19 +++++++++++++++++++
> virt/kvm/ioapic.h | 1 +
> 2 files changed, 20 insertions(+), 0 deletions(-)
>
> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> index f01392f..a2edfd1 100644
> --- a/virt/kvm/ioapic.c
> +++ b/virt/kvm/ioapic.c
> @@ -100,6 +100,19 @@ static int ioapic_service(struct kvm_ioapic *ioapic, unsigned int idx)
> return injected;
> }
>
> +static void update_handled_vectors(struct kvm_ioapic *ioapic)
> +{
> + DECLARE_BITMAP(handled_vectors, 256);
> + int i;
> +
> + memset(handled_vectors, 0, sizeof(handled_vectors));
> + for (i = 0; i < IOAPIC_NUM_PINS; ++i)
> + __set_bit(ioapic->redirtbl[i].fields.vector, handled_vectors);
> + memcpy(ioapic->handled_vectors, handled_vectors,
> + sizeof(handled_vectors));
> + smp_wmb();
> +}
> +
> static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val)
> {
> unsigned index;
> @@ -134,6 +147,7 @@ static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val)
> e->bits |= (u32) val;
> e->fields.remote_irr = 0;
> }
> + update_handled_vectors(ioapic);
> mask_after = e->fields.mask;
> if (mask_before != mask_after)
> kvm_fire_mask_notifiers(ioapic->kvm, index, mask_after);
> @@ -241,6 +255,9 @@ void kvm_ioapic_update_eoi(struct kvm *kvm, int vector, int trigger_mode)
> {
> struct kvm_ioapic *ioapic = kvm->arch.vioapic;
>
> + smp_rmb();
> + if (!test_bit(vector, ioapic->handled_vectors))
> + return;
> mutex_lock(&ioapic->lock);
> __kvm_ioapic_update_eoi(ioapic, vector, trigger_mode);
> mutex_unlock(&ioapic->lock);
> @@ -352,6 +369,7 @@ void kvm_ioapic_reset(struct kvm_ioapic *ioapic)
> ioapic->ioregsel = 0;
> ioapic->irr = 0;
> ioapic->id = 0;
> + update_handled_vectors(ioapic);
> }
>
> static const struct kvm_io_device_ops ioapic_mmio_ops = {
> @@ -401,6 +419,7 @@ int kvm_set_ioapic(struct kvm *kvm, struct kvm_ioapic_state *state)
>
> mutex_lock(&ioapic->lock);
> memcpy(ioapic, state, sizeof(struct kvm_ioapic_state));
> + update_handled_vectors(ioapic);
> mutex_unlock(&ioapic->lock);
> return 0;
> }
> diff --git a/virt/kvm/ioapic.h b/virt/kvm/ioapic.h
> index 419c43b..a505ce9 100644
> --- a/virt/kvm/ioapic.h
> +++ b/virt/kvm/ioapic.h
> @@ -46,6 +46,7 @@ struct kvm_ioapic {
> struct kvm *kvm;
> void (*ack_notifier)(void *opaque, int irq);
> struct mutex lock;
> + DECLARE_BITMAP(handled_vectors, 256);
> };
>
> #ifdef DEBUG
> --
> 1.6.5.3
next prev parent reply other threads:[~2009-12-28 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 12:08 [PATCH] KVM: avoid taking ioapic mutex for non-ioapic EOIs Avi Kivity
2009-12-28 20:37 ` Marcelo Tosatti [this message]
2009-12-28 20:47 ` Avi Kivity
2009-12-28 21:30 ` Marcelo Tosatti
2009-12-29 10:35 ` Avi Kivity
2009-12-29 16:59 ` Marcelo Tosatti
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=20091228203757.GA20508@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
/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