From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 6/8 v2] Move IO APIC to its own lock.
Date: Wed, 12 Aug 2009 11:27:13 +0300 [thread overview]
Message-ID: <4A827CE1.7040304@redhat.com> (raw)
In-Reply-To: <1249993895-11119-7-git-send-email-gleb@redhat.com>
On 08/11/2009 03:31 PM, Gleb Natapov wrote:
What is the motivation for this change?
Why a spinlock and not a mutex?
> diff --git a/arch/ia64/kvm/kvm-ia64.c b/arch/ia64/kvm/kvm-ia64.c
> index 0ad09f0..dd7ef2d 100644
> --- a/arch/ia64/kvm/kvm-ia64.c
> +++ b/arch/ia64/kvm/kvm-ia64.c
> @@ -850,9 +850,16 @@ static int kvm_vm_ioctl_get_irqchip(struct kvm *kvm,
>
> r = 0;
> switch (chip->chip_id) {
> - case KVM_IRQCHIP_IOAPIC:
> - memcpy(&chip->chip.ioapic, ioapic_irqchip(kvm),
> - sizeof(struct kvm_ioapic_state));
> + case KVM_IRQCHIP_IOAPIC: {
> + struct kvm_ioapic *ioapic = ioapic_irqchip(kvm);
> + if (ioapic) {
> + spin_lock(&ioapic->lock);
> + memcpy(&chip->chip.ioapic, ioapic,
> + sizeof(struct kvm_ioapic_state));
> + spin_unlock(&ioapic->lock);
>
Better to add an accessor than to reach into internals like this.
> + } else
> + r = -EINVAL;
> + }
> break;
> default:
> r = -EINVAL;
> @@ -867,10 +874,16 @@ static int kvm_vm_ioctl_set_irqchip(struct kvm *kvm, struct kvm_irqchip *chip)
>
> r = 0;
> switch (chip->chip_id) {
> - case KVM_IRQCHIP_IOAPIC:
> - memcpy(ioapic_irqchip(kvm),
> - &chip->chip.ioapic,
> - sizeof(struct kvm_ioapic_state));
> + case KVM_IRQCHIP_IOAPIC: {
> + struct kvm_ioapic *ioapic = ioapic_irqchip(kvm);
> + if (ioapic) {
> + spin_lock(&ioapic->lock);
> + memcpy(ioapic,&chip->chip.ioapic,
> + sizeof(struct kvm_ioapic_state));
> + spin_unlock(&ioapic->lock);
> + } else
> + r = -EINVAL;
> + }
>
... and better to deduplicate the code too.
> break;
> default:
> r = -EINVAL;
> diff --git a/arch/x86/kvm/i8259.c b/arch/x86/kvm/i8259.c
> index 01f1516..a988c0e 100644
> --- a/arch/x86/kvm/i8259.c
> +++ b/arch/x86/kvm/i8259.c
> @@ -38,7 +38,9 @@ static void pic_clear_isr(struct kvm_kpic_state *s, int irq)
> s->isr_ack |= (1<< irq);
> if (s !=&s->pics_state->pics[0])
> irq += 8;
> + spin_unlock(&s->pics_state->lock);
> kvm_notify_acked_irq(s->pics_state->kvm, SELECT_PIC(irq), irq);
> + spin_lock(&s->pics_state->lock);
> }
>
Need to explain why this is safe. I'm not sure it is, because we touch
state afterwards in pic_intack(). We need to do all vcpu-synchronous
operations before dropping the lock.
> void kvm_pic_clear_isr_ack(struct kvm *kvm)
> @@ -238,7 +240,9 @@ void kvm_pic_reset(struct kvm_kpic_state *s)
> if (vcpu0&& kvm_apic_accept_pic_intr(vcpu0))
> if (s->irr& (1<< irq) || s->isr& (1<< irq)) {
> n = irq + irqbase;
> + spin_unlock(&s->pics_state->lock);
> kvm_notify_acked_irq(kvm, SELECT_PIC(n), n);
> + spin_lock(&s->pics_state->lock);
>
Ditto here, needs to be moved until after done changing state.
>
> -static void __kvm_ioapic_update_eoi(struct kvm_ioapic *ioapic, int pin,
> - int trigger_mode)
> +static void __kvm_ioapic_update_eoi(struct kvm_ioapic *ioapic, int vector,
> + int trigger_mode)
> {
> - union kvm_ioapic_redirect_entry *ent;
> + int i;
> +
> + for (i = 0; i< IOAPIC_NUM_PINS; i++) {
> + union kvm_ioapic_redirect_entry *ent =&ioapic->redirtbl[i];
> +
> + if (ent->fields.vector != vector)
> + continue;
>
> - ent =&ioapic->redirtbl[pin];
> + spin_unlock(&ioapic->lock);
> + kvm_notify_acked_irq(ioapic->kvm, KVM_IRQCHIP_IOAPIC, i);
> + spin_lock(&ioapic->lock);
>
>
I *think* we need to clear remote_irr before dropping the lock. I
*know* there's a missing comment here.
> - kvm_notify_acked_irq(ioapic->kvm, KVM_IRQCHIP_IOAPIC, pin);
> + if (trigger_mode != IOAPIC_LEVEL_TRIG)
> + continue;
>
> - if (trigger_mode == IOAPIC_LEVEL_TRIG) {
> ASSERT(ent->fields.trig_mode == IOAPIC_LEVEL_TRIG);
> ent->fields.remote_irr = 0;
> - if (!ent->fields.mask&& (ioapic->irr& (1<< pin)))
> - ioapic_service(ioapic, pin);
> + if (!ent->fields.mask&& (ioapic->irr& (1<< i)))
> + ioapic_service(ioapic, i);
> }
> }
>
To make the patch easier to read, suggest keeping the loop in the other
function.
>
> void kvm_ioapic_update_eoi(struct kvm *kvm, int vector, int trigger_mode)
> {
> struct kvm_ioapic *ioapic = kvm->arch.vioapic;
> - int i;
>
> - for (i = 0; i< IOAPIC_NUM_PINS; i++)
> - if (ioapic->redirtbl[i].fields.vector == vector)
> - __kvm_ioapic_update_eoi(ioapic, i, trigger_mode);
> + spin_lock(&ioapic->lock);
> + __kvm_ioapic_update_eoi(ioapic, vector, trigger_mode);
> + spin_unlock(&ioapic->lock);
> }
>
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-12 8:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 12:31 [PATCH 0/8 v2] make interrupt injection lockless (almost) Gleb Natapov
2009-08-11 12:31 ` [PATCH 1/8 v2] Change irq routing table to use gsi indexed array Gleb Natapov
2009-08-12 8:05 ` Avi Kivity
2009-08-12 8:41 ` Gleb Natapov
2009-08-12 9:06 ` Avi Kivity
2009-08-11 12:31 ` [PATCH 2/8 v2] Maintain back mapping from irqchip/pin to gsi Gleb Natapov
2009-08-12 8:09 ` Avi Kivity
2009-08-12 8:42 ` Gleb Natapov
2009-08-12 9:06 ` Avi Kivity
2009-08-12 10:17 ` Gleb Natapov
2009-08-12 10:19 ` Avi Kivity
2009-08-11 12:31 ` [PATCH 3/8 v2] Move irq routing data structure to rcu locking Gleb Natapov
2009-08-11 12:31 ` [PATCH 4/8 v2] Move irq ack notifier list to arch independent code Gleb Natapov
2009-08-11 12:31 ` [PATCH 5/8 v2] Convert irq notifiers lists to RCU locking Gleb Natapov
2009-08-11 12:31 ` [PATCH 6/8 v2] Move IO APIC to its own lock Gleb Natapov
2009-08-12 8:27 ` Avi Kivity [this message]
2009-08-12 9:04 ` Gleb Natapov
2009-08-12 9:18 ` Avi Kivity
2009-08-12 9:47 ` Gleb Natapov
2009-08-12 9:57 ` Avi Kivity
2009-08-12 10:05 ` Gleb Natapov
2009-08-12 10:07 ` Avi Kivity
2009-08-11 12:31 ` [PATCH 7/8 v2] Drop kvm->irq_lock lock from irq injection path Gleb Natapov
2009-08-11 12:31 ` [PATCH 8/8 v2] Change irq_lock from mutex to spinlock Gleb Natapov
2009-08-12 8:29 ` Avi Kivity
2009-08-12 9:11 ` Gleb Natapov
2009-08-12 9:22 ` Avi Kivity
2009-08-12 9:47 ` Gleb Natapov
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=4A827CE1.7040304@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.