Closed foolstrong closed 1 year ago
nfit_test depends on replacing the "production" version of the drivers/nvdimm/ modules with the ones that tools/testing/nvdimm/Kbuild creates. Likely what is happening is that you have, for example, the original libnvdimm.ko already loaded, and then when nfit_test loads it does not find the modified libnvdimm.ko. Those "_test" symbols are there to catch those collisions.
When I test with nfit_test it is always on a throw away VM where all the replacement test modules in place before the VM boots.
my machine already load ko as follows
[root@localhost home]# lsmod | grep nfit
nfit 81920 0
libnvdimm 212992 1 nfit
I should remove the original ko already loaded,and insert these that tools/testing/nvdimm/Kbuild creates?
not problem
I get a error with nfit_test as follows
I'm sure that these config has been set, then build and install the unit test enabled libnvdimm modules in the following order