From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: David Laight <David.Laight@ACULAB.COM>,
Masami Hiramatsu <mhiramat@kernel.org>,
Paul Clarke <pc@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kallsyms: optimize kallsyms_lookup_name() for a few cases
Date: Thu, 27 Apr 2017 01:38:10 +0530 [thread overview]
Message-ID: <20170426200810.2126-1-naveen.n.rao@linux.vnet.ibm.com> (raw)
In-Reply-To: <87lgqn1m8k.fsf@concordia.ellerman.id.au>
Michael Ellerman wrote:
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:
>> diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
>> index 6a3b249a2ae1..d134b060564f 100644
>> --- a/kernel/kallsyms.c
>> +++ b/kernel/kallsyms.c
>> @@ -205,6 +205,12 @@ unsigned long kallsyms_lookup_name(const char *name)
>> unsigned long i;
>> unsigned int off;
>>
>> + if (!name || *name == '\0')
>> + return false;
>> +
>> + if (strnchr(name, MODULE_NAME_LEN, ':'))
>> + return module_kallsyms_lookup_name(name);
>> +
>> for (i = 0, off = 0; i < kallsyms_num_syms; i++) {
>> off = kallsyms_expand_symbol(off, namebuf, ARRAY_SIZE(namebuf));
> ...
> }
> return module_kallsyms_lookup_name(name);
>
> Is the rest of the context.
>
> Which looks a bit odd, we already did module lookup previously?
>
> But it's correct, because you can lookup a symbol in a module without a
> module prefix, it just looks in every module.
Yes.
>
> You could invert the logic, ie. check that there isn't a ":" in the name
> and only in that case do the for loop, always falling back to module
> lookup.
>
> Or just add a comment explaining why we call module lookup in two places.
Good point. Here's a v2 - I'm using a goto so as to not indent the code too much.
Thanks for the review!
- Naveen
--
[PATCH v2] kallsyms: optimize kallsyms_lookup_name() for a few cases
1. Fail early for invalid/zero length symbols.
2. Detect names of the form <mod:name> and skip checking for kernel
symbols in that case.
Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
---
kernel/kallsyms.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
index 6a3b249a2ae1..f7558dc5c6ac 100644
--- a/kernel/kallsyms.c
+++ b/kernel/kallsyms.c
@@ -205,12 +205,20 @@ unsigned long kallsyms_lookup_name(const char *name)
unsigned long i;
unsigned int off;
+ if (!name || *name == '\0')
+ return 0;
+
+ /* For symbols of the form <mod>:<sym>, only check the modules */
+ if (strnchr(name, MODULE_NAME_LEN, ':'))
+ goto mod;
+
for (i = 0, off = 0; i < kallsyms_num_syms; i++) {
off = kallsyms_expand_symbol(off, namebuf, ARRAY_SIZE(namebuf));
if (strcmp(namebuf, name) == 0)
return kallsyms_sym_address(i);
}
+mod:
return module_kallsyms_lookup_name(name);
}
EXPORT_SYMBOL_GPL(kallsyms_lookup_name);
--
2.12.2
next prev parent reply other threads:[~2017-04-26 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:18 [PATCH] kallsyms: optimize kallsyms_lookup_name() for a few cases Naveen N. Rao
2017-04-25 16:36 ` David Laight
2017-04-25 17:17 ` Naveen N. Rao
2017-04-26 10:44 ` Michael Ellerman
2017-04-26 20:08 ` Naveen N. Rao [this message]
2017-04-27 2:21 ` Masami Hiramatsu
2017-06-27 9:28 ` Naveen N. Rao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170426200810.2126-1-naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=pc@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).