summaryrefslogtreecommitdiff
path: root/include/hw/mem/pc-dimm.h
diff options
context:
space:
mode:
authorXiao Guangrong <guangrong.xiao@linux.intel.com>2016-05-20 16:19:58 +0800
committerMichael S. Tsirkin <mst@redhat.com>2016-06-07 15:39:28 +0300
commit3c3e88a814ef4eb8b2f8bf81863baec24838d998 (patch)
treeb03d8f590b165dff9fe794309d554ddde2f9ef33 /include/hw/mem/pc-dimm.h
parent28213cb6a61a724e2cb1e3a76d2bb17aa0ce9b36 (diff)
downloadqemu-3c3e88a814ef4eb8b2f8bf81863baec24838d998.tar.gz
pc-dimm: get memory region from ->get_memory_region()
Curretly, the memory region of backed memory is all directly mapped to guest's address space, however, it will be not true for nvdimm device if we introduce nvdimm label which only can be indirectly accessed by ACPI DSM method Also it improves the comments a bit to reflect this fact Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'include/hw/mem/pc-dimm.h')
-rw-r--r--include/hw/mem/pc-dimm.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/hw/mem/pc-dimm.h b/include/hw/mem/pc-dimm.h
index 8cdc3266b3..6024627167 100644
--- a/include/hw/mem/pc-dimm.h
+++ b/include/hw/mem/pc-dimm.h
@@ -58,7 +58,8 @@ typedef struct PCDIMMDevice {
/**
* PCDIMMDeviceClass:
- * @get_memory_region: returns #MemoryRegion associated with @dimm
+ * @get_memory_region: returns #MemoryRegion associated with @dimm which
+ * is directly mapped into the physical address space of guest
*/
typedef struct PCDIMMDeviceClass {
/* private */