From: Avi Kivity <avi@qumranet.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>, Jes Sorensen <jes@sgi.com>,
kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [RFC] kvm irq assignment
Date: Fri, 13 Jun 2008 17:22:49 +0300 [thread overview]
Message-ID: <485282B9.7040709@qumranet.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE201CC9210@pdsmsx412.ccr.corp.intel.com>
Xu, Anthony wrote:
> Hi Avi and all
>
> This is the revised one,
>
> All PCI devices send interrupt to both PIC and IOAPIC,
> a). When PIC is enabled and IOAPIC is disabled, all redirect entries in
> IOAPIC are masked.
> B) When PIC is disabled and IPAPIC is enabled, link entry bit7 is set,
> means this link entry is disable.
> Guest OS need to guarantee PIC and IOAPIC are not enabled in the same
> time. Otherwise cause many suspicious interrupt to guest.
>
> Test by running guest linux in kvm/ia32 and kvm/ia64.
>
>
>
Looks good.
> diff --git a/qemu/hw/apic.c b/qemu/hw/apic.c
> index a14cab2..c3014fa 100644
> --- a/qemu/hw/apic.c
> +++ b/qemu/hw/apic.c
> @@ -1053,9 +1053,25 @@ static void ioapic_service(IOAPICState *s)
> }
> }
>
> +int ioapic_map_irq(int devfn, int irq_num)
> +{
> + int irq;
> + irq = ((devfn >> 3) & 7) + 16;
> + return irq;
> +}
> +#ifdef KVM_CAP_IRQCHIP
> +static int ioapic_irq_count[IOAPIC_NUM_PINS];
> +#endif
> +
> void ioapic_set_irq(void *opaque, int vector, int level)
> {
> IOAPICState *s = opaque;
> +#ifdef KVM_CAP_IRQCHIP
> + ioapic_irq_count[vector] += level;
> + if (kvm_enabled())
> + if (kvm_set_irq(vector, ioapic_irq_count[vector] == 0))
> + return;
> +#endif
>
I think this can be done more cleanly using the qemu_irq infrastructure.
qem_irq_invert can do the inversion, and to get the "irq fork", you can
have a qemu_irq instance that forwards its argument to two other
qemu_irq instances.
There shouldn't be any #ifdef KVM_CAP_IRQCHIPs in there - it should work
for plain qemu as well (well, if we fix qemu ioapic polarity code).
> diff --git a/qemu/hw/piix_pci.c b/qemu/hw/piix_pci.c
> index 90cb3a6..96316ca 100644
> --- a/qemu/hw/piix_pci.c
> +++ b/qemu/hw/piix_pci.c
> @@ -225,6 +226,9 @@ static void piix3_set_irq(qemu_irq *pic, int
> irq_num, int level)
> /* now we change the pic irq level according to the piix irq
> mappings */
> /* XXX: optimize */
> pic_irq = piix3_dev->config[0x60 + irq_num];
> + /* if bit7 set 1, this link is disabled */
> + if (pic_irq & 0x80)
> + return;
>
Already caught by the test below... hacky.
> if (pic_irq < 16) {
> /* The pic level is the logical OR of all the PCI irqs mapped
> to it */
>
>
>
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-06-13 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:39 [RFC] kvm irq assignment Xu, Anthony
2008-06-12 19:16 ` Avi Kivity
2008-06-13 2:45 ` Xu, Anthony
2008-06-13 6:38 ` Xu, Anthony
2008-06-13 14:22 ` Avi Kivity [this message]
2008-06-16 1:36 ` Xu, Anthony
2008-06-14 23:32 ` Marcelo Tosatti
2008-06-16 1:34 ` Xu, Anthony
2008-06-16 5:31 ` Xu, Anthony
2008-06-16 15:52 ` Marcelo Tosatti
[not found] ` <3073362C-AF0F-4DBC-989C-AAA5E2875BDF@suse.de>
2008-06-16 1:26 ` Xu, Anthony
2008-06-16 5:40 ` Xu, Anthony
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=485282B9.7040709@qumranet.com \
--to=avi@qumranet.com \
--cc=agraf@suse.de \
--cc=anthony.xu@intel.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.org \
--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