On 02/16/2017 09:35 PM, Dan Williams wrote: > On Thu, Feb 16, 2017 at 10:51 AM, Linda Knippers <[email protected]> > wrote: <> >> True, but configuring boot options and a reboot are required. > > Module options are specified at module load time so you don't > necessarily need a reboot. However, I'm now of the opinion that > allowing the family to be changed is a more complete solution to both > problems. <> > > Let's do the work to allow the family to be switched so that tooling > can override the kernel default, because it does seem valid for a DIMM > to support multiple DSM-family types and that gives more than one path > to use a vendor specific passthrough.
BTW: Any module-parameter is already accessible via sysfs. And can be made writeable. If you need to run a small function on modification, that is easy enough, just as any sysfs, give the parameter a function-pointer. Even if you do an hot event, I'd rather it be as a module-parameter, because of the already established path in sysfs. Just my $0.017 Boaz _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
