From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v4 5/5] powerpc/mce: hookup memory_failure for UE errors
Date: Mon, 16 Oct 2017 16:40:19 +1100 [thread overview]
Message-ID: <CAKTCnzkH=5i23F9v2t-VLZET2HV86NP8u=rx9gEswG5COTJ1kw@mail.gmail.com> (raw)
In-Reply-To: <87infflkjm.fsf@concordia.ellerman.id.au>
On Mon, Oct 16, 2017 at 4:38 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> Balbir Singh <bsingharora@gmail.com> writes:
>
>> If we are in user space and hit a UE error, we now have the
>> basic infrastructure to walk the page tables and find out
>> the effective address that was accessed, since the DAR
>> is not valid.
>>
>> We use a work_queue content to hookup the bad pfn, any
>> other context causes problems, since memory_failure itself
>> can call into schedule() via lru_drain_ bits.
>>
>> We could probably poison the struct page to avoid a race
>> between detection and taking corrective action.
>>
>> Signed-off-by: Balbir Singh <bsingharora@gmail.com>
>> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
>> ---
>> arch/powerpc/kernel/mce.c | 70 +++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 67 insertions(+), 3 deletions(-)
>
> I'm not sure why this is in mce.c but the rest was in mce_power.c ?
The way the code is organized is that save_mce_event is implemented here
and called from mce_power.c. save_mce_event() does the processing
of the event.
Balbir Singh.
next prev parent reply other threads:[~2017-10-16 5:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 4:26 [PATCH v4 0/5] Revisit MCE handling for UE Errors Balbir Singh
2017-09-29 4:26 ` [PATCH v4 1/5] powerpc/mce.c: Remove unused function get_mce_fault_addr() Balbir Singh
2017-10-16 5:13 ` Michael Ellerman
2017-10-16 5:23 ` Balbir Singh
2017-10-19 4:48 ` [v4, " Michael Ellerman
2017-09-29 4:26 ` [PATCH v4 2/5] powerpc/mce: align the print of physical address better Balbir Singh
2017-10-16 5:18 ` Michael Ellerman
2017-10-16 5:36 ` Balbir Singh
2017-09-29 4:26 ` [PATCH v4 3/5] powerpc/mce: Hookup derror (load/store) UE errors Balbir Singh
2017-10-16 5:36 ` Michael Ellerman
2017-10-16 5:38 ` Balbir Singh
2017-09-29 4:26 ` [PATCH v4 4/5] powerpc/mce: Hookup ierror (instruction) " Balbir Singh
2017-09-29 4:26 ` [PATCH v4 5/5] powerpc/mce: hookup memory_failure for " Balbir Singh
2017-10-16 5:38 ` Michael Ellerman
2017-10-16 5:40 ` Balbir Singh [this message]
2017-10-16 12:07 ` Michael Ellerman
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='CAKTCnzkH=5i23F9v2t-VLZET2HV86NP8u=rx9gEswG5COTJ1kw@mail.gmail.com' \
--to=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).