From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Leonardo Bras <leobras@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v3 4/6] migration: Remove masking for compression
Date: Tue, 11 Jan 2022 13:38:06 +0000 [thread overview]
Message-ID: <Yd2IPjiM8bH1eWxR@work-vm> (raw)
In-Reply-To: <20220111124556.4892-5-quintela@redhat.com>
* Juan Quintela (quintela@redhat.com) wrote:
> Remove the mask in the call to ram_release_pages(). Nothing else does
> it, and if the offset has that bits set, we have a lot of trouble.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
Yeh I think that comes from ram_save_target_page which does:
ram_addr_t offset = ((ram_addr_t)pss->page) << TARGET_PAGE_BITS;
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/ram.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 881fe4974e..fa49d22e69 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -1340,7 +1340,7 @@ static bool do_compress_ram_page(QEMUFile *f, z_stream *stream, RAMBlock *block,
> ram_addr_t offset, uint8_t *source_buf)
> {
> RAMState *rs = ram_state;
> - uint8_t *p = block->host + (offset & TARGET_PAGE_MASK);
> + uint8_t *p = block->host + offset;
> bool zero_page = false;
> int ret;
>
> @@ -1365,7 +1365,7 @@ static bool do_compress_ram_page(QEMUFile *f, z_stream *stream, RAMBlock *block,
> }
>
> exit:
> - ram_release_page(block->idstr, offset & TARGET_PAGE_MASK);
> + ram_release_page(block->idstr, offset);
> return zero_page;
> }
>
> --
> 2.34.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-01-11 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 12:45 [PATCH v3 0/6] migration: misc cleanups Juan Quintela
2022-01-11 12:45 ` [PATCH v3 1/6] migration: All this fields are unsigned Juan Quintela
2022-01-11 12:45 ` [PATCH v3 2/6] migration: We only need last_stage in two places Juan Quintela
2022-01-11 12:45 ` [PATCH v3 3/6] migration: ram_release_pages() always receive 1 page as argument Juan Quintela
2022-01-11 13:44 ` Philippe Mathieu-Daudé
2022-01-25 9:16 ` Juan Quintela
2022-01-11 12:45 ` [PATCH v3 4/6] migration: Remove masking for compression Juan Quintela
2022-01-11 13:38 ` Dr. David Alan Gilbert [this message]
2022-01-11 12:45 ` [PATCH v3 5/6] migration: simplify do_compress_ram_page Juan Quintela
2022-01-11 13:45 ` Dr. David Alan Gilbert
2022-01-11 12:45 ` [PATCH v3 6/6] migration: Move ram_release_pages() call to save_zero_page_to_file() Juan Quintela
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=Yd2IPjiM8bH1eWxR@work-vm \
--to=dgilbert@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).