All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, berrange@redhat.com,
	dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH] dump: do not dump non-existent guest memory
Date: Tue, 12 Sep 2017 11:33:33 +0800	[thread overview]
Message-ID: <20170912033333.GA29091@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170911132627.9505-1-cohuck@redhat.com>

On Mon, Sep 11, 2017 at 03:26:27PM +0200, Cornelia Huck wrote:
> It does not really make sense to dump memory that is not there.
> 
> Moreover, that fixes a segmentation fault when calling dump-guest-memory
> with no filter for a machine with no memory defined.
> 
> New behaviour is:
> 
> (qemu) dump-guest-memory /dev/null
> dump: no guest memory to dump
> (qemu) dump-guest-memory /dev/null 0 4096
> dump: no guest memory to dump
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> 
> Another unmaintained file. Joy. cc:ing some more-or-less random folks.

I thought Marc-André had proposed to be the maintainer? But indeed I
didn't see the line in maintainer file.

Anyway, if anyone think I am ok to maintain this single file
(considering that I haven't posted patches on it for 2 years, and I
haven't been working on any kind of maintainer job), please let me
know. I'm glad to start with it (or with Marc-André).

Thanks,

-- 
Peter Xu

  parent reply	other threads:[~2017-09-12  3:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 13:26 [Qemu-devel] [PATCH] dump: do not dump non-existent guest memory Cornelia Huck
2017-09-11 13:45 ` Laurent Vivier
2017-09-11 14:02 ` Greg Kurz
2017-09-12  2:29 ` Peter Xu
2017-09-12  3:33 ` Peter Xu [this message]
2017-09-12 10:17   ` Marc-André Lureau
2017-09-13  6:12     ` Peter Xu
2017-09-13  7:58     ` Cornelia Huck
2017-09-14  5:40       ` Peter Xu

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=20170912033333.GA29091@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@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.