From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support
Date: Tue, 08 Mar 2016 14:47:13 -0800 [thread overview]
Message-ID: <20160308224713.16298.33547.stgit@dwillia2-desk3.jf.intel.com> (raw)
ACPI 6.1 introduces the ability to send "clear error" commands to the
ACPI0012:00 device representing the root of an "nvdimm bus".
Similar to relocating a bad block on a disk, this support clears
media errors in response to a write.
---
Dan Williams (3):
nfit, libnvdimm: clear poison command support
libnvdimm, pmem: fix kmap_atomic() leak in error path
libnvdimm, pmem: clear poison on write
arch/x86/include/asm/pmem.h | 5 +++
drivers/acpi/nfit.c | 12 ++++++-
drivers/nvdimm/bus.c | 65 ++++++++++++++++++++++++++++++++++++++
drivers/nvdimm/nd.h | 2 +
drivers/nvdimm/pmem.c | 40 ++++++++++++++++++++---
include/linux/pmem.h | 19 +++++++++++
include/uapi/linux/ndctl.h | 13 ++++++++
tools/testing/nvdimm/test/nfit.c | 29 +++++++++++++++++
8 files changed, 179 insertions(+), 6 deletions(-)
_______________________________________________
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: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Vishal Verma <vishal.l.verma@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-acpi@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support
Date: Tue, 08 Mar 2016 14:47:13 -0800 [thread overview]
Message-ID: <20160308224713.16298.33547.stgit@dwillia2-desk3.jf.intel.com> (raw)
ACPI 6.1 introduces the ability to send "clear error" commands to the
ACPI0012:00 device representing the root of an "nvdimm bus".
Similar to relocating a bad block on a disk, this support clears
media errors in response to a write.
---
Dan Williams (3):
nfit, libnvdimm: clear poison command support
libnvdimm, pmem: fix kmap_atomic() leak in error path
libnvdimm, pmem: clear poison on write
arch/x86/include/asm/pmem.h | 5 +++
drivers/acpi/nfit.c | 12 ++++++-
drivers/nvdimm/bus.c | 65 ++++++++++++++++++++++++++++++++++++++
drivers/nvdimm/nd.h | 2 +
drivers/nvdimm/pmem.c | 40 ++++++++++++++++++++---
include/linux/pmem.h | 19 +++++++++++
include/uapi/linux/ndctl.h | 13 ++++++++
tools/testing/nvdimm/test/nfit.c | 29 +++++++++++++++++
8 files changed, 179 insertions(+), 6 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@ml01.01.org
Cc: Vishal Verma <vishal.l.verma@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-acpi@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support
Date: Tue, 08 Mar 2016 14:47:13 -0800 [thread overview]
Message-ID: <20160308224713.16298.33547.stgit@dwillia2-desk3.jf.intel.com> (raw)
ACPI 6.1 introduces the ability to send "clear error" commands to the
ACPI0012:00 device representing the root of an "nvdimm bus".
Similar to relocating a bad block on a disk, this support clears
media errors in response to a write.
---
Dan Williams (3):
nfit, libnvdimm: clear poison command support
libnvdimm, pmem: fix kmap_atomic() leak in error path
libnvdimm, pmem: clear poison on write
arch/x86/include/asm/pmem.h | 5 +++
drivers/acpi/nfit.c | 12 ++++++-
drivers/nvdimm/bus.c | 65 ++++++++++++++++++++++++++++++++++++++
drivers/nvdimm/nd.h | 2 +
drivers/nvdimm/pmem.c | 40 ++++++++++++++++++++---
include/linux/pmem.h | 19 +++++++++++
include/uapi/linux/ndctl.h | 13 ++++++++
tools/testing/nvdimm/test/nfit.c | 29 +++++++++++++++++
8 files changed, 179 insertions(+), 6 deletions(-)
next reply other threads:[~2016-03-08 22:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 22:47 Dan Williams [this message]
2016-03-08 22:47 ` [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-08 22:47 ` [PATCH 1/3] nfit, libnvdimm: clear poison command support Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-09 23:03 ` Verma, Vishal L
2016-03-09 23:03 ` Verma, Vishal L
2016-03-09 23:03 ` Verma, Vishal L
2016-03-09 23:07 ` Dan Williams
2016-03-09 23:07 ` Dan Williams
2016-03-09 23:07 ` Dan Williams
2016-03-08 22:47 ` [PATCH 2/3] libnvdimm, pmem: fix kmap_atomic() leak in error path Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-08 22:47 ` [PATCH 3/3] libnvdimm, pmem: clear poison on write Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-08 22:47 ` Dan Williams
2016-03-11 0:39 ` Verma, Vishal L
2016-03-11 0:39 ` Verma, Vishal L
2016-03-11 0:39 ` Verma, Vishal L
2016-03-11 0:50 ` Dan Williams
2016-03-11 0:50 ` Dan Williams
2016-03-11 0:50 ` Dan Williams
2016-03-09 23:05 ` [PATCH 0/3] nfit, libnvdimm, pmem: clear poison support Verma, Vishal L
2016-03-09 23:05 ` Verma, Vishal L
2016-03-09 23:05 ` Verma, Vishal L
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=20160308224713.16298.33547.stgit@dwillia2-desk3.jf.intel.com \
--to=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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.