[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <149218909065.3926.1234846095650907678.stgit@dwillia2-desk3.amr.corp.intel.com>
Date: Fri, 14 Apr 2017 09:58:11 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: linux-nvdimm@...ts.01.org
Cc: Linda Knippers <linda.knippers@....com>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
Toshi Kani <toshi.kani@....com>, vishal.l.verma@...el.com
Subject: [PATCH 0/5] libnvdimm: acpi updates and a revert
With Dave's recent fix [1], we can restore error clearing for btt i/o in
4.12.
ACPI 6.1 introduced new health state flags. Beyond reflecting them in
the dimmX/flags sysfs attribute we also need to handle the deeper
implications of the ACPI_NFIT_MEM_MAP_FAILED flag which changes
assumptions on how the driver discovers dimms. In the "map failed" case
there may missing or no SPA entries associated with a dimm. Those dimms
should still be registered with libnvdimm so that the error state can be
communicated and recovery attempted.
[1]: https://patchwork.kernel.org/patch/9680035/
---
Dan Williams (5):
Revert "libnvdimm: band aid btt vs clear poison locking"
acpi, nfit: add support for acpi 6.1 dimm state flags
tools/testing/nvdimm: test acpi 6.1 health state flags
acpi, nfit: support "map failed" dimms
acpi, nfit: limit ->flush_probe() to initialization work
drivers/acpi/nfit/core.c | 61 +++++++++++++++++++++++++++++++-------
drivers/acpi/nfit/nfit.h | 1 +
drivers/nvdimm/claim.c | 10 +-----
tools/testing/nvdimm/test/nfit.c | 40 +++++++++++++++++++++++--
4 files changed, 88 insertions(+), 24 deletions(-)
Powered by blists - more mailing lists