qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	qiaonuohan <qiaonuohan@cn.fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] hmp interface for kdump compressed format
Date: Thu, 20 Mar 2014 22:12:38 +0100	[thread overview]
Message-ID: <532B59C6.5060001@redhat.com> (raw)
In-Reply-To: <532B5607.6060206@redhat.com>

Two additional points:

On 03/20/14 21:56, Laszlo Ersek wrote:
> On 03/20/14 21:38, Christian Borntraeger wrote:
>> Qiao Nuohan,
>>
>> is there a reason why you did not implemented the HMP part for that format
>> of kdump compressed format? After all this is a patch mostly for developers,
>> so a HMP interface might come handy. Do you already have some patch in 
>> preparation or know somebody doing it?
> 
> http://thread.gmane.org/gmane.comp.emulators.qemu/249283/focus=250059

- HMP interface could be implemented as a fully new command of course,

- the feature being targeted at developers strikes me as a completely
unexpected idea. The main goal in my understanding is to allow the
management layer (libvirt) to save a compressed vmcore when the guest
panicks, crashes, or the admin feels like it. For communication with
another program, QMP is actually preferable.

So I'm certainly not against anyone adding a HMP interface too, but it
cannot be an extension to the current HMP command (because it would
break existing HMP command lines unless the HMP parser were reworked
too), plus during review I saw no reason to stall the series even
longer, for a side feature that I perceived to be of low importance (and
I actually thought that Qiao Nuohan shared that notion).

Thanks
Laszlo

  reply	other threads:[~2014-03-20 21:13 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 [this message]
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
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=532B59C6.5060001@redhat.com \
    --to=lersek@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=lcapitulino@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 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).