[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfkBQNBEPrAJ9jKw@smile.fi.intel.com>
Date: Tue, 1 Feb 2022 11:45:36 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Maninder Singh <maninder1.s@...sung.com>
Cc: pmladek@...e.com, rostedt@...dmis.org, senozhatsky@...omium.org,
linux@...musvillemoes.dk, akpm@...ux-foundation.org,
wangkefeng.wang@...wei.com, mbenes@...e.cz, swboyd@...omium.org,
ojeda@...nel.org, linux-kernel@...r.kernel.org, will@...nel.org,
catalin.marinas@....com, Vaneet Narang <v.narang@...sung.com>
Subject: Re: [PATCH 1/1] kallsyms: print module name in %ps/S case when
KALLSYMS is disabled
On Tue, Feb 01, 2022 at 09:30:44AM +0530, Maninder Singh wrote:
> original:
> With KALLSYMS
> %pS %ps
> [16.4200] hello_init+0x0/0x24 [crash] hello_init [crash]
>
> Without KALLSYMS:
> [16.2200] 0xbe200040 0xbe200040
>
> With Patch (Without KALLSYMS:) load address + current offset [Module Name]
>
> [13.5993] 0xbe200000+0x40 [crash] 0xbe200000+0x40 [crash]
>
> It will help in better debugging and checking when KALLSYMS is disabled,
> user will get information about module name and load address of module.
>
> verified for arm64:
> / # insmod /crash.ko
>
> [ 19.263556] 0xffff800000ec0000+0x38 [crash]
>
> ..
>
> [ 19.276023] Call trace:
> [ 19.276277] 0xffff800000ec0000+0x28 [crash]
> [ 19.276567] 0xffff800000ec0000+0x58 [crash]
> [ 19.276727] 0xffff800000ec0000+0x74 [crash]
> [ 19.276866] 0xffff8000080127d0
> [ 19.276978] 0xffff80000812d95c
> [ 19.277085] 0xffff80000812f554
> Signed-off-by: Vaneet Narang <v.narang@...sung.com>
> Signed-off-by: Maninder Singh <maninder1.s@...sung.com>
Who is (are) the author(s)?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists