From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Santosh Sivaraj <santosh@fossix.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Reza Arbab <arbab@linux.ibm.com>
Subject: Re: [v3 4/7] powerpc/mce: Handle UE event for memcpy_mcsafe
Date: Mon, 8 Jul 2019 13:53:12 +0530 [thread overview]
Message-ID: <b32144b5-c97b-0292-cab6-7290c906e9e2@linux.vnet.ibm.com> (raw)
In-Reply-To: <1562406379.9eh1e6edgk.astroid@bobo.none>
On 7/6/19 3:23 PM, Nicholas Piggin wrote:
> Santosh Sivaraj's on July 6, 2019 7:26 am:
>> If we take a UE on one of the instructions with a fixup entry, set nip
>> to continue exucution at the fixup entry. Stop processing the event
>> further or print it.
>
> Minor nit, but can you instead a field in the mce data structure that
> describes the property of the event, and then the code that intends to
> ignore such events can test for it (with an appropriate comment).
>
> So it would be has_fixup_handler or similar. Then queue_event can have
> the logic
>
> /*
> * Don't report this machine check because the caller has a fixup
> * handler which will do the appropriate error handling and reporting.
> */
>
>
>> @@ -565,9 +567,18 @@ static int mce_handle_derror(struct pt_regs *regs,
>> return 0;
>> }
>>
>> -static long mce_handle_ue_error(struct pt_regs *regs)
>> +static long mce_handle_ue_error(struct pt_regs *regs,
>> + struct mce_error_info *mce_err)
>> {
>> long handled = 0;
>> + const struct exception_table_entry *entry;
>> +
>> + entry = search_exception_tables(regs->nip);
>
> Uh oh, this searches module exception tables too... we can't do that
> in real mode, can we?
Yeah, we can not do that in real mode. Should we directly call
search_extable() for kernel exception table ?
>
> Thanks,
> Nick
>
next prev parent reply other threads:[~2019-07-08 8:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:26 [v3 0/7] powerpc: implement machine check safe memcpy Santosh Sivaraj
2019-07-05 21:26 ` [v3 1/7] powerpc/mce: Make machine_check_ue_event() static Santosh Sivaraj
2019-07-06 5:18 ` Nicholas Piggin
2019-07-05 21:26 ` [v3 2/7] powerpc/mce: Bug fixes for MCE handling in kernel space Santosh Sivaraj
2019-07-06 9:44 ` Nicholas Piggin
2019-07-05 21:26 ` [v3 3/7] powerpc/memcpy: Add memcpy_mcsafe for pmem Santosh Sivaraj
2019-07-06 6:12 ` Christophe Leroy
2019-07-05 21:26 ` [v3 4/7] powerpc/mce: Handle UE event for memcpy_mcsafe Santosh Sivaraj
2019-07-06 9:53 ` Nicholas Piggin
2019-07-08 8:23 ` Mahesh Jagannath Salgaonkar [this message]
2019-07-05 21:26 ` [v3 5/7] powerpc/memcpy_mcsafe: return remaining bytes Santosh Sivaraj
2019-07-06 6:16 ` Christophe Leroy
2019-07-06 10:05 ` Nicholas Piggin
2019-07-05 21:26 ` [v3 6/7] powerpc: add machine check safe copy_to_user Santosh Sivaraj
2019-07-06 6:19 ` Christophe Leroy
2019-07-05 21:26 ` [v3 7/7] powerpc/64s: save r13 in MCE handler (simulator workaroud) Santosh Sivaraj
2019-07-06 9:56 ` Nicholas Piggin
2019-07-08 15:11 ` Reza Arbab
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=b32144b5-c97b-0292-cab6-7290c906e9e2@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arbab@linux.ibm.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--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).