[PATCH v7 7/9] powerpc/pseries: Dump the SLB contents on SLB MCE errors.
Aneesh Kumar K.V
aneesh.kumar at linux.ibm.com
Tue Aug 14 22:47:26 AEST 2018
On 08/14/2018 04:27 PM, Mahesh Jagannath Salgaonkar wrote:
> On 08/13/2018 07:57 PM, Nicholas Piggin wrote:
>> On Mon, 13 Aug 2018 09:47:04 +0530
>> Mahesh Jagannath Salgaonkar <mahesh at linux.vnet.ibm.com> wrote:
>>
>>> On 08/11/2018 10:03 AM, Nicholas Piggin wrote:
>>>> On Tue, 07 Aug 2018 19:47:39 +0530
>>>> Mahesh J Salgaonkar <mahesh at linux.vnet.ibm.com> wrote:
>>>>
>>>>> From: Mahesh Salgaonkar <mahesh at linux.vnet.ibm.com>
>>>>>
>>>>> If we get a machine check exceptions due to SLB errors then dump the
>>>>> current SLB contents which will be very much helpful in debugging the
>>>>> root cause of SLB errors. Introduce an exclusive buffer per cpu to hold
>>>>> faulty SLB entries. In real mode mce handler saves the old SLB contents
>>>>> into this buffer accessible through paca and print it out later in virtual
>>>>> mode.
>>>>>
>>>>> With this patch the console will log SLB contents like below on SLB MCE
>>>>> errors:
>>>>>
>>>>> [ 507.297236] SLB contents of cpu 0x1
>>>>> [ 507.297237] Last SLB entry inserted at slot 16
>>>>> [ 507.297238] 00 c000000008000000 400ea1b217000500
>>>>> [ 507.297239] 1T ESID= c00000 VSID= ea1b217 LLP:100
>>>>> [ 507.297240] 01 d000000008000000 400d43642f000510
>>>>> [ 507.297242] 1T ESID= d00000 VSID= d43642f LLP:110
>>>>> [ 507.297243] 11 f000000008000000 400a86c85f000500
>>>>> [ 507.297244] 1T ESID= f00000 VSID= a86c85f LLP:100
>>>>> [ 507.297245] 12 00007f0008000000 4008119624000d90
>>>>> [ 507.297246] 1T ESID= 7f VSID= 8119624 LLP:110
>>>>> [ 507.297247] 13 0000000018000000 00092885f5150d90
>>>>> [ 507.297247] 256M ESID= 1 VSID= 92885f5150 LLP:110
>>>>> [ 507.297248] 14 0000010008000000 4009e7cb50000d90
>>>>> [ 507.297249] 1T ESID= 1 VSID= 9e7cb50 LLP:110
>>>>> [ 507.297250] 15 d000000008000000 400d43642f000510
>>>>> [ 507.297251] 1T ESID= d00000 VSID= d43642f LLP:110
>>>>> [ 507.297252] 16 d000000008000000 400d43642f000510
>>>>> [ 507.297253] 1T ESID= d00000 VSID= d43642f LLP:110
>>>>> [ 507.297253] ----------------------------------
>>>>> [ 507.297254] SLB cache ptr value = 3
>>>>> [ 507.297254] Valid SLB cache entries:
>>>>> [ 507.297255] 00 EA[0-35]= 7f000
>>>>> [ 507.297256] 01 EA[0-35]= 1
>>>>> [ 507.297257] 02 EA[0-35]= 1000
>>>>> [ 507.297257] Rest of SLB cache entries:
>>>>> [ 507.297258] 03 EA[0-35]= 7f000
>>>>> [ 507.297258] 04 EA[0-35]= 1
>>>>> [ 507.297259] 05 EA[0-35]= 1000
>>>>> [ 507.297260] 06 EA[0-35]= 12
>>>>> [ 507.297260] 07 EA[0-35]= 7f000
>>>>>
>>>>> Suggested-by: Aneesh Kumar K.V <aneesh.kumar at linux.vnet.ibm.com>
>>>>> Suggested-by: Michael Ellerman <mpe at ellerman.id.au>
>>>>> Signed-off-by: Mahesh Salgaonkar <mahesh at linux.vnet.ibm.com>
>>>>> ---
>>>>>
>>>>> Changes in V7:
>>>>> - Print slb cache ptr value and slb cache data
>>>>> ---
>>>>> arch/powerpc/include/asm/book3s/64/mmu-hash.h | 7 ++
>>>>> arch/powerpc/include/asm/paca.h | 4 +
>>>>> arch/powerpc/mm/slb.c | 73 +++++++++++++++++++++++++
>>>>> arch/powerpc/platforms/pseries/ras.c | 10 +++
>>>>> arch/powerpc/platforms/pseries/setup.c | 10 +++
>>>>> 5 files changed, 103 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/arch/powerpc/include/asm/book3s/64/mmu-hash.h b/arch/powerpc/include/asm/book3s/64/mmu-hash.h
>>>>> index cc00a7088cf3..5a3fe282076d 100644
>>>>> --- a/arch/powerpc/include/asm/book3s/64/mmu-hash.h
>>>>> +++ b/arch/powerpc/include/asm/book3s/64/mmu-hash.h
>>>>> @@ -485,9 +485,16 @@ static inline void hpte_init_pseries(void) { }
>>>>>
>>>>> extern void hpte_init_native(void);
>>>>>
>>>>> +struct slb_entry {
>>>>> + u64 esid;
>>>>> + u64 vsid;
>>>>> +};
>>>>> +
>>>>> extern void slb_initialize(void);
>>>>> extern void slb_flush_and_rebolt(void);
>>>>> extern void slb_flush_and_rebolt_realmode(void);
>>>>> +extern void slb_save_contents(struct slb_entry *slb_ptr);
>>>>> +extern void slb_dump_contents(struct slb_entry *slb_ptr);
>>>>>
>>>>> extern void slb_vmalloc_update(void);
>>>>> extern void slb_set_size(u16 size);
>>>>> diff --git a/arch/powerpc/include/asm/paca.h b/arch/powerpc/include/asm/paca.h
>>>>> index 7f22929ce915..233d25ff6f64 100644
>>>>> --- a/arch/powerpc/include/asm/paca.h
>>>>> +++ b/arch/powerpc/include/asm/paca.h
>>>>> @@ -254,6 +254,10 @@ struct paca_struct {
>>>>> #endif
>>>>> #ifdef CONFIG_PPC_PSERIES
>>>>> u8 *mce_data_buf; /* buffer to hold per cpu rtas errlog */
>>>>> +
>>>>> + /* Capture SLB related old contents in MCE handler. */
>>>>> + struct slb_entry *mce_faulty_slbs;
>>>>> + u16 slb_save_cache_ptr;
>>>>> #endif /* CONFIG_PPC_PSERIES */
>>>>> } ____cacheline_aligned;
>>>>>
>>>>> diff --git a/arch/powerpc/mm/slb.c b/arch/powerpc/mm/slb.c
>>>>> index e89f675f1b5e..16a53689ffd4 100644
>>>>> --- a/arch/powerpc/mm/slb.c
>>>>> +++ b/arch/powerpc/mm/slb.c
>>>>> @@ -151,6 +151,79 @@ void slb_flush_and_rebolt_realmode(void)
>>>>> get_paca()->slb_cache_ptr = 0;
>>>>> }
>>>>>
>>>>> +void slb_save_contents(struct slb_entry *slb_ptr)
>>>>> +{
>>>>> + int i;
>>>>> + unsigned long e, v;
>>>>> +
>>>>> + /* Save slb_cache_ptr value. */
>>>>> + get_paca()->slb_save_cache_ptr = get_paca()->slb_cache_ptr;
>>>>
>>>> What's the point of saving this?
>>>
>>> This is to know how many valid cache entries were present at the time of
>>> SLB mutlihit. We use this index value while dumping the slb cahce entries.
>>
>> Oh I see you're dumping that thing as well. I don't know if that's
>> worth doing, it just gives you the first 8 SLB entries installed but
>> you already have those (or they're overwritten and irrelevat).
>
> Aneesh, Can you comment on this ?
>
>
We never clear slb_cache entries. We just update slb_cache_ptr. Now on
debug we would like to find which entries are the valid
slb_cache_entries for this run. slb_cache_ptr gives us that details.
One of the ways we could end up with a slb multi hit is if we have
slb_cache_ptr corruption. So instead of doing a flush_and_rebolt, we
invalidated a subset of valid slb entries. But I understand that in that
specific case, we context switched out with that corrupted value and the
value we are dumping above really won't help in isolating. But if we are
corrupting paca, we might continue to overwrite it again and we can
compare the slb contents against slb_cache contents and see if there is
any corruption.
-aneesh
More information about the Linuxppc-dev
mailing list