From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] Add '-device help' output for device params and help text
Date: Mon, 07 Jun 2010 11:09:32 -0500 [thread overview]
Message-ID: <4C0D19BC.6030305@codemonkey.ws> (raw)
In-Reply-To: <cover.1275309375.git.amit.shah@redhat.com>
On 05/31/2010 07:41 AM, Amit Shah wrote:
> Hello,
>
> This patch series adds support to specify some descriptive help text
> to qdev device parameters. This series adds some help text to the
> virtserialport and net family of devices as an example, and the new
> output is shown in the respective commits.
>
> This series also adds a new '-device help' option that lists all the
> available qdev devices (which is avl. via -device ? now), and adds
> each device's parameters to the output listing. This output also shows
> the descriptive text.
>
> The idea is to auto-generate documentation from code and to populate
> some wiki / qemu-doc.texi using this new target.
>
I really dislike having options print their own help.
Maybe we can introduce a proper -help option that takes an argument that
can display subsystem specific help?
For instance:
qemu -help device
Would display the help output in this series.
My other concern is that we now have a big mess of properties that don't
have help text. What are the chances that anyone is going to go through
and do this?
I'd rather we bite the bullet and add help everywhere before merging any
of this because experience has shown that existing code usually never
gets converted if not converted all at once.
Regards,
Anthony Liguori
> Changes from previous send:
> - Removed the 'RFC' tag
> - Not using macros in net.h (Markus)
>
> It'll be helpful to have people submit some short descriptive text for
> the subsystems they care about.
>
> Amit Shah (5):
> qdev: Add a description field for qdev properties for documentation
> virtio-serial: Add description fields for qdev properties
> net.h: Add description fields for qdev properites
> qdev: Re-arrange code to have device properties shown from own
> function
> qdev: Add new '-device help' option, shows all devices and properties
>
> block_int.h | 10 +++---
> hw/a9mpcore.c | 2 +-
> hw/acpi_piix4.c | 2 +-
> hw/arm11mpcore.c | 4 +-
> hw/arm_sysctl.c | 4 +-
> hw/armv7m.c | 2 +-
> hw/cs4231a.c | 6 ++--
> hw/debugcon.c | 6 ++--
> hw/eccmemctl.c | 2 +-
> hw/escc.c | 16 +++++-----
> hw/etraxfs_pic.c | 3 +-
> hw/fdc.c | 10 +++---
> hw/gus.c | 8 ++--
> hw/i2c.c | 2 +-
> hw/ide/cmd646.c | 2 +-
> hw/ide/isa.c | 6 ++--
> hw/ide/qdev.c | 4 +-
> hw/integratorcp.c | 2 +-
> hw/lance.c | 2 +-
> hw/m48t59.c | 12 ++++----
> hw/mc146818rtc.c | 2 +-
> hw/ne2000-isa.c | 4 +-
> hw/parallel.c | 8 ++--
> hw/pci.c | 10 +++---
> hw/qdev-addr.h | 4 +-
> hw/qdev.c | 51 +++++++++++++++++++++------------
> hw/qdev.h | 75 ++++++++++++++++++++++++++-----------------------
> hw/s390-virtio-bus.c | 2 +-
> hw/sb16.c | 10 +++---
> hw/scsi-bus.c | 2 +-
> hw/scsi-disk.c | 2 +-
> hw/serial.c | 8 ++--
> hw/slavio_timer.c | 2 +-
> hw/smbus_eeprom.c | 2 +-
> hw/sparc32_dma.c | 2 +-
> hw/sun4m.c | 2 +-
> hw/sun4m_iommu.c | 2 +-
> hw/sun4u.c | 2 +-
> hw/syborg_fb.c | 4 +-
> hw/syborg_interrupt.c | 2 +-
> hw/syborg_keyboard.c | 2 +-
> hw/syborg_pointer.c | 4 +-
> hw/syborg_serial.c | 2 +-
> hw/syborg_timer.c | 2 +-
> hw/tcx.c | 10 +++---
> hw/usb-ohci.c | 4 +-
> hw/usb-serial.c | 12 ++++----
> hw/vga-pci.c | 4 +-
> hw/virtio-blk.h | 4 +-
> hw/virtio-console.c | 19 ++++++++----
> hw/virtio-net.h | 51 +++++++++++++++++++++------------
> hw/virtio-pci.c | 16 +++++-----
> hw/virtio-serial.h | 13 ++++++++
> hw/virtio.h | 2 +-
> hw/xilinx_ethlite.c | 6 ++-
> hw/xilinx_intc.c | 3 +-
> hw/xilinx_timer.c | 4 +-
> net.h | 9 ++++--
> usb-linux.c | 8 ++--
> 59 files changed, 268 insertions(+), 208 deletions(-)
>
>
>
next prev parent reply other threads:[~2010-06-07 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 12:41 [Qemu-devel] [PATCH 0/5] Add '-device help' output for device params and help text Amit Shah
2010-05-31 12:41 ` [Qemu-devel] [PATCH 1/5] qdev: Add a description field for qdev properties for documentation Amit Shah
2010-05-31 12:41 ` [Qemu-devel] [PATCH 2/5] virtio-serial: Add description fields for qdev properties Amit Shah
2010-05-31 12:41 ` [Qemu-devel] [PATCH 3/5] net.h: Add description fields for qdev properites Amit Shah
2010-05-31 12:41 ` [Qemu-devel] [PATCH 4/5] qdev: Re-arrange code to have device properties shown from own function Amit Shah
2010-05-31 12:41 ` [Qemu-devel] [PATCH 5/5] qdev: Add new '-device help' option, shows all devices and properties Amit Shah
2010-06-07 14:43 ` Markus Armbruster
2010-06-08 5:13 ` Amit Shah
2010-06-07 16:09 ` Anthony Liguori [this message]
2010-06-08 5:21 ` [Qemu-devel] [PATCH 0/5] Add '-device help' output for device params and help text Amit Shah
2010-06-14 16:55 ` Anthony Liguori
2010-06-15 9:17 ` Markus Armbruster
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=4C0D19BC.6030305@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).