diff options
| author | Kees Cook | 2018-10-18 22:13:51 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi | 2018-10-29 14:35:22 +0100 |
| commit | bd54b11062c4baa7d2e4efadcf71b8cfd55311fd (patch) | |
| tree | 3ec10f019a4389ee3519a6ad30eb8bbf4a16327b | |
| parent | util: aio-posix: fix a typo (diff) | |
| download | qemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.tar.gz qemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.tar.xz qemu-bd54b11062c4baa7d2e4efadcf71b8cfd55311fd.zip | |
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>
| -rw-r--r-- | docs/nvdimm.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt index 5f158a6170..7231c2d78f 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: |