RE: How is a Region format interface codec used in NFIT/PEME/BLK/BTT driver?

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On > Behalf Of Soccer Liu > Sent: Thursday, February 09, 2017 1:45 PM > Subject: How is a Region format interface codec used in > NFIT/PEME/BLK/BTT driver? > >   I am trying to figure out what changes

RE: [PATCH] ndctl: move test/dax-errors buffer to global to avoid gcc optimization

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On > Behalf Of Dave Jiang > Sent: Thursday, September 15, 2016 5:28 PM > To: vishal.l.ve...@intel.com > Cc: linux-nvdimm@lists.01.org > Subject: [PATCH] ndctl: move test/dax-errors buffer to global to >

/dev/dax size

How is an application supposed to detect the max mmap() size possible for a /dev/daxNN device? fio, for example, doesn't know what size to use. Its os/os-linux.h does not define FIO_HAVE_CHARDEV_SIZE and it has no chardev_size function to determine the size of a character device. --- Robert

RE: [PATCH] ndctl: move test/dax-errors buffer to global to avoid gcc optimization

> -Original Message- > From: Dave Jiang [mailto:dave.ji...@intel.com] > Sent: Friday, September 16, 2016 12:24 PM ... > Subject: Re: [PATCH] ndctl: move test/dax-errors buffer to global to > avoid gcc optimization > > On 09/15/2016 06:18 PM, Elliott, Robert (Per

RE: [PATCH v2] libnvdimm: check and clear poison before writing to pmem

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On > Behalf Of Vishal Verma > Sent: Thursday, November 10, 2016 3:56 PM > To: Dan Williams > Cc: linux-nvdimm@lists.01.org > Subject: Re: [PATCH v2] libnvdimm: check and clear

RE: [PATCH 1/3] dev-dax: add support to display badblocks in sysfs for dev-dax

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On > Behalf Of Dave Jiang > Sent: Monday, December 12, 2016 6:15 PM > Subject: [PATCH 1/3] dev-dax: add support to display badblocks in > sysfs for dev-dax > > Adding support to show badblocks in the pmem

RE: [RFC] memcpy_nocache() and memcpy_writethrough()

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Al Viro > Sent: Friday, December 30, 2016 8:26 PM > Subject: [RFC] memcpy_nocache() and memcpy_writethrough() > ... > Why does pmem need writethrough warranties,

RE: [PATCH v2] libndctl: add support for the MSFT family of DSM functions

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf > Of lijun@dell.com > Sent: Wednesday, March 29, 2017 4:41 PM > To: dan.j.willi...@intel.com; lijunpan2...@gmail.com > Subject: RE: [PATCH v2] libndctl: add support for the MSFT family of DSM

RE: [PATCH v4 0/8] Adding blk-mq and DMA support to pmem block driver

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Monday, August 7, 2017 11:39 AM > To: vinod.k...@intel.com; dan.j.willi...@intel.com > Cc: dmaeng...@vger.kernel.org; linux-nvdimm@lists.01.org > Subject: [PATCH v4 0/8]

RE: [PATCH] mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Luck, Tony > Sent: Wednesday, June 21, 2017 12:54 PM > To: Naoya Horiguchi > Cc: Borislav Petkov ; Dave Hansen

RE: Access to NVDIMM JEDEC registers

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Brian Stark > Sent: Wednesday, September 20, 2017 11:11 AM > To: Dan Williams > Cc: Raghu Kulkarni ; linux-nvdimm@lists.01.org >

RE: [PATCH] acpi/nfit: export read_only attribute of dimms

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On > Behalf Of Dan Williams > Sent: Monday, November 06, 2017 5:32 PM > To: Lijun Pan > Cc: linux-nvdimm@lists.01.org > Subject: Re: [PATCH] acpi/nfit: export read_only attribute of

RE: [PATCH v2] acpi: nfit: document sysfs interface

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Aishwarya Pant > Sent: Friday, February 23, 2018 6:55 AM > To: Dan Williams ; Rafael J. Wysocki > ; Len Brown ; linux- >

RE: [qemu PATCH v2 3/4] nvdimm, acpi: support NFIT platform capabilities

... > Would it help to show them in hex? > > As of ACPI 6.2 Errata A, the following values are valid for the bottom > two bits: > > 0x2 - Memory Controller Flush to NVDIMM Durability on Power Loss Capable. > 0x3 - CPU Cache Flush to NVDIMM Durability on Power Loss Capable. Yes, that

RE: [qemu PATCH v2 3/4] nvdimm, acpi: support NFIT platform capabilities

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Ross Zwisler > Sent: Thursday, May 17, 2018 12:00 AM > Subject: [qemu PATCH v2 3/4] nvdimm, acpi: support NFIT platform > capabilities > > Add a machine command line option to allow the

RE: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1

r.kernel.org; Elliott, Robert (Persistent > Memory) > Subject: Re: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with > ACPI 6.1 > > On Mon, Jun 18, 2018 at 12:39 PM, Kani, Toshi wrote: > > On Mon, 2018-06-18 at 12:01 -0700, Dan Williams wrote: > >>

RE: [PATCH] mm: disallow mapping that conflict for devm_memremap_pages()

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Thursday, June 14, 2018 1:25 PM > Subject: [PATCH] mm: disallow mapping that conflict for > devm_memremap_pages() ... > + conflict_pgmap =

RE: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Dan Williams > Sent: Tuesday, June 19, 2018 10:29 AM > Subject: Re: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with > ACPI 6.1 ... > > > > Here are

RE: [qemu PATCH v4 0/4] support NFIT platform capabilities

> Ping on this series. Rob, I think I've addressed all your feedback. > Can you please verify? I haven't tested it, but it reads OK. I'm OK with just extending the valid count for bits set to one for now; we can add a new argument later if a need arises for extending it to express new bits set

RE: [qemu PATCH v4 3/4] nvdimm, acpi: support NFIT platform capabilities

> > Okay, we can move to the symbolic names. Do you want them to be that > long, or > > would: > > > > nvdimm-cap-cpu > > nvdimm-cap-mem-ctrl > > nvdimm-cap-mirroring > > Wait, why is mirroring part of this? This data structure is intended to report any kind of platform capability, not just

RE: [PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1

> -Original Message- > From: Dan Williams [mailto:dan.j.willi...@intel.com] > Sent: Monday, June 18, 2018 4:47 PM > To: Elliott, Robert (Persistent Memory) > Cc: Kani, Toshi ; linux-ker...@vger.kernel.org; linux- > nvd...@lists.01.org; Moore, Robert ; Li, Juston >

RE: [PATCH 04/11] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Monday, July 2, 2018 6:39 PM > To: dan.j.willi...@intel.com > Cc: dhowe...@redhat.com; alison.schofi...@intel.com; > keyri...@vger.kernel.org; keesc...@chromium.org;

RE: [PATCH 04/11] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs

> > Since it contains a high-value password, I recommend zeroing > > cmd->passphrase before calling kfree() so that data isn't seen > > by a subsequent kmalloc() caller (and make sure the compiler > > cannot optimize away the clearing code). > > > > Also, check if the ndctl() call chain makes

RE: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Ross Zwisler ... > > On Wed, Dec 20, 2017 at 10:19:37AM -0800, Matthew Wilcox wrote: ... > > initiator is a CPU? I'd have expected you to expose a memory controller > > abstraction

RE: caching options

> -Original Message- > From: Linux-nvdimm On Behalf Of > Brian Stark > Sent: Tuesday, July 31, 2018 11:43 AM > To: linux-nvdimm@lists.01.org > Subject: caching options > > I have a customer that requires persistent memory be set to Write > Combining cache attribute with the Skylake

ndctl create-namespace region order

ndctl create-namespace doesn't walk through the regions from lowest to highest; in this example it's going 1,3,5,0,2,4,6: $ sudo ndctl create-namespace --verbose ROB: parsing bus id=0 path=ndbus0 ROB: parsing region id=1 path=region1 namespace_create:770: region1: insufficient capacity size: 0

RE: [PATCH v5 09/12] nfit/libnvdimm: add support for issue secure erase DSM to Intel nvdimm

> -Original Message- > From: Dave Jiang > Sent: Wednesday, July 18, 2018 12:41 PM > To: Elliott, Robert (Persistent Memory) ; Williams, > Dan J > Cc: dhowe...@redhat.com; Schofield, Alison > ; keyri...@vger.kernel.org; > keesc...@chromium.org; linux-nvdimm@li

RE: [PATCH v5 03/12] nfit/libnvdimm: store dimm id as a member to struct nvdimm

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Tuesday, July 17, 2018 3:54 PM > Subject: [PATCH v5 03/12] nfit/libnvdimm: store dimm id as a member to struct > nvdimm ... > + if (dcr->valid_fields &

RE: [PATCH v5 09/12] nfit/libnvdimm: add support for issue secure erase DSM to Intel nvdimm

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Tuesday, July 17, 2018 3:55 PM > Subject: [PATCH v5 09/12] nfit/libnvdimm: add support for issue secure erase > DSM to Intel nvdimm ... +static int

RE: open sets ext4_da_aops for DAX existing files

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Kani, Toshi > Sent: Monday, September 10, 2018 9:52 AM > To: j...@suse.cz > Cc: linux-fsde...@vger.kernel.org; linux-nvdimm@lists.01.org > Subject: Re: open sets ext4_da_aops for DAX

ndctl read-labels default output format

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dan Williams > Sent: Saturday, April 9, 2016 2:40 PM > To: linux-nvdimm@lists.01.org > Subject: [ndctl PATCH 3/4] ndctl: new 'read-labels' utility > > For debug, it is useful to be able

RE: [PATCH v2] nfit, mce: only handle uncorrectable machine checks

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Vishal Verma > Sent: Thursday, October 25, 2018 1:06 PM ... > +++ b/drivers/acpi/nfit/mce.c > @@ -25,8 +25,8 @@ static int nfit_handle_mce(struct notifier_block *nb, > unsigned long

RE: [PATCH 0/9] Allow persistent memory to be used like normal RAM

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dan Williams > Sent: Monday, October 22, 2018 8:05 PM > Subject: Re: [PATCH 0/9] Allow persistent memory to be used like normal RAM > > On Mon, Oct 22, 2018 at 1:18 PM Dave Hansen >

RE: [PATCH 10/11] tools/testing/nvdimm: add Intel DSM 1.8 support for nfit_test

> -Original Message- > From: Linux-nvdimm On Behalf Of > Dave Jiang > Sent: Friday, November 09, 2018 4:15 PM > To: dan.j.willi...@intel.com; zo...@linux.vnet.ibm.com > Cc: linux-nvdimm@lists.01.org > Subject: [PATCH 10/11] tools/testing/nvdimm: add Intel DSM 1.8 > support for

RE: [PATCH 07/11] libnvdimm/security: add overwrite status notification

> -Original Message- > From: Linux-nvdimm On Behalf Of > Dave Jiang > Sent: Friday, November 09, 2018 4:14 PM > Subject: [PATCH 07/11] libnvdimm/security: add overwrite status > notification > ... > @@ -2033,6 +2033,11 @@ static int acpi_nfit_register_dimms(struct > acpi_nfit_desc

RE: [PATCH v15 07/16] acpi/nfit, libnvdimm: Add unlock of nvdimm support for Intel DIMMs

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Dave Jiang > Sent: Thursday, December 13, 2018 5:49 PM > To: dan.j.willi...@intel.com > Cc: linux-nvdimm@lists.01.org > Subject: [PATCH v15 07/16] acpi/nfit, libnvdimm: Add unlock of

RE: [PATCH] libnvdimm: normalize dev_debug failed and succeeded wording

> -Original Message- > From: Dan Williams [mailto:dan.j.willi...@intel.com] > Sent: Tuesday, January 22, 2019 4:24 PM > To: Elliott, Robert (Persistent Memory) > Cc: linux-nvdimm > Subject: Re: [PATCH] libnvdimm: normalize dev_debug failed and succeeded > wordin

RE: Question on Error Injection

For mailing lists, please use plaintext rather than HTML emails, and don’t top-post. > Are these statements correct? > > 1) Reading from a memory location (mmaped) with uncorrectable AND unknown > error (also called as latent error) results in a machine-check (which > usually results in a

RE: Question on Error Injection

> -Original Message- > From: Linux-nvdimm On Behalf Of Verma, > Vishal L > Sent: Thursday, January 3, 2019 3:27 PM > To: kamalkakri2...@yahoo.com; linux-nvdimm@lists.01.org > Subject: Re: Question on Error Injection > > > On Thu, 2019-01-03 at 20:02 +, Kamal Kakri wrote: > > My

RE: Question on Error Injection

> -Original Message- > From: Verma, Vishal L > Sent: Thursday, January 3, 2019 6:03 PM > To: kamalkakri2...@yahoo.com; linux-nvdimm@lists.01.org; Elliott, Robert > (Persistent Memory) > Subject: Re: Question on Error Injection > > > On Thu, 2019-01-03 at 2

RE: Question on Error Injection

Kamal Kakri wrote: > What do you mean by: > > "The application itself shouldn't be terminated with SIGBUS - that's > for an application doing memory accesses that cannot be resolved." > > Can you elaborate with an example ? DAX (direct access). If the application uses mmap() of a file or

RE: [ndctl PATCH 1/2] autoconf: Check for MAP_SHARED_VALIDATE

> -Original Message- > From: Dan Williams [mailto:dan.j.willi...@intel.com] > Sent: Thursday, February 14, 2019 10:54 AM > To: Elliott, Robert (Persistent Memory) > Cc: linux-nvdimm > Subject: Re: [ndctl PATCH 1/2] autoconf: Check for MAP_SHARED_VALIDATE > > O

RE: [PATCH v4 1/5] libndctl: Use the supported_alignment attribute

> -Original Message- > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of > Oliver O'Halloran > Sent: Tuesday, January 29, 2019 8:49 AM > To: linux-nvdimm@lists.01.org > Subject: [PATCH v4 1/5] libndctl: Use the supported_alignment attribute > > Reworded