aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2018-10-18 13:13:51 -0700
committerStefan Hajnoczi <stefanha@redhat.com>2018-10-29 13:35:22 +0000
commitbd54b11062c4baa7d2e4efadcf71b8cfd55311fd (patch)
tree3ec10f019a4389ee3519a6ad30eb8bbf4a16327b /docs
parent82dfee5a68240fe786ae3d0dbc5e026430203155 (diff)
downloadqemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.zip
qemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.tar.gz
qemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.tar.bz2
nvdimm: Add docs hint for Linux driver name
I spent way too much time trying to figure out why the emulated NVDIMM was missing under Linux. In an effort to help others who might be looking for these kinds of things in the future, include a hint. Signed-off-by: Kees Cook <keescook@chromium.org> Message-id: 20181018201351.GA25286@beast Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/nvdimm.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
index 5f158a6..7231c2d 100644
--- a/docs/nvdimm.txt
+++ b/docs/nvdimm.txt
@@ -49,8 +49,9 @@ Multiple vNVDIMM devices can be created if multiple pairs of "-object"
and "-device" are provided.
For above command line options, if the guest OS has the proper NVDIMM
-driver, it should be able to detect a NVDIMM device which is in the
-persistent memory mode and whose size is $NVDIMM_SIZE.
+driver (e.g. "CONFIG_ACPI_NFIT=y" under Linux), it should be able to
+detect a NVDIMM device which is in the persistent memory mode and whose
+size is $NVDIMM_SIZE.
Note: