From: Laszlo Ersek <lersek@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gonglei <arei.gonglei@huawei.com>, Peter Xu <peterx@redhat.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] scripts: Fix dump-guest-memory.py for MemoryRegion.ram_block removal
Date: Mon, 7 Mar 2016 10:37:24 +0100 [thread overview]
Message-ID: <56DD4BD4.5060905@redhat.com> (raw)
In-Reply-To: <1457342271-13410-1-git-send-email-famz@redhat.com>
On 03/07/16 10:17, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
>
> This goes after "[PATCH v2 4/7] memory: Drop MemoryRegion.ram_addr" (or
> squashed into it if we want strict synchronization).
> ---
> scripts/dump-guest-memory.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/dump-guest-memory.py b/scripts/dump-guest-memory.py
> index f274bf8..c0a2e99 100644
> --- a/scripts/dump-guest-memory.py
> +++ b/scripts/dump-guest-memory.py
> @@ -352,7 +352,7 @@ def memory_region_get_ram_ptr(memory_region):
> return (memory_region_get_ram_ptr(memory_region["alias"].dereference())
> + memory_region["alias_offset"])
>
> - return qemu_get_ram_ptr(memory_region["ram_addr"] & TARGET_PAGE_MASK)
> + return qemu_get_ram_ptr(memory_region["ram_block"]["offset"])
>
>
> def get_guest_phys_blocks():
>
I didn't follow your series, and I've by now forgotten most of the dump
stuff, but if you tested the above with GDB, I can ack it.
Acked-by: Laszlo Ersek <lersek@redhat.com>
I hope that Janosch can chime in as well.
Thanks
Laszlo
next prev parent reply other threads:[~2016-03-07 9:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 6:18 [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 1/7] exec: Return RAMBlock pointer from allocating functions Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 2/7] memory: Move assignment to ram_block to memory_region_init_* Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 3/7] memory: Implement memory_region_get_ram_addr with mr->ram_block Fam Zheng
2016-03-01 6:58 ` Gonglei (Arei)
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 4/7] memory: Drop MemoryRegion.ram_addr Fam Zheng
2016-03-07 9:17 ` [Qemu-devel] [PATCH] scripts: Fix dump-guest-memory.py for MemoryRegion.ram_block removal Fam Zheng
2016-03-07 9:37 ` Laszlo Ersek [this message]
2016-03-07 9:45 ` Fam Zheng
2016-03-07 10:08 ` Laszlo Ersek
2016-03-07 13:00 ` Paolo Bonzini
2016-03-07 16:35 ` Janosch Frank
2016-03-08 7:54 ` Janosch Frank
2016-03-08 8:54 ` Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 5/7] exec: Pass RAMBlock pointer to qemu_ram_free Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 6/7] exec: Factor out section_covers_addr Fam Zheng
2016-03-01 7:23 ` Peter Xu
2016-03-01 9:42 ` Paolo Bonzini
2016-03-02 2:24 ` Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 7/7] exec: Introduce AddressSpaceDispatch.mru_section Fam Zheng
2016-03-01 9:43 ` [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate Paolo Bonzini
2016-03-07 8:53 ` Laszlo Ersek
2016-03-07 9:04 ` Fam Zheng
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=56DD4BD4.5060905@redhat.com \
--to=lersek@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=famz@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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.