From: Ganesh <ganeshgr@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: aneesh.kumar@linux.ibm.com, santosh@fossix.org,
arbab@linux.ibm.com, mahesh@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/mce: Add MCE notification chain
Date: Sat, 4 Apr 2020 18:35:23 +0530 [thread overview]
Message-ID: <a9b03938-5053-3c44-217b-5892533bd38d@linux.ibm.com> (raw)
In-Reply-To: <1585879413.ubv3w8ta2y.astroid@bobo.none>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On 4/3/20 7:38 AM, Nicholas Piggin wrote:
> Ganesh Goudar's on March 30, 2020 5:12 pm:
>> From: Santosh S <santosh@fossix.org>
>>
>> Introduce notification chain which lets know about uncorrected memory
>> errors(UE). This would help prospective users in pmem or nvdimm subsystem
>> to track bad blocks for better handling of persistent memory allocations.
>>
>> Signed-off-by: Santosh S <santosh@fossix.org>
>> Signed-off-by: Ganesh Goudar <ganeshgr@linux.ibm.com>
> Do you have any such users yet? It would be good to refer to an example
> user and give a brief description of what it does in its notifier.
Santosh has sent a patch which uses this notification.
https://patchwork.ozlabs.org/patch/1265062/
>> @@ -263,6 +277,7 @@ static void machine_process_ue_event(struct work_struct *work)
>> while (__this_cpu_read(mce_ue_count) > 0) {
>> index = __this_cpu_read(mce_ue_count) - 1;
>> evt = this_cpu_ptr(&mce_ue_event_queue[index]);
>> + blocking_notifier_call_chain(&mce_notifier_list, 0, evt);
> Can we really use a blocking notifier here? I'm not sure that we can.
I think we can, do you see any problem?
>
> Thanks,
> Nick
[-- Attachment #2: Type: text/html, Size: 2393 bytes --]
next prev parent reply other threads:[~2020-04-04 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:12 [PATCH] powerpc/mce: Add MCE notification chain Ganesh Goudar
2020-04-03 2:08 ` Nicholas Piggin
2020-04-04 13:05 ` Ganesh [this message]
2020-04-06 2:17 ` Nicholas Piggin
2020-04-06 17:17 ` Mahesh J Salgaonkar
2020-05-04 6:39 ` Ganesh
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=a9b03938-5053-3c44-217b-5892533bd38d@linux.ibm.com \
--to=ganeshgr@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arbab@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=santosh@fossix.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 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).