qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jason Baron <jbaron@redhat.com>
Cc: avi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] memory: add -dont-dump-guest option to reduce core dump size
Date: Thu, 5 Jul 2012 21:04:18 -0300	[thread overview]
Message-ID: <20120706000418.GB7150@amt.cnet> (raw)
In-Reply-To: <20120521175335.GD3353@redhat.com>

On Mon, May 21, 2012 at 01:53:36PM -0400, Jason Baron wrote:
> On Fri, May 04, 2012 at 05:23:51PM -0400, Jason Baron wrote:
> > Add a command line parameter to not dump guest memory in the core dump, the
> > command line is: -dont-dump-guest. This brought the core dump down from
> > 383MB to 13 MB on a 1GB guest.
> > 
> > Signed-off-by: Jason Baron <jbaron@redhat.com>
> > ---
> >  exec.c          |   13 +++++++++++++
> >  osdep.h         |    7 +++++++
> >  qemu-options.hx |    5 +++++
> >  sysemu.h        |    1 +
> >  vl.c            |    4 ++++
> >  5 files changed, 30 insertions(+), 0 deletions(-)
> > 
> 
> Any thoughts on this? Is the guest memory often helpful in debugging
> when the qemu process segfaults?

For most development related usage, no (with large guests, its 
troublesome).

Please add documentation for the command (patch looks fine otherwise).

> This feature also seems useful if somebody is running a sensitive
> workload, such that the non-sensitive qemu state can be dumped
> independently of the guest state. In that case, perhaps there should
> also be an option that allows the guest to be dumped on a segfault, now
> separately?

Isnt what this option does? (well, disabling it).

  reply	other threads:[~2012-07-06  0:05 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 [this message]
2012-07-06  5:11     ` Markus Armbruster
2012-07-11 14:14       ` Avi Kivity
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=20120706000418.GB7150@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=jbaron@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).