From: Vishal Verma <vishal.l.verma@intel.com> To: linux-nvdimm@lists.01.org Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>, linux-acpi@vger.kernel.org Subject: [PATCH 0/3] misc updates for Address Range Scrub Date: Fri, 30 Sep 2016 17:19:28 -0600 [thread overview] Message-ID: <1475277571-10152-1-git-send-email-vishal.l.verma@intel.com> (raw) Changes in v3: - Rename MCE_SCRUB* to HW_ERROR_SCRUB* (Dan) - Make the default scrub_mode '0' so it doesn't have to be set explicitly (Dan) Changes in v2: - Change the 'scrub' attribute to only show the number of completed scrubs, and start a new one ondemand. (Dan) - Add a new attribute 'hw_error_scrub' which controls whether or not a full scrub will run on hardware memory errors. (Dan) Patch 1 changes the default behaviour on machine check exceptions to just adding the error address to badblocks accounting instead of starting a full ARS. The old behaviour can be enabled via sysfs. Patch 2 and 3 fix a problem where stale badblocks could show up after an on-demand ARS or an MCE triggered scrub, or even a namespace disable/enable cycle because when clearing poison, we didn't clear the internal nvdimm_bus->poison_list. Vishal Verma (3): nfit: don't start a full scrub by default for an MCE pmem: reduce kmap_atomic sections to the memcpys only libnvdimm: clear the internal poison_list when clearing badblocks drivers/acpi/nfit/core.c | 53 ++++++++++++++++++++++++++++++++++ drivers/acpi/nfit/mce.c | 24 ++++++++++++---- drivers/acpi/nfit/nfit.h | 6 ++++ drivers/nvdimm/bus.c | 2 ++ drivers/nvdimm/core.c | 73 ++++++++++++++++++++++++++++++++++++++++++++--- drivers/nvdimm/pmem.c | 28 ++++++++++++++---- include/linux/libnvdimm.h | 2 ++ 7 files changed, 174 insertions(+), 14 deletions(-) -- 2.7.4 _______________________________________________ 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: Vishal Verma <vishal.l.verma@intel.com> To: linux-nvdimm@lists.01.org Cc: Dan Williams <dan.j.williams@intel.com>, Ross Zwisler <ross.zwisler@linux.intel.com>, Linda Knippers <linda.knippers@hpe.com>, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>, Vishal Verma <vishal.l.verma@intel.com> Subject: [PATCH 0/3] misc updates for Address Range Scrub Date: Fri, 30 Sep 2016 17:19:28 -0600 [thread overview] Message-ID: <1475277571-10152-1-git-send-email-vishal.l.verma@intel.com> (raw) Changes in v3: - Rename MCE_SCRUB* to HW_ERROR_SCRUB* (Dan) - Make the default scrub_mode '0' so it doesn't have to be set explicitly (Dan) Changes in v2: - Change the 'scrub' attribute to only show the number of completed scrubs, and start a new one ondemand. (Dan) - Add a new attribute 'hw_error_scrub' which controls whether or not a full scrub will run on hardware memory errors. (Dan) Patch 1 changes the default behaviour on machine check exceptions to just adding the error address to badblocks accounting instead of starting a full ARS. The old behaviour can be enabled via sysfs. Patch 2 and 3 fix a problem where stale badblocks could show up after an on-demand ARS or an MCE triggered scrub, or even a namespace disable/enable cycle because when clearing poison, we didn't clear the internal nvdimm_bus->poison_list. Vishal Verma (3): nfit: don't start a full scrub by default for an MCE pmem: reduce kmap_atomic sections to the memcpys only libnvdimm: clear the internal poison_list when clearing badblocks drivers/acpi/nfit/core.c | 53 ++++++++++++++++++++++++++++++++++ drivers/acpi/nfit/mce.c | 24 ++++++++++++---- drivers/acpi/nfit/nfit.h | 6 ++++ drivers/nvdimm/bus.c | 2 ++ drivers/nvdimm/core.c | 73 ++++++++++++++++++++++++++++++++++++++++++++--- drivers/nvdimm/pmem.c | 28 ++++++++++++++---- include/linux/libnvdimm.h | 2 ++ 7 files changed, 174 insertions(+), 14 deletions(-) -- 2.7.4
next reply other threads:[~2016-09-30 23:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-30 23:19 Vishal Verma [this message] 2016-09-30 23:19 ` [PATCH 0/3] misc updates for Address Range Scrub Vishal Verma 2016-09-30 23:19 ` [PATCH 1/3] nfit: don't start a full scrub by default for an MCE Vishal Verma 2016-09-30 23:19 ` Vishal Verma 2016-09-30 23:19 ` [PATCH 2/3] pmem: reduce kmap_atomic sections to the memcpys only Vishal Verma 2016-09-30 23:19 ` Vishal Verma 2016-09-30 23:19 ` [PATCH 3/3] libnvdimm: clear the internal poison_list when clearing badblocks Vishal Verma 2016-09-30 23:19 ` Vishal Verma -- strict thread matches above, loose matches on Subject: below -- 2016-09-29 0:10 [PATCH 0/3] misc updates for Address Range Scrub Vishal Verma 2016-09-29 0:10 ` Vishal Verma
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=1475277571-10152-1-git-send-email-vishal.l.verma@intel.com \ --to=vishal.l.verma@intel.com \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=rafael.j.wysocki@intel.com \ /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: linkBe 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.