From: Eduardo Habkost <ehabkost@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
pkrempa@redhat.com, Michal Privoznik <mprivozn@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 5/7] hmp: Add info commands for preconfig
Date: Wed, 13 Jun 2018 10:44:23 -0300 [thread overview]
Message-ID: <20180613134423.GP7451@localhost.localdomain> (raw)
In-Reply-To: <871sdcxzej.fsf@dusky.pond.sub.org>
On Tue, Jun 12, 2018 at 09:00:20AM +0200, Markus Armbruster wrote:
> Igor Mammedov <imammedo@redhat.com> writes:
>
> > On Mon, 11 Jun 2018 15:40:16 -0300
> > Eduardo Habkost <ehabkost@redhat.com> wrote:
> >
> >> On Mon, Jun 11, 2018 at 02:01:52PM +0200, Markus Armbruster wrote:
> >> > * Eduardo, why does "info numa" have no QMP equivalent?
> >>
> >> Nobody ever asked for one, which seems to qualify as "only for
> >> human users".
> >>
> >> Should we add an equivalent QMP command even if we don't expect
> >> anybody to use it?
>
> The hard requirement for QMP from day one was "provide everything
> machine clients need". To avoid speculation and endless arguments about
> what might be needed / not needed, we resolved to approximate this by
> "provide everything, except stuff that's *clearly* of no use to
> machines".
>
> When you think a command is such an exception, you should explain why in
> its commit message.
It's not an exception nor it needs to be one. I was just not
aware of the above approximation.
>
> Note that HMP need not provide the functionality in the exact same
> packaging. For instance, it's fine to have building blocks in QMP, and
> just a high-level command in HMP. However, the latter must be
> implemented with the building blocks to make it obvious that QMP
> provides the same functionality.
>
> For additional references, see
> Message-ID: <87d0x1p6go.fsf@dusky.pond.sub.org>
> https://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg02176.html
>
> > we inderectly can fetch numa info via QMP, using
> > query-hotpluggable-cpus
> > for CPU mapping and
> > query-memory-devices
> > for (NV|PC)-dimm devices, however there is no QMP way for getting
> > for numa mapping of initial RAM nor configured numa nodes
> > (not counting querying CLI options).
>
> Sounds like most of the building blocks are already there. The
> "obviousness" isn't.
>
> > So perhaps we need info 'numa' equivalent for QMP which would give
> > the same amount of information as HMP in one query.
>
> I'd appreciate patches to get us to "QMP has the building blocks, and
> HMP is implemented with them".
Agreed.
--
Eduardo
next prev parent reply other threads:[~2018-06-13 13:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 13:08 [Qemu-devel] [PATCH v3 0/7] Reenable hmp for preconfig mode Dr. David Alan Gilbert (git)
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 1/7] hmp: Add flag for preconfig commands Dr. David Alan Gilbert (git)
2018-06-11 8:49 ` Markus Armbruster
2018-06-11 17:37 ` Dr. David Alan Gilbert
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 2/7] hmp: Allow help on " Dr. David Alan Gilbert (git)
2018-06-11 9:00 ` Markus Armbruster
2018-06-11 10:27 ` Dr. David Alan Gilbert
2018-06-11 13:18 ` Markus Armbruster
2018-06-11 18:49 ` Dr. David Alan Gilbert
2018-06-12 7:03 ` Markus Armbruster
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 3/7] hmp: Restrict auto-complete in preconfig Dr. David Alan Gilbert (git)
2018-06-11 9:02 ` Markus Armbruster
2018-06-11 17:38 ` Dr. David Alan Gilbert
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 4/7] qmp: enable query-[chardev|version|name|uuid|iothreads|memdev] commands in preconfig state Dr. David Alan Gilbert (git)
2018-06-11 11:28 ` Markus Armbruster
2018-06-11 17:43 ` Dr. David Alan Gilbert
2018-06-12 7:05 ` Markus Armbruster
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 5/7] hmp: Add info commands for preconfig Dr. David Alan Gilbert (git)
2018-06-11 12:01 ` Markus Armbruster
2018-06-11 17:49 ` Dr. David Alan Gilbert
2018-06-12 5:37 ` Gerd Hoffmann
2018-06-12 12:00 ` Markus Armbruster
2018-06-12 12:52 ` Dr. David Alan Gilbert
2018-06-15 16:10 ` [Qemu-devel] Abandon our QMP first policy? (was: [PATCH v3 5/7] hmp: Add info commands for preconfig) Markus Armbruster
2018-06-15 16:32 ` Dr. David Alan Gilbert
2018-06-15 18:44 ` Eduardo Habkost
2018-06-18 6:36 ` Gerd Hoffmann
2018-06-20 14:48 ` Dr. David Alan Gilbert
2018-06-12 6:43 ` [Qemu-devel] [PATCH v3 5/7] hmp: Add info commands for preconfig Markus Armbruster
2018-06-12 8:49 ` Dr. David Alan Gilbert
2018-06-13 13:47 ` Eduardo Habkost
2018-06-13 13:53 ` Daniel P. Berrangé
2018-06-13 16:59 ` Eduardo Habkost
2018-06-11 18:40 ` Eduardo Habkost
2018-06-11 21:33 ` Igor Mammedov
2018-06-12 7:00 ` Markus Armbruster
2018-06-13 13:44 ` Eduardo Habkost [this message]
2018-06-12 7:57 ` Daniel P. Berrangé
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 6/7] hmp: add exit_preconfig Dr. David Alan Gilbert (git)
2018-06-11 12:04 ` Markus Armbruster
2018-06-11 18:29 ` Dr. David Alan Gilbert
2018-06-08 13:08 ` [Qemu-devel] [PATCH v3 7/7] hmp: Allow HMP in preconfig state again Dr. David Alan Gilbert (git)
2018-06-11 12:06 ` [Qemu-devel] [PATCH v3 0/7] Reenable hmp for preconfig mode Markus Armbruster
2018-06-11 12:09 ` Dr. David Alan Gilbert
2018-06-11 12:44 ` Markus Armbruster
2018-06-14 13:17 ` Igor Mammedov
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=20180613134423.GP7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pkrempa@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.