Re: [RFC v2 0/5] surface heterogeneous memory performance information

2017-07-07 Thread Ross Zwisler
On Thu, Jul 06, 2017 at 10:30:46PM -0700, John Hubbard wrote: > On 07/06/2017 02:52 PM, Ross Zwisler wrote: > [...] > > > > The naming collision between Jerome's "Heterogeneous Memory Management > > (HMM)" and this "Heterogeneous Memory (HMEM)" series is unfortunate, but I > > was trying to stick

Re: [RFC v2 3/5] hmem: add heterogeneous memory sysfs support

2017-07-07 Thread Ross Zwisler
On Thu, Jul 06, 2017 at 10:53:39PM -0700, John Hubbard wrote: > On 07/06/2017 02:52 PM, Ross Zwisler wrote: > [...] > > diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile > > index b1aacfc..31e3f20 100644 > > --- a/drivers/acpi/Makefile > > +++ b/drivers/acpi/Makefile > > @@ -72,6 +72,7 @@

Re: [RFC v2 0/5] surface heterogeneous memory performance information

2017-07-07 Thread Ross Zwisler
On Fri, Jul 07, 2017 at 04:27:16PM +1000, Balbir Singh wrote: > On Thu, 2017-07-06 at 15:52 -0600, Ross Zwisler wrote: > > Quick Summary > > > > Platforms in the very near future will have multiple types of memory > > attached to a single CPU. These disparate memory ranges will have

Re: [RFC v2 0/5] surface heterogeneous memory performance information

2017-07-07 Thread Dave Hansen
On 07/06/2017 11:27 PM, Balbir Singh wrote: > On Thu, 2017-07-06 at 15:52 -0600, Ross Zwisler wrote: >> # grep . mem_tgt2/* mem_tgt2/local_init/* 2>/dev/null >> mem_tgt2/firmware_id:1 This is here for folks that know their platform and know exactly the firmware ID (PXM in ACPI parlance) of a

[PATCH] libnvdimm: fix badblock range handling of ARS range

2017-07-07 Thread Toshi Kani
__add_badblock_range() does not account sector alignment when it sets 'num_sectors'. Therefore, an ARS error record range spanning across two sectors is set to a single sector length, which leaves the 2nd sector unprotected. Change __add_badblock_range() to set 'num_sectors' properly. Fixes:

[ndctl PATCH 0/2] Be kind to humans

2017-07-07 Thread Dan Williams
Prompted by Yasunori's patch to add a few more fields to the "ndctl list --dimm" output we realized it would be nice to have listings be more user-friendly by default. These patches take advantage of json-c's ability to specify a custom object serializer so that we can select 'human' vs 'machine'

[ndctl PATCH 1/2] ndctl, list: convert json control flags to bit-flags

2017-07-07 Thread Dan Williams
Before we go to add new flags to pass through the json helpers, convert the existing control flags to bit flags. Signed-off-by: Dan Williams --- daxctl/list.c | 17 ++--- ndctl/list.c | 25 ++--- ndctl/namespace.c |3 ++-

[ndctl PATCH 2/2] ndctl, daxctl, list: make terminal output human readable by default

2017-07-07 Thread Dan Williams
The json output format of the 'list' commands is meant to make it easy to ingest the data into other tools. However, for direct administrator use of the utility it now offers human friendly formatting by default. Before: # ndctl list --region=7 { "dev":"region7",

Re: Standardization of ACPI NVDIMM DSMs

2017-07-07 Thread Dan Williams
On Sun, Jul 2, 2017 at 9:53 PM, Yasunori Goto wrote: [..] > 2) I suppose a notification daemon may be necessary to inform the over > threshold event (to syslog, to other servers, or logging management OSS, > etc) > > Please correct me, if ndctl has this