[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87jzwngx65.fsf@mail.lhotse>
Date: Thu, 01 Jun 2023 22:54:42 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Maninder Singh <maninder1.s@...sung.com>, bcain@...cinc.com,
npiggin@...il.com, christophe.leroy@...roup.eu,
keescook@...omium.org, nathanl@...ux.ibm.com, ustavoars@...nel.org,
alex.gaynor@...il.com, gary@...yguo.net, ojeda@...nel.org,
pmladek@...e.com, wedsonaf@...gle.com,
linux-hexagon@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, Onkarnath <onkarnath.1@...sung.com>
Subject: Re: [PATCH 2/2] powerpc/xmon: use KSYM_NAME_LEN in array size
Miguel Ojeda <miguel.ojeda.sandonis@...il.com> writes:
> On Thu, Jun 1, 2023 at 4:02 AM Michael Ellerman <mpe@...erman.id.au> wrote:
>>
>> > Side-note: in `get_function_bounds()`, I see `kallsyms_lookup()` being
>> > used, but the name seems discarded? Can
>> > `kallsyms_lookup_size_offset()` be used instead, thus avoiding the
>> > usage of the buffer there to begin with?
>>
>> A few lines below it uses the modname, and AFAICS there's no (easy) way
>> to lookup the modname without also looking up the name.
>
> Hmm... I think you are looking at the `xmon_print_symbol()` one? I was
> referring to the `get_function_bounds()` one, where the `modname`
> parameter is `NULL` (and the `name` contents are not used, only
> whether it was found or not).
Yes you're right, apparently I can't read :}
cheers
Powered by blists - more mailing lists