Le 31/10/2018 à 04:13, Dan Williams a écrit :
> On the expectation that some environments may not upgrade libdaxctl
> (userspace component that depends on the /sys/class/dax hierarchy),
> provide a default / legacy dax_pmem_compat driver. The dax_pmem_compat
> driver implements the original /sys/class/dax sysfs layout rather than
> /sys/bus/dax. When userspace is upgraded it can blacklist this module
> and switch to the dax_pmem driver going forward.


Hello Dan

It looks like /sys/bus/dax/devices remains empty forever if
dax_pmem_compat has ever been loaded during this boot. Unloading
dax_pmem_compat and recreating dax devices with ndctl afterwards doesn't
make them appear (neither in /sys/class/dax obviously, nor in
/sys/bus/dax/devices surprisingly). Is this expected?

Things appear fine in /sys/bus/dax/devices after disabling the compat
module in Kconfig.

I am using your nvdimm-pending branch.

Thanks

Brice


_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm

Reply via email to