From: Mark McLoughlin <markmc@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 5/5] monitor: add "info capabilities" command
Date: Fri, 14 Nov 2008 16:02:43 +0000 [thread overview]
Message-ID: <1226678563.9332.98.camel@blaa> (raw)
In-Reply-To: <491C8520.5040005@codemonkey.ws>
On Thu, 2008-11-13 at 13:50 -0600, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > +static void do_info_capabilities(void)
> > +{
> > + term_printf("[qemu]\n");
> > + list_printf("accel", accel_names);
> > + term_printf("arch=%s\n", TARGET_ARCH);
> > + list_printf("cpu", cpu_names());
> > + machines_printf();
> > +
> > + term_printf("\n");
> > +
> > + do_machine_capabilities();
> > +
> > + term_printf("[devices]\n");
> > + list_printf("bluetooth", bt_list_types());
> > + list_printf("char", qemu_chr_list_types());
> > + list_printf("drive_cache", drive_cache_types());
> > + list_printf("drive_if", drive_if_types());
> > + list_printf("graphics", graphics_list_types());
> > + list_printf("network", net_client_types());
> > +#ifdef HAS_AUDIO
> > + list_printf("soundhw", soundhw_list_types());
> > +#endif
> > + list_printf("vga", vga_list_types());
> > +
> > + term_printf("\n");
> >
>
> This makes me uneasy because it introduces a lot of dependencies that
> are going to be hard to break. I think this level of logic needs to be
> more encapsulated in the various subsystems.
So, something like have [network], [block], [audio] etc. sections and
call out to network_capabilities() etc.?
Cheers,
Mark.
next prev parent reply other threads:[~2008-11-14 16:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 16:45 [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command Mark McLoughlin
2008-11-13 16:45 ` [Qemu-devel] [PATCH 1/5] Re-factor nic model listing Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 2/5] Add cpu_list() for any targets that don't already have it Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 3/5] Rename xxx_cpu_list() to cpu_xxx_list() Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 4/5] Add new cpu_names() function Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 5/5] monitor: add "info capabilities" command Mark McLoughlin
2008-11-13 19:50 ` [Qemu-devel] " Anthony Liguori
2008-11-14 16:02 ` Mark McLoughlin [this message]
2008-11-14 10:07 ` [Qemu-devel] " Avi Kivity
2008-11-14 15:58 ` Mark McLoughlin
2008-11-16 7:17 ` Avi Kivity
2008-11-14 10:13 ` Daniel P. Berrange
2008-11-13 19:47 ` [Qemu-devel] Re: [PATCH 4/5] Add new cpu_names() function Anthony Liguori
2008-11-14 15:36 ` Mark McLoughlin
2008-11-13 18:35 ` [Qemu-devel] [PATCH 1/5] Re-factor nic model listing Paul Brook
2008-11-13 19:45 ` Anthony Liguori
2008-11-13 22:50 ` Paul Brook
2008-11-14 2:31 ` Jamie Lokier
2008-11-14 2:49 ` Anthony Liguori
2008-11-13 19:44 ` [Qemu-devel] " Anthony Liguori
2008-11-14 15:34 ` Mark McLoughlin
2008-11-13 17:49 ` [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command Blue Swirl
2008-11-14 2:50 ` Jamie Lokier
2008-11-14 16:09 ` Mark McLoughlin
2008-11-14 3:28 ` [Qemu-devel] " Anthony Liguori
2008-11-14 3:51 ` Jamie Lokier
2008-11-14 15:56 ` Mark McLoughlin
2008-11-14 22:54 ` Jamie Lokier
2008-11-14 15:51 ` Mark McLoughlin
2008-11-14 22:52 ` Jamie Lokier
2008-11-14 10:16 ` [Qemu-devel] " Daniel P. Berrange
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=1226678563.9332.98.camel@blaa \
--to=markmc@redhat.com \
--cc=anthony@codemonkey.ws \
--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.