From: Santosh Sivaraj <santosh@fossix.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Chandan Rajendra <chandan@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>
Subject: Re: [PATCH 0/3] Add bad pmem bad blocks to bad range
Date: Tue, 20 Aug 2019 08:05:12 +0530 [thread overview]
Message-ID: <87a7c4pnrz.fsf@santosiv.in.ibm.com> (raw)
In-Reply-To: <20190820023030.18232-1-santosh@fossix.org>
Santosh Sivaraj <santosh@fossix.org> writes:
> This series, which should be based on top of the still un-merged
> "powerpc: implement machine check safe memcpy" series, adds support
> to add the bad blocks which generated an MCE to the NVDIMM bad blocks.
> The next access of the same memory will be blocked by the NVDIMM layer
> itself.
This is the v2 series. Missed to add in the subject.
>
> ---
> Santosh Sivaraj (3):
> powerpc/mce: Add MCE notification chain
> of_pmem: Add memory ranges which took a mce to bad range
> papr/scm: Add bad memory ranges to nvdimm bad ranges
>
> arch/powerpc/include/asm/mce.h | 3 +
> arch/powerpc/kernel/mce.c | 15 +++
> arch/powerpc/platforms/pseries/papr_scm.c | 86 +++++++++++-
> drivers/nvdimm/of_pmem.c | 151 +++++++++++++++++++---
> 4 files changed, 234 insertions(+), 21 deletions(-)
>
> --
> 2.21.0
next prev parent reply other threads:[~2019-08-20 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 2:30 [PATCH 0/3] Add bad pmem bad blocks to bad range Santosh Sivaraj
2019-08-20 2:30 ` [PATCH 1/3] powerpc/mce: Add MCE notification chain Santosh Sivaraj
2019-08-20 2:30 ` [PATCH 2/3] of_pmem: Add memory ranges which took a mce to bad range Santosh Sivaraj
2019-08-20 8:41 ` Oliver O'Halloran
2019-08-20 2:30 ` [PATCH 3/3] papr/scm: Add bad memory ranges to nvdimm bad ranges Santosh Sivaraj
2019-08-20 2:35 ` Santosh Sivaraj [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-14 8:24 [PATCH 0/3] Add bad pmem bad blocks to bad range Santosh Sivaraj
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=87a7c4pnrz.fsf@santosiv.in.ibm.com \
--to=santosh@fossix.org \
--cc=chandan@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).