From: Jiri Olsa <jolsa@redhat.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org
Subject: Re: [PATCH] perf tests vmlinux-kallsyms: ignore hidden symbols
Date: Tue, 13 Jul 2021 11:57:50 +0200 [thread overview]
Message-ID: <YO1jnjHofv9oSR0M@krava> (raw)
In-Reply-To: <20210708122805.2832-1-mpetlan@redhat.com>
On Thu, Jul 08, 2021 at 02:28:05PM +0200, Michael Petlan wrote:
> Symbols containing particular prefixes are purposely hidden from kallsyms.
> The prefixes are listed in scripts/kallsyms.c, using ignored_prefixes[]
> string array. The perf test "vmlinux symtab matches kallsyms" fails in case
> perf finds some of the hidden symbols in its machine image and can't match
> them to kallsyms.
there's also other arrays like ignored_suffixes, ignored_matches ...
should we have them as well? should we take the whole is_ignored_symbol
function?
>
> Let's add a filter to check if a symbol not found isn't one of these before
> failing the test.
>
> The ignored_prefixes[] array has been copied from scripts/kallsyms.c and needs
> to be updated along with the original.
>
> Signed-off-by: Michael Petlan <mpetlan@redhat.com>
> ---
> tools/perf/tests/vmlinux-kallsyms.c | 41 +++++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/tools/perf/tests/vmlinux-kallsyms.c b/tools/perf/tests/vmlinux-kallsyms.c
> index 193b7c91b4e2..11cd276ec8fd 100644
> --- a/tools/perf/tests/vmlinux-kallsyms.c
> +++ b/tools/perf/tests/vmlinux-kallsyms.c
> @@ -14,6 +14,41 @@
>
> #define UM(x) kallsyms_map->unmap_ip(kallsyms_map, (x))
>
> +/* Symbol names that begin with the following are ignored. (a copy from scripts/kallsyms.c) */
> +static const char * const ignored_prefixes[] = {
> + "$", /* local symbols for ARM, MIPS, etc. */
> + ".LASANPC", /* s390 kasan local symbols */
> + "__crc_", /* modversions */
> + "__efistub_", /* arm64 EFI stub namespace */
> + "__kvm_nvhe_", /* arm64 non-VHE KVM namespace */
> + "__AArch64ADRPThunk_", /* arm64 lld */
> + "__ARMV5PILongThunk_", /* arm lld */
> + "__ARMV7PILongThunk_",
> + "__ThumbV7PILongThunk_",
> + "__LA25Thunk_", /* mips lld */
> + "__microLA25Thunk_",
> + NULL
> +};
> +
> +static int has_prefix(const char *prefix, const char *string)
> +{
> + while(*prefix)
> + if(*prefix++ != *string++)
> + return 0;
> +
> + return 1;
> +}
> +
> +static int should_be_hidden(const char *sym_name)
> +{
> + int i;
> + for(i = 0; ignored_prefixes[i] != NULL; i++)
> + if(has_prefix(ignored_prefixes[i], sym_name))
> + return 1;
> +
> + return 0;
please check your patch with scripts/checkpatch.pl before posting
thanks,
jirka
next prev parent reply other threads:[~2021-07-13 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:28 [PATCH] perf tests vmlinux-kallsyms: ignore hidden symbols Michael Petlan
2021-07-13 9:57 ` Jiri Olsa [this message]
2021-07-23 8:54 ` Michael Petlan
2021-07-23 9:03 ` Michael Petlan
2021-09-22 15:27 Michael Petlan
2021-09-22 16:36 ` Ian Rogers
2021-09-29 17:14 ` Arnaldo Carvalho de Melo
2021-09-29 21:10 ` Arnaldo Carvalho de Melo
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=YO1jnjHofv9oSR0M@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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).