From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "qiaonuohan@cn.fujitsu.com" <qiaonuohan@cn.fujitsu.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] hmp interface for kdump compressed format
Date: Fri, 21 Mar 2014 10:38:28 +0100 [thread overview]
Message-ID: <532C0894.5000803@de.ibm.com> (raw)
In-Reply-To: <532C0684.90505@cn.fujitsu.com>
On 21/03/14 10:31, qiaonuohan@cn.fujitsu.com wrote:
[....]
>>> Another option would be to leave the current command intact, and add an
>>> independent command that wouldn't take "begin", "end", nor "paging", but
>>> would take compression format.
>>
>> Another possibility is to kill begin/length from the dump-guest-memory command.
>> HMP is not stable, so if that's useful we can do it.
>
> AFAIK, kdump-compressed format can only be analyzed by crash-utility right
> now. ELF is big but we still need it, then begin/length will help us save
> time and space when only part of the memory is need.
>
> IMHO, a new HMP command will be a good choice and it is more simple than
> making dump format 'stateful'. I am not so clear about HMP, but I think
> the new HMP command can be 'dump-guest-memory-with-format', and still
> base on qmp_dump_guest_memory. If you guys like it, I will send a patch
> that add this command.
Yes, please do, if you find the time.
Maybe user "dump-guest-memory-format" or whatever comes up might be a better name, though.
Thanks a lot
Christian
next prev parent reply other threads:[~2014-03-21 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 20:38 [Qemu-devel] hmp interface for kdump compressed format Christian Borntraeger
2014-03-20 20:56 ` Laszlo Ersek
2014-03-20 21:12 ` Laszlo Ersek
2014-03-20 21:18 ` Christian Borntraeger
2014-03-20 21:28 ` Laszlo Ersek
2014-03-20 21:51 ` Paolo Bonzini
2014-03-21 9:31 ` qiaonuohan
2014-03-21 9:38 ` Christian Borntraeger [this message]
2014-03-26 17:04 ` Markus Armbruster
2014-03-27 1:22 ` qiaonuohan
2014-03-27 8:38 ` Markus Armbruster
2014-04-02 1:54 ` qiaonuohan
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=532C0894.5000803@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaonuohan@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.