qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] Transitioning from HMP to QMP for QEMU
Date: Thu, 15 Dec 2011 14:37:38 +0100	[thread overview]
Message-ID: <4EE9F822.4060601@siemens.com> (raw)
In-Reply-To: <4EE9F734.7050305@redhat.com>

On 2011-12-15 14:33, Kevin Wolf wrote:
> Am 15.12.2011 14:18, schrieb Jan Kiszka:
>> On 2011-12-15 14:02, Stefan Hajnoczi wrote:
>>> What is the status of QEMU's transition from HMP to the QMP interface?
>>>
>>> My current understanding is that QEMU provides new HMP commands for
>>> humans, but HMP is being phased out as an API.  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.
>>>
>>> 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.
>>>
>>> Does everyone agree on this?  I think this is an important discussion
>>> if we want our management interface to get better and more consistent
>>> in the future.
>>
>> To phase out the classic HMP implementation, we need an internal
>> HMP-over-JSON wrapper (with tab expansion etc.) so that virtual console
>> and gdbstub monitors continue to benefit from new commands. Those
>> interfaces will stay for a long time, I'm sure.
> 
> I think we're not talking about dropping HMP here, only about how long
> to support it as a stable API for management tools. I believe that we
> have been in a transitional phase for long enough now that we can start
> changing the output format of HMP commands without considering it an API
> breakage.

We are also talking about introducing new commands twice, which is a
PITA. Also, peoples interest in HMP vs. QMP varies. Some focus on
management usability, others on human-machine interaction. So you get
suggestions for new command typical either for one, not for both.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-12-15 13:37 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 [this message]
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

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=4EE9F822.4060601@siemens.com \
    --to=jan.kiszka@siemens.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 \
    --cc=stefanha@gmail.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).