On 18/03/24 14:18, HAGIO KAZUHITO(萩尾 一仁) wrote:
On 2024/03/18 17:26, Aditya Gupta wrote:
Hi,
The commit removing 'vmap_area_list' is now merged in Linux mainline tree.
commit: 55c49fee57af99f3c663e69dedc5b85e691bbe50
mm/vmalloc: remove vmap_area_list
Applied with this commit
Hi,
The commit removing 'vmap_area_list' is now merged in Linux mainline tree.
commit: 55c49fee57af99f3c663e69dedc5b85e691bbe50
mm/vmalloc: remove vmap_area_list
Any comments on this patch ?
Thanks,
Aditya Gupta
On 24/02/24 00:33, Aditya Gupta wrote:
Below error was noticed when
Hi Kazu,
On Wed, Feb 28, 2024 at 12:25:04AM +, HAGIO KAZUHITO(萩尾 一仁) wrote:
> On 2024/02/23 17:39, Aditya Gupta wrote:
> > Currently makedumpfile depends on reading the 'cur_cpu_spec' kernel
> > symbol to get the current MMU type on PowerPC64.
> >
> > The disa
Hi Kazu,
On Wed, Feb 28, 2024 at 04:51:28AM +, HAGIO KAZUHITO(萩尾 一仁) wrote:
> Hi Aditya,
>
> thanks for the patch.
>
> On 2024/02/24 4:03, Aditya Gupta wrote:
> > Below error was noticed when running makedumpfile on linux-next kernel
> > crash (l
' symbol is there in vmcoreinfo:
1. Set vmalloc_start based on 'VMALLOC_START'
2. Don't error if vmap_area_list/vmlist are not defined
Reported-by: Sachin Sant
Signed-off-by: Aditya Gupta
---
arch/ppc64.c | 19 +--
makedumpfile.c | 3 ++-
makedumpfile.h | 6 +++---
3 files
e will
simply fall back to using 'cur_cpu_spec'.
The earlier defines for 'RADIX_MMU' have been renamed to 'MMU_TYPE_RADIX'
which avoids conflict with the vmcoreinfo string 'RADIX_MMU', as well as
being more clear about the value 0x40 with a comment about MMU_FTR_TYPE_RADIX
Signed-off-by:
On Fri, Feb 23, 2024 at 03:54:12PM +0800, Baoquan He wrote:
> Add maintainer Kazu to CC.
Thanks, I missed him, will resend this patch with him in CC.
Thanks,
Aditya Gupta
>
> On 02/23/24 at 11:23am, Aditya Gupta wrote:
> > Currently makedumpfile depends on reading the 'cur_c
e will
simply fall back to using 'cur_cpu_spec'.
The earlier defines for 'RADIX_MMU' have been renamed to 'MMU_TYPE_RADIX'
which avoids conflict with the vmcoreinfo string 'RADIX_MMU', as well as
being more clear about the value 0x40 with a comment about MMU_FTR_TYPE_RADIX
Signed-off-by:
ported-by: Srikar Dronamraju
Signed-off-by: Aditya Gupta
---
kexec/arch/ppc64/kexec-elf-ppc64.c| 22 +++---
kexec/arch/ppc64/kexec-ppc64.c| 6 +++---
kexec/arch/ppc64/kexec-zImage-ppc64.c | 2 +-
3 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/kexec/arch
On Wed, Sep 27, 2023 at 06:32:44AM +, HAGIO KAZUHITO(萩尾 一仁) wrote:
> On 2023/09/14 18:22, Aditya Gupta wrote:
> > Currently 'makedumpfile' fails to collect vmcore on upstream kernel,
> > with the errors:
> >
> > readpage_elf: Attempt to read non-existent
Or, the vmlinux can be provided to makedumpfile, so that it finds the
'cur_cpu_spec.mmu_features' symbol, run makedumpfile with '-x' flag similar to
this:
makedumpfile -l -d 31 -x VMLINUX /proc/vmcore /var/crash/vmcore.kdump
Thanks,
Aditya Gupta
___
kexec mailing
-by: Aditya Gupta
---
arch/ppc64.c | 111 ++---
makedumpfile.h | 6 +++
2 files changed, 84 insertions(+), 33 deletions(-)
diff --git a/arch/ppc64.c b/arch/ppc64.c
index 5e70acb51aba..9456b8b570c5 100644
--- a/arch/ppc64.c
+++ b/arch/ppc64.c
@@ -196,6
12 matches
Mail list logo