All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] acpi, nfit: support "map failed" dimms
Date: Mon, 17 Apr 2017 18:16:30 +0000	[thread overview]
Message-ID: <1492452970.26622.5.camel@hpe.com> (raw)
In-Reply-To: <149218911271.3926.4006907031326342869.stgit@dwillia2-desk3.amr.corp.intel.com>

On Fri, 2017-04-14 at 09:58 -0700, Dan Williams wrote:
> Stop requiring dimms be successfully mapped into a
> system-physical-address range. For provisioning and hardware
> remediation purposes the kernel should account for failed devices in
> sysfs. If possible it should still allow management commands to be
> sent to the device.
> 
> Reported-by: Toshi Kani <toshi.kani@hpe.com>
> Reported-by: Linda Knippers <linda.knippers@hpe.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Tested the "map failed" condition with HPE NVDIMMs. 

Tested-by: Toshi Kani <toshi.kani@hpe.com>

Thanks Dan!
-Toshi
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Cc: "Knippers, Linda" <linda.knippers@hpe.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>
Subject: Re: [PATCH 4/5] acpi, nfit: support "map failed" dimms
Date: Mon, 17 Apr 2017 18:16:30 +0000	[thread overview]
Message-ID: <1492452970.26622.5.camel@hpe.com> (raw)
In-Reply-To: <149218911271.3926.4006907031326342869.stgit@dwillia2-desk3.amr.corp.intel.com>

On Fri, 2017-04-14 at 09:58 -0700, Dan Williams wrote:
> Stop requiring dimms be successfully mapped into a
> system-physical-address range. For provisioning and hardware
> remediation purposes the kernel should account for failed devices in
> sysfs. If possible it should still allow management commands to be
> sent to the device.
> 
> Reported-by: Toshi Kani <toshi.kani@hpe.com>
> Reported-by: Linda Knippers <linda.knippers@hpe.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Tested the "map failed" condition with HPE NVDIMMs. 

Tested-by: Toshi Kani <toshi.kani@hpe.com>

Thanks Dan!
-Toshi

WARNING: multiple messages have this Message-ID (diff)
From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>
Cc: "Knippers, Linda" <linda.knippers@hpe.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>
Subject: Re: [PATCH 4/5] acpi, nfit: support "map failed" dimms
Date: Mon, 17 Apr 2017 18:16:30 +0000	[thread overview]
Message-ID: <1492452970.26622.5.camel@hpe.com> (raw)
In-Reply-To: <149218911271.3926.4006907031326342869.stgit@dwillia2-desk3.amr.corp.intel.com>

On Fri, 2017-04-14 at 09:58 -0700, Dan Williams wrote:
> Stop requiring dimms be successfully mapped into a
> system-physical-address range. For provisioning and hardware
> remediation purposes the kernel should account for failed devices in
> sysfs. If possible it should still allow management commands to be
> sent to the device.
> 
> Reported-by: Toshi Kani <toshi.kani@hpe.com>
> Reported-by: Linda Knippers <linda.knippers@hpe.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Tested the "map failed" condition with HPE NVDIMMs. 

Tested-by: Toshi Kani <toshi.kani@hpe.com>

Thanks Dan!
-Toshi

  reply	other threads:[~2017-04-17 18:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 16:58 [PATCH 0/5] libnvdimm: acpi updates and a revert Dan Williams
2017-04-14 16:58 ` Dan Williams
2017-04-14 16:58 ` [PATCH 1/5] Revert "libnvdimm: band aid btt vs clear poison locking" Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58 ` [PATCH 2/5] acpi, nfit: add support for acpi 6.1 dimm state flags Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-17 17:28   ` Kani, Toshimitsu
2017-04-17 17:28     ` Kani, Toshimitsu
2017-04-17 17:28     ` Kani, Toshimitsu
2017-04-14 16:58 ` [PATCH 3/5] tools/testing/nvdimm: test acpi 6.1 health " Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58 ` [PATCH 4/5] acpi, nfit: support "map failed" dimms Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-17 18:16   ` Kani, Toshimitsu [this message]
2017-04-17 18:16     ` Kani, Toshimitsu
2017-04-17 18:16     ` Kani, Toshimitsu
2017-04-14 16:58 ` [PATCH 5/5] acpi, nfit: limit ->flush_probe() to initialization work Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 16:58   ` Dan Williams
2017-04-14 17:30   ` Dan Williams
2017-04-14 17:30     ` Dan Williams
2017-04-14 17:30     ` Dan Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1492452970.26622.5.camel@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.