From: Avi Kivity <avi@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Jason Baron <jbaron@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] memory: add -dont-dump-guest option to reduce core dump size
Date: Wed, 11 Jul 2012 17:14:32 +0300 [thread overview]
Message-ID: <4FFD8A48.2050607@redhat.com> (raw)
In-Reply-To: <m3ipe1tqxj.fsf@blackfin.pond.sub.org>
On 07/06/2012 08:11 AM, Markus Armbruster wrote:
>
> It seems there could be more knobs to control than just "dump guest
> state yes/no". Therefore, extensible command line syntax like
> "--core-dump guest-ram=off" seems to be advisable. We have too many
> -dont-do-FOO options already.
-m 2T,dump=no
?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-11 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 21:23 [Qemu-devel] [PATCH] memory: add -dont-dump-guest option to reduce core dump size Jason Baron
2012-05-21 17:53 ` Jason Baron
2012-07-06 0:04 ` Marcelo Tosatti
2012-07-06 5:11 ` Markus Armbruster
2012-07-11 14:14 ` Avi Kivity [this message]
2012-07-06 20:26 ` Jason Baron
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=4FFD8A48.2050607@redhat.com \
--to=avi@redhat.com \
--cc=armbru@redhat.com \
--cc=jbaron@redhat.com \
--cc=mtosatti@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).