All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus
Date: Thu, 27 Aug 2009 10:57:26 +0300	[thread overview]
Message-ID: <4A963C66.6040300@redhat.com> (raw)
In-Reply-To: <4A96375D.1070005@redhat.com>

On 08/27/2009 10:35 AM, Gerd Hoffmann wrote:
>>> BTW: Seems linux doesn't use IRQ 5 even with lots of PCI devices,
>>> instead it makes them share 10+11 ...
>>
>> We could change the defaults to include 5, but maybe it makes more sense
>> to fix Linux to distribute active PCI IRQs across the resources it has
>> at its disposal.
>
> i.e. Linux decides to stick with the defaults (starred) here ...
>
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
>
> ... instead of trying to minimize IRQ sharing by using IRQ 5?

Yes.  And if it turns out you have two active devices and 6 inactive 
devices, move the two active devices to private lines and pile up the 
inactive ones on the leftover.

>
>> They'll be slow regardless. I should be easy to support msi on e1000
>> though.
>
> What is needed on the guest side?  Looks like even 2.6.30 doesn't use 
> MSI for virtio-net ...

virtio msi support was merged in 2.6.31.  For e1000, guest support is 
presumably there, just need to wire it into the device.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-08-27  7:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09 16:44 [Qemu-devel] [PATCH 0/2] Disentagle ISA IRQs Avi Kivity
2009-08-09 16:44 ` [Qemu-devel] [PATCH 1/2] Route PC irqs to ISA bus instead of i8259 directly Avi Kivity
2009-08-10  8:34   ` Gerd Hoffmann
2009-08-10  8:46     ` Avi Kivity
2009-08-10  9:04   ` Alexander Graf
2009-08-10  9:43     ` Avi Kivity
2009-08-10  9:45     ` Stefan Assmann
2009-08-10  9:52       ` Avi Kivity
2009-08-10 13:20         ` Olaf Dabrunz
2009-08-10 13:14       ` Olaf Dabrunz
2009-08-09 16:44 ` [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus Avi Kivity
2009-08-10  8:38   ` Gerd Hoffmann
2009-08-26 16:03   ` Gerd Hoffmann
2009-08-26 16:06     ` Avi Kivity
2009-08-26 16:30       ` Gerd Hoffmann
2009-08-26 19:09         ` Gleb Natapov
2009-08-27  7:40           ` Gerd Hoffmann
2009-08-27  7:57             ` Gleb Natapov
2009-08-27  8:18               ` Jamie Lokier
2009-08-27  8:24                 ` Gleb Natapov
2009-08-27  8:55                 ` Gerd Hoffmann
2009-08-27 10:35                   ` Isaku Yamahata
2009-08-27 21:07                   ` [Qemu-devel] " Bjørn Mork
2009-08-27  4:53         ` [Qemu-devel] " Avi Kivity
2009-08-27  7:35           ` Gerd Hoffmann
2009-08-27  7:57             ` Avi Kivity [this message]
2009-08-27  8:13               ` Gerd Hoffmann
2009-08-27  8:26                 ` Avi Kivity
2009-08-28  2:20       ` Beth Kon
2009-08-29 17:47         ` Avi Kivity
2009-08-30  2:09           ` Beth Kon

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=4A963C66.6040300@redhat.com \
    --to=avi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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.