diff options
author | Daniel P. Berrange <berrange@redhat.com> | 2017-03-03 11:32:55 +0000 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2017-03-15 11:55:41 +0800 |
commit | 9dc44aa5829eb3131a01378a738dee28a382bbc1 (patch) | |
tree | 7626e5cbbd351029d49c269a4291b60540beba1e /translate-common.c | |
parent | d84f714eafedd8bb9d4aaec8b76417bef8e3535e (diff) |
os: don't corrupt pre-existing memory-backend data with prealloc
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>
Reviewed-by: Andrea Arcangeli <aarcange@redhat.com>
Message-id: 20170303113255.28262-1-berrange@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'translate-common.c')
0 files changed, 0 insertions, 0 deletions