| Message ID | 20181018201351.GA25286@beast (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | nvdimm: Add docs hint for Linux driver name | expand |
On Thu, Oct 18, 2018 at 01:13:51PM -0700, Kees Cook wrote: > 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> > --- > docs/nvdimm.txt | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) Thanks, applied to my block tree: https://github.com/stefanha/qemu/commits/block Stefan
diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt index 5f158a61708e..7231c2d78f65 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:
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> --- docs/nvdimm.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)