From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/3] Rework --name to use QemuOpts
Date: Tue, 11 Feb 2014 06:30:01 -0700 [thread overview]
Message-ID: <52FA25D9.9080906@redhat.com> (raw)
In-Reply-To: <52F9E861.9020504@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On 02/11/2014 02:07 AM, Paolo Bonzini wrote:
> Il 10/02/2014 17:12, Laszlo Ersek ha scritto:
>>> > I'd checked every piece of output I'd found, but hadn't found
>>> > the query-command-line-options; I think you're right there
>>> > are no other \n's in there - but also all the other .help texts
>>> > are much briefer and less chatty; maybe I need to just chop
>>> > them down to a minimum, I wonder if there is anywhere they're
>>> > ever displayed to a human?
>> I share your wondering :)
>
> I do too, but I'd wager the answer is no.
Libvirt logs the result of query-command-line-options, including the
human portion associated with the details. And libvirt also exposes the
'virsh qemu-monitor-command' backdoor which can be used by developers to
get at the human-readable information in this query. I _have_ called
query-command-line-options to see what it output, and did appreciate the
human text available there.
But you are correct that in the day-to-day operation of libvirtd, the
human text is ignored - it's there mainly for developers.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-02-11 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 10:20 [Qemu-devel] [PATCH v2 0/3] Name threads Dr. David Alan Gilbert (git)
2014-01-30 10:20 ` [Qemu-devel] [PATCH v2 1/3] Rework --name to use QemuOpts Dr. David Alan Gilbert (git)
2014-02-09 8:43 ` Laszlo Ersek
2014-02-10 10:03 ` Dr. David Alan Gilbert
2014-02-10 16:12 ` Laszlo Ersek
2014-02-11 9:07 ` Paolo Bonzini
2014-02-11 13:30 ` Eric Blake [this message]
2014-01-30 10:20 ` [Qemu-devel] [PATCH v2 2/3] Add 'debug-threads' suboption to --name Dr. David Alan Gilbert (git)
2014-02-09 9:08 ` Laszlo Ersek
2014-02-10 10:16 ` Dr. David Alan Gilbert
2014-02-10 16:14 ` Laszlo Ersek
2014-01-30 10:20 ` [Qemu-devel] [PATCH v2 3/3] Add a 'name' parameter to qemu_thread_create Dr. David Alan Gilbert (git)
2014-02-09 9:37 ` Laszlo Ersek
2014-02-10 9:49 ` Dr. David Alan Gilbert
2014-01-30 12:59 ` [Qemu-devel] [PATCH v2 0/3] Name threads Eric Blake
2014-01-30 13:03 ` Dr. David Alan Gilbert
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=52FA25D9.9080906@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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.