From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 05/10] KVM: Merge MSI handling to kvm_set_irq
Date: Tue, 30 Dec 2008 12:48:42 +0200 [thread overview]
Message-ID: <4959FC8A.70808@redhat.com> (raw)
In-Reply-To: <1230616562-18113-6-git-send-email-sheng@linux.intel.com>
Sheng Yang wrote:
> Using kvm_set_irq to handle all interrupt injection.
>
>
> /* This should be called with the kvm->lock mutex held */
> -void kvm_set_irq(struct kvm *kvm, int irq_source_id, int irq, int level)
> +void kvm_set_irq(struct kvm *kvm, int irq_source_id, u32 gsi, int level)
> {
> - unsigned long *irq_state = (unsigned long *)&kvm->arch.irq_states[irq];
> -
> - /* Logical OR for level trig interrupt */
> - if (level)
> - set_bit(irq_source_id, irq_state);
> - else
> - clear_bit(irq_source_id, irq_state);
> -
> - /* Not possible to detect if the guest uses the PIC or the
> - * IOAPIC. So set the bit in both. The guest will ignore
> - * writes to the unused one.
> - */
> - kvm_ioapic_set_irq(ioapic_irqchip(kvm), irq, !!(*irq_state));
> + unsigned long *irq_state;
> +#ifdef CONFIG_X86
> + int vcpu_id;
> + struct kvm_vcpu *vcpu;
> + struct kvm_ioapic *ioapic = ioapic_irqchip(kvm);
> + struct kvm_gsi_msg *gsi_msg;
> + int dest_id, vector, dest_mode, trig_mode, delivery_mode;
> + u32 deliver_bitmask;
> +
> + BUG_ON(!ioapic);
> +#endif
> +
> + if (!(gsi & KVM_GSI_MSG_MASK)) {
> + int irq = gsi;
> +
> + irq_state = (unsigned long *)&kvm->arch.irq_states[irq];
> +
> + /* Logical OR for level trig interrupt */
> + if (level)
> + set_bit(irq_source_id, irq_state);
> + else
> + clear_bit(irq_source_id, irq_state);
> +
> + /* Not possible to detect if the guest uses the PIC or the
> + * IOAPIC. So set the bit in both. The guest will ignore
> + * writes to the unused one.
> + */
> + kvm_ioapic_set_irq(ioapic, irq, !!(*irq_state));
> #ifdef CONFIG_X86
> - kvm_pic_set_irq(pic_irqchip(kvm), irq, !!(*irq_state));
> + kvm_pic_set_irq(pic_irqchip(kvm), irq, !!(*irq_state));
> +#endif
> + return;
> + }
> +
> +#ifdef CONFIG_X86
> + mutex_lock(&kvm->gsi_msg_lock);
>
The lock is already taken here?
> + gsi_msg = kvm_find_gsi_msg(kvm, gsi);
> + mutex_unlock(&kvm->gsi_msg_lock);
> + if (!gsi_msg) {
> + printk(KERN_WARNING "kvm: fail to find correlated gsi_msg\n");
> + return;
> + }
> +
> + dest_id = (gsi_msg->msg.address_lo & MSI_ADDR_DEST_ID_MASK)
> + >> MSI_ADDR_DEST_ID_SHIFT;
> + vector = (gsi_msg->msg.data & MSI_DATA_VECTOR_MASK)
> + >> MSI_DATA_VECTOR_SHIFT;
> + dest_mode = test_bit(MSI_ADDR_DEST_MODE_SHIFT,
> + (unsigned long *)&gsi_msg->msg.address_lo);
> + trig_mode = test_bit(MSI_DATA_TRIGGER_SHIFT,
> + (unsigned long *)&gsi_msg->msg.data);
> + delivery_mode = test_bit(MSI_DATA_DELIVERY_MODE_SHIFT,
> + (unsigned long *)&gsi_msg->msg.data);
> + deliver_bitmask = kvm_ioapic_get_delivery_bitmask(ioapic,
> + dest_id, dest_mode);
> + /* IOAPIC delivery mode value is the same as MSI here */
> + switch (delivery_mode) {
> + case IOAPIC_LOWEST_PRIORITY:
> + vcpu = kvm_get_lowest_prio_vcpu(ioapic->kvm, vector,
> + deliver_bitmask);
> + if (vcpu != NULL)
> + kvm_apic_set_irq(vcpu, vector, trig_mode);
> + else
> + printk(KERN_INFO "kvm: null lowest priority vcpu!\n");
> + break;
> + case IOAPIC_FIXED:
> + for (vcpu_id = 0; deliver_bitmask != 0; vcpu_id++) {
> + if (!(deliver_bitmask & (1 << vcpu_id)))
> + continue;
> + deliver_bitmask &= ~(1 << vcpu_id);
> + vcpu = ioapic->kvm->vcpus[vcpu_id];
> + if (vcpu)
> + kvm_apic_set_irq(vcpu, vector, trig_mode);
> + }
> + break;
> + default:
> + printk(KERN_INFO "kvm: unsupported MSI delivery mode\n");
> + }
> #endif
> }
>
>
This looks very messy. Would be better to have the in-kernel irq
structure contain a (*set_level)() callback that can take the
appropriate action.
Also, the CONFIG_X86 worries me, can we have IA64 enable this as well?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-30 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 5:55 [PATCH 0/10][v3] GSI->MSG route layer for MSI/MSI-X Sheng Yang
2008-12-30 5:55 ` [PATCH 01/10] KVM: Add a route layer to convert MSI message to GSI Sheng Yang
2008-12-30 10:39 ` Avi Kivity
2008-12-30 5:55 ` [PATCH 02/10] KVM: Using gsi_msg mapping for MSI device assignment Sheng Yang
2008-12-30 5:55 ` [PATCH 03/10] KVM: Improve MSI dispatch function Sheng Yang
2008-12-30 5:55 ` [PATCH 04/10] KVM: Using ioapic_irqchip() macro for kvm_set_irq Sheng Yang
2008-12-30 5:55 ` [PATCH 05/10] KVM: Merge MSI handling to kvm_set_irq Sheng Yang
2008-12-30 10:48 ` Avi Kivity [this message]
2008-12-30 11:00 ` Sheng Yang
2008-12-30 11:07 ` Avi Kivity
2008-12-30 11:26 ` Sheng Yang
2008-12-30 5:55 ` [PATCH 06/10] KVM: Split IOAPIC structure Sheng Yang
2008-12-30 5:55 ` [PATCH 07/10] KVM: Unified the delivery of IOAPIC and MSI Sheng Yang
2008-12-30 5:56 ` [PATCH 08/10] KVM: Change API of kvm_ioapic_get_delivery_bitmask Sheng Yang
2008-12-30 5:56 ` [PATCH 09/10] KVM: Update intr delivery func to accept unsigned long* bitmap Sheng Yang
2008-12-30 5:56 ` [PATCH 10/10] KVM: bit ops for deliver_bitmap Sheng Yang
2008-12-30 6:01 ` [PATCH 0/10][v3] GSI->MSG route layer for MSI/MSI-X Sheng Yang
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 10:42 [PATCH 0/10][v4]GSI " Sheng Yang
2009-01-07 10:42 ` [PATCH 05/10] KVM: Merge MSI handling to kvm_set_irq Sheng Yang
2009-01-07 21:39 ` Marcelo Tosatti
2009-01-08 9:24 ` Sheng Yang
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=4959FC8A.70808@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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).