qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
	Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] Transitioning from HMP to QMP for QEMU
Date: Thu, 15 Dec 2011 14:23:54 +0000	[thread overview]
Message-ID: <CAJSP0QWK-0g-da0Jt11nxpr5ENPdAGRvcsTbmBCJbvkZqshE5g@mail.gmail.com> (raw)
In-Reply-To: <20111215115731.3ee45e4b@doriath>

On Thu, Dec 15, 2011 at 1:57 PM, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Thu, 15 Dec 2011 13:02:40 +0000
> Stefan Hajnoczi <stefanha@gmail.com> wrote:
>
>> What is the status of QEMU's transition from HMP to the QMP interface?
>
> Depends on what you consider the transition to be.
>
> For management tools the transition can be considered done already because we
> do not support HMP as a stable interface.
>
>> My current understanding is that QEMU provides new HMP commands for
>> humans, but HMP is being phased out as an API.
>
> It already did.
>
>>  Management tools
>> should rely only on QMP for new commands.  That would mean new HMP
>> commands are not guaranteed to produce backwards-compatible output
>> because tools are not supposed to parse the output.
>
> Exactly.
>
>> On the libvirt side, new QEMU features should only be supported via
>> the json monitor in the future (i.e. human monitor patches should not
>> be sent/merged)? Existing HMP commands will still need the human
>> monitor support in order to handle old QEMU versions gracefully, but
>> I'm thinking about new commands only.
>
> Maybe it's a matter of terminology, but I have the impression you're
> talking about two things here:
>
>  1. HMP will always exist, in the meaning that qemu will always provide
>    a human interface. If we move it to a python script or some kind of
>    external process, that's an implementation detail.
>
>    This means that, if you're adding new functionality to qemu and it
>    does make sense for humans to use it, then it should have a HMP
>    version.
>
>  2. If you do add the HMP interface, that's for humans to consume and
>    its output/semantics should make sense for humans, not for management tools.

This entire email is useful, thanks.  It feels like this should be
captured somewhere - on the wiki, in qemu/doc/, or as a comment in
monitor.c.  That way anyone who wishes to contribute new monitor
commands will start with the right idea.

Stefan

      parent reply	other threads:[~2011-12-15 14:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 13:02 [Qemu-devel] Transitioning from HMP to QMP for QEMU Stefan Hajnoczi
2011-12-15 13:18 ` Jan Kiszka
2011-12-15 13:33   ` Kevin Wolf
2011-12-15 13:37     ` Jan Kiszka
2011-12-15 13:38     ` Lucas Meneghel Rodrigues
2011-12-15 13:39       ` Jan Kiszka
2011-12-15 13:45         ` Stefan Hajnoczi
2011-12-15 13:49         ` Kevin Wolf
2011-12-15 13:53           ` Stefan Hajnoczi
2011-12-15 13:57             ` Jan Kiszka
2011-12-15 15:01               ` Luiz Capitulino
2011-12-15 13:31 ` [Qemu-devel] [libvirt] " Stefan Berger
2011-12-15 13:57 ` [Qemu-devel] " Luiz Capitulino
2011-12-15 14:06   ` Anthony Liguori
2011-12-15 14:52     ` Luiz Capitulino
2011-12-15 14:57       ` Anthony Liguori
2011-12-15 14:23   ` Stefan Hajnoczi [this message]

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=CAJSP0QWK-0g-da0Jt11nxpr5ENPdAGRvcsTbmBCJbvkZqshE5g@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=agl@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=libvir-list@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).