From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI: how handle multifunction / compound devices best?
Date: Tue, 05 Jul 2011 09:41:32 +0200 [thread overview]
Message-ID: <4E12C02C.2010603@redhat.com> (raw)
In-Reply-To: <m3fwmmf2o3.fsf@blackfin.pond.sub.org>
Hi,
> Device macros destroy the 1:1 relationship between -device and device
> tree nodes. Or rather what's left of it: we already have a device that
> expands into multiple devices, namely usb-storage. But it's an ad hoc
> hack, which has caused us some grief.
Exactly thats why I don't feel like adding more ad hoc hacks ...
cheers,
Gerd
prev parent reply other threads:[~2011-07-05 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 11:27 [Qemu-devel] PCI: how handle multifunction / compound devices best? Gerd Hoffmann
2011-07-01 11:27 ` [Qemu-devel] [PATCH 1/2] usb: add ich9_ehci_with_companion_init() Gerd Hoffmann
2011-07-01 11:27 ` [Qemu-devel] [PATCH 2/2] usb: windup ich9_ehci_with_companion_init via -usb2 switch Gerd Hoffmann
2011-07-01 12:19 ` [Qemu-devel] PCI: how handle multifunction / compound devices best? Anthony Liguori
2011-07-04 15:19 ` Markus Armbruster
2011-07-04 16:09 ` Markus Armbruster
2011-07-05 7:41 ` Gerd Hoffmann [this message]
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=4E12C02C.2010603@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@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.