On Tue, Jul 19, 2016 at 3:53 PM, Dan Williams <[email protected]> wrote: > On Tue, Jul 19, 2016 at 3:46 PM, Jerry Hoemann <[email protected]> wrote: >> On Tue, Jul 19, 2016 at 01:01:16PM -0700, Dan Williams wrote: >>> On Tue, Jul 19, 2016 at 11:52 AM, Dan Williams <[email protected]> >>> wrote: >>> > On Tue, Jul 19, 2016 at 11:50 AM, Linda Knippers <[email protected]> >>> > wrote: >>> >> On 7/19/2016 1:11 PM, Jerry Hoemann wrote: >>> [..] >>> >>> As nfit_mem->family always equals NVDIMM_FAMILY_INTEL, no subsequent >>> >>> DSM call will succeed for NVDIMM_FAMILY_HPE1 or any other >>> >>> family. >>> >>> >>> >>> I don't have a fix as of yet, but wanted to make you aware of >>> >>> the problem. >>> >> >>> >> Could we try the all known UUIDs looking for one that returns a non-zero >>> >> value? >>> >> >>> > >>> > Yes, that seems like the way forward, and also make not finding a DSM >>> > family non-fatal. >>> >>> Actually, all we need is that last bit... Jerry, Xiao, can you try >>> the attached patch on top for v4.7-rc6 to see if it works in both HPe >>> and QEMU 2.6 environments respectively? >> >> Dan, >> >> I applied this patch on top of the SLES 12 sp2 kernel I was testing >> with last night. >> >> The proposed patch below works for HPE nvdimms. > > Thanks Jerry, I'll add your Tested-by and push it for v4.7-final after > Xiao has a chance to confirm.
I was able to verify this on QEMU 2.6. _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
