From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Isaku Yamahata <yamahata@valinux.co.jp>
Subject: Re: [Qemu-devel] [Xen-devel] Re: [PATCH] xen: fix interrupt routing
Date: Wed, 15 Jun 2011 19:34:25 +0300 [thread overview]
Message-ID: <4DF8DF11.1030206@redhat.com> (raw)
In-Reply-To: <DCAB4C78-3A84-41F0-8074-3E2712F60EE4@suse.de>
On 06/15/2011 11:24 AM, Alexander Graf wrote:
> I'm actually not quite sure what exactly he's describing here. But if it's bypassing the bus logic, it's not a normal PCI device :). Sure, there are special case devices that also expose a PCI interface. But real PCI cards that you plug in onto the PCI bus can't bypass the interrupt logic of the bus, as the only interrupt wires they have go to the bus. And since the PCI adapters we use in PC machines in Qemu are all non-special, guests can possibly choke on this.
>
There actually is a special device in qemu - acpi power management is
configured as a PCI device, but its interrupt is hard-wired to gsi 9 and
is edge-triggered (so it can't share the irq line).
I other devices that are special in this regard to also be part of the
chipset, not devices you can plug into arbitrary slots.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-15 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 15:48 [Qemu-devel] [PATCH] xen: fix interrupt routing Stefano Stabellini
2011-05-27 23:17 ` Alexander Graf
2011-05-31 11:05 ` Stefano Stabellini
2011-06-14 9:25 ` Alexander Graf
2011-06-14 12:17 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2011-06-14 12:30 ` Alexander Graf
2011-06-14 13:08 ` [Qemu-devel] " Jan Kiszka
2011-06-14 13:31 ` Stefano Stabellini
2011-06-14 13:27 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2011-06-14 15:30 ` [Qemu-devel] " Jan Kiszka
2011-06-14 18:18 ` Stefano Stabellini
2011-06-15 8:24 ` Alexander Graf
2011-06-15 16:34 ` Avi Kivity [this message]
2011-06-15 16:54 ` [Qemu-devel] [Xen-devel] " Alexander Graf
2011-06-15 8:16 ` Alexander Graf
2011-06-15 16:32 ` Stefano Stabellini
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=4DF8DF11.1030206@redhat.com \
--to=avi@redhat.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=agraf@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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).