[PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

Presently, while reading a vmcore, makedumpfile uses
`cur_cpu_spec.mmu_features` to decide whether the crashed system had
RADIX MMU or not.

Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
a vmlinux is passed with the `-x` flag to makedumpfile), and hence
assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
MMU to be hash MMU.

Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
`cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
is accessible to makedumpfile, without needing the vmlinux file

Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
---
 arch/powerpc/kexec/core.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/powerpc/kexec/core.c b/arch/powerpc/kexec/core.c
index de64c7962991..369b8334a4f0 100644
--- a/arch/powerpc/kexec/core.c
+++ b/arch/powerpc/kexec/core.c
@@ -63,6 +63,8 @@ void arch_crash_save_vmcoreinfo(void)
 #ifndef CONFIG_NUMA
 	VMCOREINFO_SYMBOL(contig_page_data);
 #endif
+	VMCOREINFO_SYMBOL(cur_cpu_spec);
+	VMCOREINFO_OFFSET(cpu_spec, mmu_features);
 #if defined(CONFIG_PPC64) && defined(CONFIG_SPARSEMEM_VMEMMAP)
 	VMCOREINFO_SYMBOL(vmemmap_list);
 	VMCOREINFO_SYMBOL(mmu_vmemmap_psize);
-- 
2.41.0

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Sachin Sant]

> On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
> 
> Presently, while reading a vmcore, makedumpfile uses
> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> RADIX MMU or not.
> 
> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> MMU to be hash MMU.
> 
> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> is accessible to makedumpfile, without needing the vmlinux file
> 
> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> ---

Thanks for the patch. With this patch applied (along with makedumpfile changes)
I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e

Reported-by: Sachin Sant <sachinp@linux.ibm.com>
Tested-by: Sachin Sant <sachinp@linux.ibm.com>

- Sachin

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

Hello Sachin,

On Wed, Sep 13, 2023 at 06:19:11PM +0530, Sachin Sant wrote:
> 
> 
> > On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
> > 
> > Presently, while reading a vmcore, makedumpfile uses
> > `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> > RADIX MMU or not.
> > 
> > Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> > a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> > assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> > MMU to be hash MMU.
> > 
> > Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> > `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> > is accessible to makedumpfile, without needing the vmlinux file
> > 
> > Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> > ---
> 
> Thanks for the patch. With this patch applied (along with makedumpfile changes)
> I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e
> 
> Reported-by: Sachin Sant <sachinp@linux.ibm.com>
> Tested-by: Sachin Sant <sachinp@linux.ibm.com>

Thanks for testing this, and for providing the tags.

- Aditya Gupta

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Michael Ellerman]

Sachin Sant <sachinp@linux.ibm.com> writes:
>> On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
>> 
>> Presently, while reading a vmcore, makedumpfile uses
>> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
>> RADIX MMU or not.
>> 
>> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
>> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
>> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
>> MMU to be hash MMU.
>> 
>> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
>> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
>> is accessible to makedumpfile, without needing the vmlinux file
>> 
>> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
>> ---
>
> Thanks for the patch. With this patch applied (along with makedumpfile changes)
> I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e

I can't find that commit? Was just wondering if it should be referenced
in the commit message.

cheers

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Sachin Sant]

> On 14-Sep-2023, at 6:52 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> 
> Sachin Sant <sachinp@linux.ibm.com> writes:
>>> On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
>>> 
>>> Presently, while reading a vmcore, makedumpfile uses
>>> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
>>> RADIX MMU or not.
>>> 
>>> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
>>> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
>>> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
>>> MMU to be hash MMU.
>>> 
>>> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
>>> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
>>> is accessible to makedumpfile, without needing the vmlinux file
>>> 
>>> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
>>> ---
>> 
>> Thanks for the patch. With this patch applied (along with makedumpfile changes)
>> I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e
> 
> I can't find that commit? Was just wondering if it should be referenced
> in the commit message.
> 

My bad, I copied that commit id from the email when I first reported this issue
against linux-next.

The commit should be 
368a0590d954: (powerpc/book3s64/vmemmap: switch radix to use a
different vmemmap handling function)

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Michael Ellerman]

Sachin Sant <sachinp@linux.ibm.com> writes:
>> On 14-Sep-2023, at 6:52 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> 
>> Sachin Sant <sachinp@linux.ibm.com> writes:
>>>> On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
>>>> 
>>>> Presently, while reading a vmcore, makedumpfile uses
>>>> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
>>>> RADIX MMU or not.
>>>> 
>>>> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
>>>> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
>>>> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
>>>> MMU to be hash MMU.
>>>> 
>>>> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
>>>> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
>>>> is accessible to makedumpfile, without needing the vmlinux file
>>>> 
>>>> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
>>>> ---
>>> 
>>> Thanks for the patch. With this patch applied (along with makedumpfile changes)
>>> I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e
>> 
>> I can't find that commit? Was just wondering if it should be referenced
>> in the commit message.
>> 
>
> My bad, I copied that commit id from the email when I first reported this issue
> against linux-next.
>
> The commit should be 
> 368a0590d954: (powerpc/book3s64/vmemmap: switch radix to use a
> different vmemmap handling function)

OK thanks.

Aditya, can you please rephrase the commit message to mention how that
commit broke the previous behaviour.

Also I don't know what pgd_offset_l4 is?

cheers

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

Hello mpe,

On Fri, Sep 15, 2023 at 11:16:08AM +1000, Michael Ellerman wrote:
> Sachin Sant <sachinp@linux.ibm.com> writes:
> >> On 14-Sep-2023, at 6:52 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> >> 
> >> Sachin Sant <sachinp@linux.ibm.com> writes:
> >>>> On 11-Sep-2023, at 2:44 PM, Aditya Gupta <adityag@linux.ibm.com> wrote:
> >>>> 
> >>>> Presently, while reading a vmcore, makedumpfile uses
> >>>> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> >>>> RADIX MMU or not.
> >>>> 
> >>>> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> >>>> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> >>>> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> >>>> MMU to be hash MMU.
> >>>> 
> >>>> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> >>>> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> >>>> is accessible to makedumpfile, without needing the vmlinux file
> >>>> 
> >>>> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> >>>> ---
> >>> 
> >>> Thanks for the patch. With this patch applied (along with makedumpfile changes)
> >>> I am able to capture vmcore against a kernel which contains commit 8dc9a0ad0c3e
> >> 
> >> I can't find that commit? Was just wondering if it should be referenced
> >> in the commit message.
> >> 
> >
> > My bad, I copied that commit id from the email when I first reported this issue
> > against linux-next.
> >
> > The commit should be 
> > 368a0590d954: (powerpc/book3s64/vmemmap: switch radix to use a
> > different vmemmap handling function)
> 
> OK thanks.
> 
> Aditya, can you please rephrase the commit message to mention how that
> commit broke the previous behaviour.

Offsets were being wrongly assigned, in makedumpfile, in Radix MMU case (unless
-x vmlinux was passed to makedumpfile, which generally isn't the case)

That was happening even before the '368a0590d954' commit mentioned, it's just
that we hit the issue now, since with above commit, we needed to use those
offsets for page traversal, in makedumpfile. And those offsets were incorrecly
assigned, and hence page traversal failed.

For the offsets/shifts to be correctly assigned in makedumpfile,
`cur_cpu_spec.mmu_features` needs to be exported in VMCOREINFO by kernel.

> 
> Also I don't know what pgd_offset_l4 is?

Sure, I will try to explain with more context in commit description in next
version, or directly mention the particular shifts that was wrong.

In makedumpfile, it is the offset of pgdir from the kernel pgd, for a given
virtual address

It is same as what the `pgd_index` function returns, in the powerpc
kernel source.

> 
> cheers

Thanks

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Michael Ellerman]

Aditya Gupta <adityag@linux.ibm.com> writes:
> Presently, while reading a vmcore, makedumpfile uses
> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> RADIX MMU or not.
>
> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> MMU to be hash MMU.
>
> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> is accessible to makedumpfile, without needing the vmlinux file

This looks fine.

Seems like cpu_features would be needed or at least pretty useful too?

cheers

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Hari Bathini]

On 14/09/23 6:52 pm, Michael Ellerman wrote:
> Aditya Gupta <adityag@linux.ibm.com> writes:
>> Presently, while reading a vmcore, makedumpfile uses
>> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
>> RADIX MMU or not.
>>
>> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
>> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
>> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
>> MMU to be hash MMU.
>>
>> Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
>> `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
>> is accessible to makedumpfile, without needing the vmlinux file
> 
> This looks fine.
> 
> Seems like cpu_features would be needed or at least pretty useful too?

Yeah. Would be nice to have access to that, to accurately identify the
kind of system vmcore was generated for.

Thanks
Hari

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

On Thu, Sep 14, 2023 at 11:22:01PM +1000, Michael Ellerman wrote:
> Aditya Gupta <adityag@linux.ibm.com> writes:
> > Presently, while reading a vmcore, makedumpfile uses
> > `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> > RADIX MMU or not.
> >
> > Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> > a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> > assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> > MMU to be hash MMU.
> >
> > Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> > `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> > is accessible to makedumpfile, without needing the vmlinux file
> 
> This looks fine.
> 
> Seems like cpu_features would be needed or at least pretty useful too?
> 
> cheers

Sure, that can be added too, to the vmcoreinfo. Not sure if it's used now, but
sure it can help to identify features in makedumpfile.

Will add it, in next version.

Thanks
- Aditya Gupta

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Michael Ellerman]

Aditya Gupta <adityag@linux.ibm.com> writes:
> On Thu, Sep 14, 2023 at 11:22:01PM +1000, Michael Ellerman wrote:
>> Aditya Gupta <adityag@linux.ibm.com> writes:
>> > Presently, while reading a vmcore, makedumpfile uses
>> > `cur_cpu_spec.mmu_features` to decide whether the crashed system had
>> > RADIX MMU or not.
>> >
>> > Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
>> > a vmlinux is passed with the `-x` flag to makedumpfile), and hence
>> > assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
>> > MMU to be hash MMU.
>> >
>> > Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
>> > `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
>> > is accessible to makedumpfile, without needing the vmlinux file
>> 
>> This looks fine.
>> 
>> Seems like cpu_features would be needed or at least pretty useful too?
>> 
>> cheers
>
> Sure, that can be added too, to the vmcoreinfo. Not sure if it's used now, but
> sure it can help to identify features in makedumpfile.
>
> Will add it, in next version.

Please do it in a separate commit to the mmu_features :)

cheers

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

On Tue, Sep 19, 2023 at 08:07:15PM +1000, Michael Ellerman wrote:
> Aditya Gupta <adityag@linux.ibm.com> writes:
> > On Thu, Sep 14, 2023 at 11:22:01PM +1000, Michael Ellerman wrote:
> >> Aditya Gupta <adityag@linux.ibm.com> writes:
> >> > Presently, while reading a vmcore, makedumpfile uses
> >> > `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> >> > RADIX MMU or not.
> >> >
> >> > Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> >> > a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> >> > assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> >> > MMU to be hash MMU.
> >> >
> >> > Add `cur_cpu_spec` symbol and offset of `mmu_features` in the
> >> > `cpu_spec` struct, to VMCOREINFO, so that the symbol address and offset
> >> > is accessible to makedumpfile, without needing the vmlinux file
> >> 
> >> This looks fine.
> >> 
> >> Seems like cpu_features would be needed or at least pretty useful too?
> >> 
> >> cheers
> >
> > Sure, that can be added too, to the vmcoreinfo. Not sure if it's used now, but
> > sure it can help to identify features in makedumpfile.
> >
> > Will add it, in next version.
> 
> Please do it in a separate commit to the mmu_features :)
> 
> cheers

Sure, have done it in a separate patch in V2.

Thanks

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Michael Ellerman]

On Mon, 11 Sep 2023 14:44:09 +0530, Aditya Gupta wrote:
> Presently, while reading a vmcore, makedumpfile uses
> `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> RADIX MMU or not.
> 
> Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> MMU to be hash MMU.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo
      https://git.kernel.org/powerpc/c/7135b921b32966d7602ede396b7286d372aee63f

cheers

Re: [PATCH] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo

[Aditya Gupta]

On Thu, Sep 21, 2023 at 07:30:00PM +1000, Michael Ellerman wrote:
> On Mon, 11 Sep 2023 14:44:09 +0530, Aditya Gupta wrote:
> > Presently, while reading a vmcore, makedumpfile uses
> > `cur_cpu_spec.mmu_features` to decide whether the crashed system had
> > RADIX MMU or not.
> > 
> > Currently, makedumpfile fails to get the `cur_cpu_spec` symbol (unless
> > a vmlinux is passed with the `-x` flag to makedumpfile), and hence
> > assigns offsets and shifts (such as pgd_offset_l4) incorrecly considering
> > MMU to be hash MMU.
> > 
> > [...]
> 
> Applied to powerpc/next.
> 
> [1/1] powerpc: add `cur_cpu_spec` symbol to vmcoreinfo
>       https://git.kernel.org/powerpc/c/7135b921b32966d7602ede396b7286d372aee63f
> 
> cheers

Thanks for the update