From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] qdev: add -pcidevice command line option.
Date: Mon, 29 Jun 2009 09:51:31 -0500 [thread overview]
Message-ID: <4A48D4F3.3030200@codemonkey.ws> (raw)
In-Reply-To: <1246286263-27970-1-git-send-email-kraxel@redhat.com>
Gerd Hoffmann wrote:
> Ok, lets start to collect some low-hanging fruit we can get from the
> qdev bits even at the current early state.
>
> ==> stop adding cmd line switches for each and every device <==
> ==> do funky stuff you could not do before <==
>
> Here is a patch adding a generic -pcidevice command line switch. Works
> only for qdev-converted devices. Works (for now) only for devices which
> don't need configuration (i.e. nics don't work or maybe use vlan0
> unconditionally). Most useful with my qdev patch queue applied.
>
> Examples:
>
> -pcidevice ES1370,addr=42 (replaces -audio es1370).
> -pcidevice virtio-balloon-pci (replaces -balloon).
> -pcidevice lsi53c895a,addr=23 (add scsi adapter in specified slot).
> -pcidevice "PIIX3 USB-UHCI" (add second usb bus).
>
> Comments?
>
You read my mind :-)
I was just thinking about this as I was looking over staging.
What I would like to see is that this internal mechanism be used to
implement the switches it replaces. That is, -balloon should just add
just be a convenience option that expands to -pcidevice. The same for
-audio.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-29 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:37 [Qemu-devel] [RFC PATCH] qdev: add -pcidevice command line option Gerd Hoffmann
2009-06-29 14:51 ` Anthony Liguori [this message]
2009-06-30 7:55 ` Gerd Hoffmann
2009-06-29 21:02 ` Markus Armbruster
2009-06-30 8:00 ` Gerd Hoffmann
2009-06-30 9:29 ` Gerd Hoffmann
2009-06-30 11:16 ` Paul Brook
2009-06-30 13:37 ` Markus Armbruster
2009-06-30 15: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=4A48D4F3.3030200@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@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 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).