Re: Question on PMEM regions (Linux 4.9 Kernel & above)

2020-06-19 Thread Dan Williams
On Fri, Jun 19, 2020 at 7:02 PM Ananth, Rajesh wrote: > > We used the Ubuntu 18.04 to get the "acpdump" outputs (This is the only > complete package distribution we have. Otherwise, we use mainly the built > Kernels). The NFIT data is all valid, but somehow it is printing the "@ > addresss"

RE: Question on PMEM regions (Linux 4.9 Kernel & above)

2020-06-19 Thread Ananth, Rajesh
We used the Ubuntu 18.04 to get the "acpdump" outputs (This is the only complete package distribution we have. Otherwise, we use mainly the built Kernels). The NFIT data is all valid, but somehow it is printing the "@ addresss" at the beginning as zeros. =

Re: Question on PMEM regions (Linux 4.9 Kernel & above)

2020-06-19 Thread Dan Williams
[ add back linux-nvdimm as others may hit the same issue too and I want this in the archives ] On Fri, Jun 19, 2020 at 4:49 PM Ananth, Rajesh wrote: > > Dan, > > Thank you so much for your response. Our PLATFORM is totally NFIT compliant > and does not use the Type-12/E820 maps. Ah, great. >

Re: Question on PMEM regions (Linux 4.9 Kernel & above)

2020-06-19 Thread Dan Williams
On Fri, Jun 19, 2020 at 4:18 PM Ananth, Rajesh wrote: > > I have a question on the default REGION creation (unlabeled NVDIMM) on the > Interleave Sets. I observe that for a Single Interleave Set, the Linux > Kernels earlier to 4.9 create only one "Region0->namespace0.0" (pmem0 for the >

Question on PMEM regions (Linux 4.9 Kernel & above)

2020-06-19 Thread Ananth, Rajesh
I have a question on the default REGION creation (unlabeled NVDIMM) on the Interleave Sets. I observe that for a Single Interleave Set, the Linux Kernels earlier to 4.9 create only one "Region0->namespace0.0" (pmem0 for the entire size), but in the later Kernels I observe for the same

[GIT PULL] libnvdimm for v5.8-rc2

2020-06-19 Thread Dan Williams
Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-5.8-rc2 ...to receive a feature (papr_scm health retrieval) and a fix (sysfs attribute visibility) for v5.8. Vaibhav explains in the merge commit below why missing v5.8 would be painful

Re: [PATCH][next] nvdimm/region: Use struct_size() in kzalloc()

2020-06-19 Thread Ira Weiny
On Fri, Jun 19, 2020 at 12:21:12PM -0500, Gustavo A. R. Silva wrote: > Make use of the struct_size() helper instead of an open-coded version > in order to avoid any potential type mistakes. > > This issue was found with the help of Coccinelle and, audited and fixed > manually. > >

[PATCH][next] nvdimm/region: Use struct_size() in kzalloc()

2020-06-19 Thread Gustavo A. R. Silva
Make use of the struct_size() helper instead of an open-coded version in order to avoid any potential type mistakes. This issue was found with the help of Coccinelle and, audited and fixed manually. Addresses-KSPP-ID: https://github.com/KSPP/linux/issues/83 Signed-off-by: Gustavo A. R. Silva

CV

2020-06-19 Thread Mehmood Khan
___ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org

Re: [PATCH v5 00/10] Support new pmem flush and sync instructions for POWER

2020-06-19 Thread Aneesh Kumar K.V
"Aneesh Kumar K.V" writes: > This patch series enables the usage os new pmem flush and sync instructions > on POWER > architecture. POWER10 introduces two new variants of dcbf instructions > (dcbstps and dcbfps) > that can be used to write modified locations back to persistent storage. >