diff options
| author | Xiao Guangrong <guangrong.xiao@linux.intel.com> | 2016-07-13 12:18:06 +0800 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2016-07-13 13:30:04 +0200 |
| commit | 2aece63c8a9d2c3a8ff41d2febc4cdeff2633331 (patch) | |
| tree | 02964fa0c17b241f41f4be55d1381eb8f2b24018 /target-i386 | |
| parent | 1454d33f0507cb54d62ed80f494884157c9e7130 (diff) | |
| download | qemu-2aece63c8a9d2c3a8ff41d2febc4cdeff2633331.zip qemu-2aece63c8a9d2c3a8ff41d2febc4cdeff2633331.tar.gz qemu-2aece63c8a9d2c3a8ff41d2febc4cdeff2633331.tar.bz2 | |
hostmem: detect host backend memory is being used properly
Currently, we use memory_region_is_mapped() to detect if the host
backend memory is being used. This works if the memory is directly
mapped into guest's address space, however, it is not true for
nvdimm as it uses aliased memory region to map the memory. This is
why this bug can happen:
https://bugzilla.redhat.com/show_bug.cgi?id=1352769
Fix it by introduce a new filed, is_mapped, to HostMemoryBackend,
we set/clear this filed accordingly when the device link/unlink to
host backend memory
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'target-i386')
0 files changed, 0 insertions, 0 deletions