From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>,
Jitendra Kolhe <jitendra.kolhe@hpe.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] os: don't corrupt pre-existing memory-backend data with prealloc
Date: Fri, 10 Mar 2017 12:30:48 +0800 [thread overview]
Message-ID: <20170310043048.GC4589@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170303113255.28262-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Fri, Mar 03, 2017 at 11:32:55AM +0000, Daniel P. Berrange wrote:
> When using a memory-backend object with prealloc turned on, QEMU
> will memset() the first byte in every memory page to zero. While
> this might have been acceptable for memory backends associated
> with RAM, this corrupts application data for NVDIMMs.
>
> Instead of setting every page to zero, read the current byte
> value and then just write that same value back, so we are not
> corrupting the original data. Directly write the value instead
> of memset()ing it, since there's no benefit to memset for a
> single byte write.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
>
> Changed in v3:
>
> - Mark the target of the write as volatile, instead of the intermedia
> variable (Andrea)
>
> util/oslib-posix.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
There are no official maintainers for this source file. I want to make
sure this patch goes into QEMU 2.9, so...
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-03-10 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 11:32 [Qemu-devel] [PATCH v3] os: don't corrupt pre-existing memory-backend data with prealloc Daniel P. Berrange
2017-03-03 11:38 ` no-reply
2017-03-03 16:10 ` Andrea Arcangeli
2017-03-10 4:27 ` Stefan Hajnoczi
2017-03-10 4:30 ` Stefan Hajnoczi [this message]
2017-03-10 8:34 ` Paolo Bonzini
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=20170310043048.GC4589@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=aarcange@redhat.com \
--cc=berrange@redhat.com \
--cc=jitendra.kolhe@hpe.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).