From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: jan.kiszka@siemens.com, aliguori@us.ibm.com,
qemu-devel@nongnu.org, d.hatayama@jp.fujitsu.com,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/3] qmp: dump-guest-memory: improve schema doc (again)
Date: Fri, 21 Sep 2012 12:11:32 -0600 [thread overview]
Message-ID: <505CADD4.5070407@redhat.com> (raw)
In-Reply-To: <1348247243-12446-2-git-send-email-lcapitulino@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On 09/21/2012 11:07 AM, Luiz Capitulino wrote:
> o Add a note about memory allocation with paging=true
> o Fix indentation
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> qapi-schema.json | 32 ++++++++++++++++++++------------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 14e4419..3d93ebe 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -1982,26 +1982,33 @@
> # supported on i386 and x86_64.
> #
> # @paging: if true, do paging to get guest's memory mapping. This allows
> -# using gdb to process the core file. However, setting @paging to false
> -# may be desirable because of two reasons:
> +# using gdb to process the core file.
You've got a TAB in there, that made it hard to see what the intended
indentation really is. The rest of the file doesn't have TABs, so you
need to respin this.
> +# IMPORTANT: this option can make QEMU allocates several gigabytes
s/allocates/allocate/
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 617 bytes --]
next prev parent reply other threads:[~2012-09-21 18:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 17:07 [Qemu-devel] [PATCH 0/3]: qmp/hmp: dump-guest-memory fixes Luiz Capitulino
2012-09-21 17:07 ` [Qemu-devel] [PATCH 1/3] qmp: dump-guest-memory: improve schema doc (again) Luiz Capitulino
2012-09-21 18:11 ` Eric Blake [this message]
2012-09-21 17:07 ` [Qemu-devel] [PATCH 2/3] qmp: dump-guest-memory: don't spin if non-blocking fd would block Luiz Capitulino
2012-09-21 18:30 ` Eric Blake
2012-09-24 6:27 ` Wen Congyang
2012-09-24 13:34 ` Luiz Capitulino
2012-09-25 8:19 ` Wen Congyang
2012-09-25 9:01 ` Markus Armbruster
2012-09-25 9:13 ` Wen Congyang
2012-09-25 9:14 ` Wen Congyang
2012-09-21 17:07 ` [Qemu-devel] [PATCH 3/3] hmp: dump-guest-memory: hardcode protocol argument to file: Luiz Capitulino
2012-09-21 18:13 ` Eric Blake
2012-09-25 8:48 ` Markus Armbruster
2012-09-25 12:02 ` Luiz Capitulino
2012-09-25 10:10 ` Wen Congyang
2012-09-25 8:54 ` [Qemu-devel] [PATCH 0/3]: qmp/hmp: dump-guest-memory fixes Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 18:56 [Qemu-devel] [PATCH v2 0/3] " Luiz Capitulino
2012-09-26 18:56 ` [Qemu-devel] [PATCH 1/3] qmp: dump-guest-memory: improve schema doc (again) Luiz Capitulino
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=505CADD4.5070407@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@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).