From: David Gibson <david@gibson.dropbear.id.au>
To: qemu-devel@nongnu.org, quintela@redhat.com
Cc: aik@ozlabs.ru
Subject: Re: [Qemu-devel] [PATCH] migration: Fix madvise breakage if host and guest have different page sizes
Date: Wed, 21 Nov 2012 16:42:35 +1100 [thread overview]
Message-ID: <20121121054235.GU18362@truffula.fritz.box> (raw)
In-Reply-To: <1353473965-30678-1-git-send-email-david@gibson.dropbear.id.au>
On Wed, Nov 21, 2012 at 03:59:25PM +1100, David Gibson wrote:
> madvise(DONTNEED) will throw away the contents of the whole page at the
> given address, even if the given length is less than the page size. One
> can argue about whether that's the correct behaviour, but that's what it's
> done for a long time in Linux at least.
>
> That means that the madvise() in ram_load(), on a setup where
> TARGET_PAGE_SIZE is smaller than the host page size, can throw away data
> in guest pages adjacent to the one it's actually processing right now,
> leading to guest memory corruption on an incoming migration.
>
> This patch therefore, disables the madvise() if the host page size is
> larger than TARGET_PAGE_SIZE. This means we don't get the benefits of that
> madvise() in this case, but a more complete fix is more difficult to
> accomplish. This at least fixes the guest memory corruption.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Sorry, forgot to add:
Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2012-11-21 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 4:59 [Qemu-devel] [PATCH] migration: Fix madvise breakage if host and guest have different page sizes David Gibson
2012-11-21 5:04 ` David Gibson
2012-11-21 5:42 ` David Gibson [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=20121121054235.GU18362@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--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).