From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: amit.shah@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
agraf@suse.de
Subject: Re: [Qemu-devel] [RFC] vmstate: Add info vmstate HMP command (WIP)
Date: Fri, 1 Nov 2013 10:32:28 -0400 [thread overview]
Message-ID: <20131101103228.4e58ef95@redhat.com> (raw)
In-Reply-To: <1382628890-3701-1-git-send-email-afaerber@suse.de>
On Thu, 24 Oct 2013 16:34:50 +0100
Andreas Färber <afaerber@suse.de> wrote:
> This adds a command "info vmstate" for dumping a textual representation
> of the currently registered VMStateDescriptions.
>
> Being purely for debugging, intentionally no QMP schema is set in stone.
We had a discussion in the past about prefixing such QMP commands with
x- or adding a special vendor extension for them. I don't remember the
conclusion there, although I see that we do have x-rdma-pin-all in the
schema.
prev parent reply other threads:[~2013-11-01 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 15:34 [Qemu-devel] [RFC] vmstate: Add info vmstate HMP command (WIP) Andreas Färber
2013-11-01 14:32 ` Luiz Capitulino [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=20131101103228.4e58ef95@redhat.com \
--to=lcapitulino@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).