All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI: how handle multifunction / compound devices best?
Date: Fri, 01 Jul 2011 07:19:20 -0500	[thread overview]
Message-ID: <4E0DBB48.30208@codemonkey.ws> (raw)
In-Reply-To: <1309519646-3206-1-git-send-email-kraxel@redhat.com>

On 07/01/2011 06:27 AM, Gerd Hoffmann wrote:
>    Hi folks,
>
> I'm still looking for a sane way to handle multifunction pci devices,
> specifically a EHCI USB controller with UHCI companion controllers.
>
> Here comes a small (incomplete[1]) two patch series to make the issue
> more clear.  The first patch adds a function which creates all devices
> with the properties set as needed.  The second patch adds a '-usb2'
> switch to windup this in a user-friendly way.
>
> Adding a -usb2 switch sucks though.  I'd prefer to have some way to
> create such devices via -device, but without asking the user to create
> all functions individually on the command line, i.e. have something
> along the lines of ...
>
>   qemu -device ich9-usb,slot=08

This is the place where are current infrastructure pretty much stinks.

The first problem is that the device factory interface should be 
involved with device addressing.  We really should have:

qemu -device ich9-usb,id=uhci0 -set i440fx.slot[8]=uhci0

The device doesn't care what it's PCI slot address is.

ich9-usb should be able to create its functions too as part of its 
initialization.  I don't see an easy answer here unless we do away with 
the current bus model.  There's no way we can do composition given the 
bus model we have.

Best we could do is syntactic sugar for what you have below.

Regards,

Anthony Liguori

>
> ... instead of ...
>
>   qemu \
>    -device ich9-usb-ehci1,addr=08.7,multifunction=on,id=ehci \
>    -device ich9-usb-uhci1,addr=08.0,multifunction=on,masterbus=ehci.0,firstport=0 \
>    -device ich9-usb-uhci2,addr=08.1,multifunction=on,masterbus=ehci.0,firstport=2 \
>    -device ich9-usb-uhci3,addr=08.2,multifunction=on,masterbus=ehci.0,firstport=4
>
> Suggestions?
>
> cheers,
>    Gerd
>
> [1] full series @ http://www.kraxel.org/cgit/qemu/log/?h=usb.18
>
> Gerd Hoffmann (2):
>    usb: add ich9_ehci_with_companion_init()
>    usb: windup ich9_ehci_with_companion_init via -usb2 switch.
>
>   hw/pc_piix.c    |   14 ++++++++++----
>   hw/usb-ehci.c   |   49 +++++++++++++++++++++++++++++++++++++++++++++++++
>   hw/usb.h        |    3 +++
>   qemu-options.hx |   13 +++++++++++--
>   vl.c            |    3 +++
>   5 files changed, 76 insertions(+), 6 deletions(-)
>
>

  parent reply	other threads:[~2011-07-01 12:19 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 ` Anthony Liguori [this message]
2011-07-04 15:19   ` [Qemu-devel] PCI: how handle multifunction / compound devices best? Markus Armbruster
2011-07-04 16:09 ` Markus Armbruster
2011-07-05  7:41   ` Gerd Hoffmann

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=4E0DBB48.30208@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.