qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgaluk" <Pavel.Dovgaluk@ispras.ru>
To: 'Eric Blake' <eblake@redhat.com>,
	'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH 08/22] Monitor commands
Date: Wed, 2 Jul 2014 14:43:23 +0400	[thread overview]
Message-ID: <014b01cf95e2$72e3e840$58abb8c0$@Dovgaluk@ispras.ru> (raw)
In-Reply-To: <53B2F0CC.6010001@redhat.com>

> -----Original Message-----
> From: Eric Blake [mailto:eblake@redhat.com]
> Sent: Tuesday, July 01, 2014 9:33 PM
> To: Pavel Dovgaluk; 'QEMU Developers'
> Subject: Re: [Qemu-devel] [RFC PATCH 08/22] Monitor commands
> 
> On 07/01/2014 05:23 AM, Pavel Dovgaluk wrote:
> > This patch adds commands to control replay from the monitor.
> >
> > Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@gmail.com>
> > ---
> 
> What are the counterpart QMP commands?  It is seldom right to add an HMP
> command unless the same thing can be done via QMP.

We haven't controlled qemu through QMP yet, thus haven't implemented QMP support
for replay commands.

Today I started adding this support and noticed, that QMP in current master branch is
broken - it does not reply anything except information at start.

> > @@ -2596,6 +2734,7 @@ int monitor_handle_fd_param2(Monitor *mon, const char *fdname, Error
> **errp)
> >      return fd;
> >  }
> >
> > +
> >  /* Please update hmp-commands.hx when adding or changing commands */
> >  static mon_cmd_t info_cmds[] = {
> 
> Spurious newline addition?

Thanks, forgot to undo this.

Pavel Dovgaluk

  reply	other threads:[~2014-07-02 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 11:23 [Qemu-devel] [RFC PATCH 08/22] Monitor commands Pavel Dovgaluk
2014-07-01 17:33 ` Eric Blake
2014-07-02 10:43   ` Pavel Dovgaluk [this message]
2014-07-02 10:54     ` Kirill Batuzov

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='014b01cf95e2$72e3e840$58abb8c0$@Dovgaluk@ispras.ru' \
    --to=pavel.dovgaluk@ispras.ru \
    --cc=eblake@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).