From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, tumanova@linux.vnet.ibm.com,
agraf@suse.de, qemu-devel@nongnu.org, rabin@rab.in,
borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [RFC qom-cpu] dump: Unconditionally compile
Date: Mon, 20 May 2013 22:44:31 +0200 [thread overview]
Message-ID: <519A8B2F.7050702@suse.de> (raw)
In-Reply-To: <5196109A.30208@redhat.com>
Am 17.05.2013 13:12, schrieb Paolo Bonzini:
> Il 17/05/2013 12:58, Andreas Färber ha scritto:
>> qmp_dump_guest_memory() calls dump_init() and returns an Error when
>> cpu_get_dump_info() returns an error, as done by the stub.
>> So there is no need to have a stub for qmp_dump_guest_memory().
>>
>> Enable the documentation of the always-present dump-guest-memory command.
>>
>> That way we can drop CONFIG_HAVE_CORE_DUMP.
>
> Nicer. :)
Thanks, applied to qom-cpu:
https://github.com/afaerber/qemu-cpu/commits/qom-cpu
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-20 20:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:30 [Qemu-devel] [PATCH 0/2] s390: dump-guest-memory support Jens Freimann
2013-04-23 15:30 ` [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code Jens Freimann
2013-04-23 15:41 ` Eric Blake
2013-04-23 15:54 ` Jens Freimann
2013-05-17 10:18 ` Andreas Färber
2013-04-24 15:50 ` Luiz Capitulino
2013-04-24 16:23 ` Eric Blake
2013-04-24 17:25 ` Luiz Capitulino
2013-04-24 17:07 ` Ekaterina Tumanova
2013-04-24 19:57 ` Eric Blake
2013-05-17 10:58 ` [Qemu-devel] [RFC qom-cpu] dump: Unconditionally compile Andreas Färber
2013-05-17 11:12 ` Paolo Bonzini
2013-05-20 20:44 ` Andreas Färber [this message]
2013-04-23 15:30 ` [Qemu-devel] [PATCH 2/2] s390: dump guest memory implementation Jens Freimann
2013-04-26 17:12 ` Alexander Graf
2013-04-29 11:39 ` Ekaterina Tumanova
2013-04-30 10:02 ` Alexander Graf
2013-04-30 10:20 ` Ekaterina Tumanova
2013-04-30 10:25 ` Alexander Graf
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=519A8B2F.7050702@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rabin@rab.in \
--cc=tumanova@linux.vnet.ibm.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).