From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] nfit, address-range-scrub: rework and fixes
Date: Sat, 07 Apr 2018 08:45:52 -0700 [thread overview]
Message-ID: <152311595210.35426.13667585208560808244.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
Changes since v2 [1]:
* Handle -EAGAIN (no result) ars_status responses
---
Given the fact that ARS can take 10s to 100s of seconds it is not
feasible to wait for ARS completion before publishing persistent memory
namespaces. Instead convert the ARS implementation to perform a short
ARS for critical errors, ones that caused a previous system reset,
before registering namespaces. Finally, arrange for all long ARS
operations to run in the background and populate the badblock lists at
run time.
In the extreme situation that an implementation is unable to return
sufficient results in a short scan and the system encounters media
errors that machine check recovery does not handle, an administrator can
arrange to wait for a full ARS scan by doing the following:
1/ Boot with "modprobe.blacklist=nd_pmem" to stop pmem namespaces from
starting automatically
2/ Call "ndctl wait-scrub" to wait for the OS or BIOS initiated ARS to complete
3/ Manually start up namespaces with the up to date error list
"modprobe nd_pmem"
---
Dan Williams (3):
nfit, address-range-scrub: determine one platform max_ars value
nfit, address-range-scrub: rework and simplify ARS state machine
nfit, address-range-scrub: add module option to skip initial ars
drivers/acpi/nfit/core.c | 557 +++++++++++++++++++++-------------------------
drivers/acpi/nfit/nfit.h | 6
2 files changed, 261 insertions(+), 302 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Cc: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/3] nfit, address-range-scrub: rework and fixes
Date: Sat, 07 Apr 2018 08:45:52 -0700 [thread overview]
Message-ID: <152311595210.35426.13667585208560808244.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
Changes since v2 [1]:
* Handle -EAGAIN (no result) ars_status responses
---
Given the fact that ARS can take 10s to 100s of seconds it is not
feasible to wait for ARS completion before publishing persistent memory
namespaces. Instead convert the ARS implementation to perform a short
ARS for critical errors, ones that caused a previous system reset,
before registering namespaces. Finally, arrange for all long ARS
operations to run in the background and populate the badblock lists at
run time.
In the extreme situation that an implementation is unable to return
sufficient results in a short scan and the system encounters media
errors that machine check recovery does not handle, an administrator can
arrange to wait for a full ARS scan by doing the following:
1/ Boot with "modprobe.blacklist=nd_pmem" to stop pmem namespaces from
starting automatically
2/ Call "ndctl wait-scrub" to wait for the OS or BIOS initiated ARS to complete
3/ Manually start up namespaces with the up to date error list
"modprobe nd_pmem"
---
Dan Williams (3):
nfit, address-range-scrub: determine one platform max_ars value
nfit, address-range-scrub: rework and simplify ARS state machine
nfit, address-range-scrub: add module option to skip initial ars
drivers/acpi/nfit/core.c | 557 +++++++++++++++++++++-------------------------
drivers/acpi/nfit/nfit.h | 6
2 files changed, 261 insertions(+), 302 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Dave Jiang <dave.jiang@intel.com>,
Toshi Kani <toshi.kani@hpe.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] nfit, address-range-scrub: rework and fixes
Date: Sat, 07 Apr 2018 08:45:52 -0700 [thread overview]
Message-ID: <152311595210.35426.13667585208560808244.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
Changes since v2 [1]:
* Handle -EAGAIN (no result) ars_status responses
---
Given the fact that ARS can take 10s to 100s of seconds it is not
feasible to wait for ARS completion before publishing persistent memory
namespaces. Instead convert the ARS implementation to perform a short
ARS for critical errors, ones that caused a previous system reset,
before registering namespaces. Finally, arrange for all long ARS
operations to run in the background and populate the badblock lists at
run time.
In the extreme situation that an implementation is unable to return
sufficient results in a short scan and the system encounters media
errors that machine check recovery does not handle, an administrator can
arrange to wait for a full ARS scan by doing the following:
1/ Boot with "modprobe.blacklist=nd_pmem" to stop pmem namespaces from
starting automatically
2/ Call "ndctl wait-scrub" to wait for the OS or BIOS initiated ARS to complete
3/ Manually start up namespaces with the up to date error list
"modprobe nd_pmem"
---
Dan Williams (3):
nfit, address-range-scrub: determine one platform max_ars value
nfit, address-range-scrub: rework and simplify ARS state machine
nfit, address-range-scrub: add module option to skip initial ars
drivers/acpi/nfit/core.c | 557 +++++++++++++++++++++-------------------------
drivers/acpi/nfit/nfit.h | 6
2 files changed, 261 insertions(+), 302 deletions(-)
next reply other threads:[~2018-04-07 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 15:45 Dan Williams [this message]
2018-04-07 15:45 ` [PATCH v3 0/3] nfit, address-range-scrub: rework and fixes Dan Williams
2018-04-07 15:45 ` Dan Williams
2018-04-07 15:45 ` [PATCH v3 1/3] nfit, address-range-scrub: determine one platform max_ars value Dan Williams
2018-04-07 15:45 ` Dan Williams
2018-04-07 15:45 ` Dan Williams
2018-04-07 15:46 ` [PATCH v3 2/3] nfit, address-range-scrub: rework and simplify ARS state machine Dan Williams
2018-04-07 15:46 ` Dan Williams
2018-04-07 15:46 ` Dan Williams
2018-04-07 15:46 ` [PATCH v3 3/3] nfit, address-range-scrub: add module option to skip initial ars Dan Williams
2018-04-07 15:46 ` Dan Williams
2018-04-07 15:46 ` 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=152311595210.35426.13667585208560808244.stgit@dwillia2-desk3.amr.corp.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 \
/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.