From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: "Bonzini, Paolo" <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] scripts/dump-guest-memory: Synchronize with guest_phys_blocks_region_add
Date: Mon, 29 Oct 2018 17:56:51 +0400 [thread overview]
Message-ID: <CAMxuvaxY1Nap6bW+=G8FH_4CFiLB1DNguGzyWaf-vBXN63dREA@mail.gmail.com> (raw)
In-Reply-To: <20181029135049.12552-1-pbonzini@redhat.com>
On Mon, Oct 29, 2018 at 5:50 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> Recent patches have removed ram_device and nonvolatile RAM
> from dump-guest-memory's output. Do the same for dumps
> that are extracted from a QEMU core file.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> scripts/dump-guest-memory.py | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/dump-guest-memory.py b/scripts/dump-guest-memory.py
> index 5a857cebcf..f04697b1dd 100644
> --- a/scripts/dump-guest-memory.py
> +++ b/scripts/dump-guest-memory.py
> @@ -417,7 +417,9 @@ def get_guest_phys_blocks():
> memory_region = flat_range["mr"].dereference()
>
> # we only care about RAM
> - if not memory_region["ram"]:
> + if not memory_region["ram"] \
> + or memory_region["ram_device"] \
> + or memory_region["nonvolatile"]:
> continue
>
> section_size = int128_get64(flat_range["addr"]["size"])
> --
> 2.17.1
>
prev parent reply other threads:[~2018-10-29 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 13:50 [Qemu-devel] [PATCH] scripts/dump-guest-memory: Synchronize with guest_phys_blocks_region_add Paolo Bonzini
2018-10-29 13:56 ` Marc-André Lureau [this message]
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='CAMxuvaxY1Nap6bW+=G8FH_4CFiLB1DNguGzyWaf-vBXN63dREA@mail.gmail.com' \
--to=marcandre.lureau@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@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).