All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jason Baron <jbaron@redhat.com>
Cc: qemu-devel@nongnu.org, mtosatti@redhat.com, eblake@redhat.com,
	avi@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] memory: add cmd line option, to omit guest memory from qemu core dump
Date: Wed, 01 Aug 2012 13:54:44 -0500	[thread overview]
Message-ID: <87ipd25tor.fsf@codemonkey.ws> (raw)
In-Reply-To: <20120801182811.GA25130@redhat.com>

Jason Baron <jbaron@redhat.com> writes:

> On Wed, Aug 01, 2012 at 01:21:57PM -0500, Anthony Liguori wrote:
>> Jason Baron <jbaron@redhat.com> writes:
>> 
>> > Add a new '[,dump_guest_core=on|off]' option to the '-machine' option. When
>> > 'dump_guest_core=off' is specified, guest memory is omitted from the core dump.
>> > The default behavior continues to be to include guest memory when a core dump is
>> > triggered. In my testing, this brought the core dump size down from 384MB to 6MB
>> > on a 2GB guest.
>> >
>> > Changelog:
>> > v2: move the option from -m to -machine, rename option dump -> dump_guest_core
>> >
>> > Signed-off-by: Jason Baron <jbaron@redhat.com>
>> > ---
>> >  exec.c          |   13 +++++++++++++
>> >  osdep.h         |    7 +++++++
>> >  qemu-config.c   |    4 ++++
>> >  qemu-options.hx |    5 ++++-
>> >  sysemu.h        |    1 +
>> >  vl.c            |    4 ++++
>> >  6 files changed, 33 insertions(+), 1 deletions(-)
>> >
>> > diff --git a/exec.c b/exec.c
>> > index feb4795..0764818 100644
>> > --- a/exec.c
>> > +++ b/exec.c
>> > @@ -35,6 +35,7 @@
>> >  #include "qemu-timer.h"
>> >  #include "memory.h"
>> >  #include "exec-memory.h"
>> > +#include "sysemu.h"
>> >  #if defined(CONFIG_USER_ONLY)
>> >  #include <qemu.h>
>> >  #if defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
>> > @@ -2514,6 +2515,7 @@ ram_addr_t qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,
>> >                                     MemoryRegion *mr)
>> >  {
>> >      RAMBlock *new_block;
>> > +    int ret;
>> >  
>> >      size = TARGET_PAGE_ALIGN(size);
>> >      new_block = g_malloc0(sizeof(*new_block));
>> > @@ -2555,6 +2557,17 @@ ram_addr_t qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,
>> >                                         last_ram_offset() >> TARGET_PAGE_BITS);
>> >      cpu_physical_memory_set_dirty_range(new_block->offset, size, 0xff);
>> >  
>> > +
>> > +    /* Use MADV_DONTDUMP, if user doesn't want the guest memory in the core */
>> > +    if (dont_dump_guest_core) {
>> 
>>     machine_opts = qemu_opts_find(qemu_find_opts("machine"), 0);
>>     if (machine_opts && qemu_opt_get_bool(machine_opts, "dump-guest-core")) {
>> 
>
> should be:
>  
> ... && !qemu_opt_get_bool(machine_opts, "dump-guest-core", true)
>
> ??

Yes.

Regards,

Anthony Liguori

  reply	other threads:[~2012-08-01 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 16:19 [Qemu-devel] [PATCH v2] memory: add cmd line option, to omit guest memory from qemu core dump Jason Baron
2012-08-01 18:21 ` Anthony Liguori
2012-08-01 18:28   ` Jason Baron
2012-08-01 18:54     ` Anthony Liguori [this message]
2012-08-02 18:05   ` Luiz Capitulino

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=87ipd25tor.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=eblake@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 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.