On 25/08/26 6:35 am, Dave Young wrote:
[snip]
>>
>> One question, arm64 adjusts kimage_voffset post-relocation and riscv64
>> adjusts kernel_link_addr, once the KASLR offset is derived. Does
>> LoongArch need a similar fixup for its virtual-to-physical translation,
>> or is the global kt->relocate sufficient?
>
> I suppose we do not need them though I'm not very clear about the arch code.
> loongarch kernel code does not export those related vmcore infos and test passed.
From the loongarch support code of vaddr -> paddr translation loongarch64_pgd_vtop(),
it does not depend on any further offset, I think something similar to arm64/riscv is not
needed. Anyway it is a good question!
Thanks for the confirmation and explanation, Dave! Glad to know
LoongArch doesn't need that extra handling here.
>
> Anyway let's see if wangming from loongson company can provide more info.
>
>>
>>>
>>> case PRE_GDB:
>>> --
>>> Crash-utility mailing list -- devel(a)lists.crash-utility.osci.io
>>> To unsubscribe send an email to devel-leave(a)lists.crash-utility.osci.io
>>> https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
>>> Contribution Guidelines:
https://github.com/crash-utility/crash/wiki
>>
> --
> Crash-utility mailing list -- devel(a)lists.crash-utility.osci.io
> To unsubscribe send an email to devel-leave(a)lists.crash-utility.osci.io
> https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
> Contribution Guidelines:
https://github.com/crash-utility/crash/wiki
--
Regards,
Mukesh Pilaniya