mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bot+bpf-ci@kernel.org
To: david.laight.linux@gmail.com,pmladek@suse.com,kees@kernel.org,david.laight.linux@gmail.com,linux-kernel@vger.kernel.org,linux-kbuild@vger.kernel.org,bpf@vger.kernel.org,jim.cromie@gmail.com,ljs@kernel.org
Cc: mcgrof@kernel.org,andrey.grodzovsky@crowdstrike.com,rostedt@goodmis.org,andrii@kernel.org,wusamuel@google.com,linux-kselftest@vger.kernel.org,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,mason@kernel.org,ihor.solodrai@linux.dev
Subject: Re: [PATCH v3 next 06/13] kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output
Date: Wed, 11 Nov 2026 23:17:06 +0000 (UTC)	[thread overview]
Message-ID: <54d7eddad4b50bbaa72bc31ea3219ce9a944548da1fef3eabbc1e7337d37e5f2@mail.kernel.org> (raw)
In-Reply-To: <20261111115911.1142000-7-david.laight.linux@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2889 bytes --]

> kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output

TL;DR: Commit message only: it says 4 functions get noinline_for_stack but the
patch marks 5, and it omits the compression-ratio output format fix; maybe
split that into a separate patch.

> kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output
>
> - Improve the test stability/reproducability by taking the faster of
>   two calls to kallsyms_lookup_name().
> - Check that kallsyms_lookup_name() returns the expected address
>   unless the symbol is duplicated.
> - Report the names of the min/max symbols.
> - Output an 8 line 64 entry histogram of the times taken.
> - This shows there is a reasonably normal distribution with a small
>   number of much slower outliers that don't really affect the average.
>
> Additionally:
> - Add a very long symbol to check the handling of two byte lengths.
> - Do the test_perf_kallsyms_lookup_name() last because it can take long
>   enough that the CPU frequency changes and the times reported by the
>   other tests can change.
> - Mark the 4 test functions noinline_for_stack since they all have a
>   quite large on-stack structure.
>
> Example output (after all these patches)
> kallsyms_on_each_symbol() traverse all: 7742950 ns
> kallsyms_on_each_match_symbol() traverse all: 951 ns
> kallsyms_lookup_name() looked up 123312 symbols, average 200 ns
>         fastest 60 ns (_rs.0)
>         slowest 662 ns (The_time_has_come_the_Walrus_said_To_talk_of_many_things_Of_sho)
>         Distribution, 20ns per column, 2916 counts per *:
>         |         **
>         |        ****
>         |        ****
>         |        ****
>         |       ******
>         |       *******
>         |      *********
>         |   ******************  **    * * *
>
> Signed-off-by: David Laight <david.laight.linux@gmail.com>
>

The changelog says 4 test functions are marked noinline_for_stack "since they
all have a quite large on-stack structure", but the patch marks five:
test_kallsyms_compression_ratio(), test_perf_kallsyms_lookup_name(),
test_perf_kallsyms_on_each_symbol(), test_perf_kallsyms_on_each_match_symbol()
and test_kallsyms_basic_function().

test_kallsyms_compression_ratio() has only seven u32 locals and no large
on-stack structure, so the stated reason does not cover it.

The same function also changes its output format from "%2d.%-2d" to
"%2d.%02d", which fixes how the fractional part is printed (12.05 used to show
as "12.5 "). The changelog does not mention this.

Could the changelog give the right count and mention the format fix, or should
the compression-ratio changes go in a separate patch?


---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

CI run summary: https://github.com/kernel-patches/bpf/actions/runs/43116767394

  reply	other threads:[~2026-11-11 23:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 11:58 [PATCH v3 next 00/13] kallsyms: optimise symbol search by name David Laight
2026-11-11 11:58 ` [PATCH v3 next 01/13] scripts/kallsyms: Avoid overrunning on-stack buffer David Laight
2026-11-11 11:59 ` [PATCH v3 next 02/13] scripts/kallsyms: Improve error reporting David Laight
2026-11-11 23:33   ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 03/13] scripts/elf-parse: add elf_map_big_endian() helper David Laight
2026-11-11 11:59 ` [PATCH v3 next 04/13] scripts/kallsyms: make use of binary data output optional David Laight
2026-11-11 23:34   ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 05/13] kallsyms: Fix selftest startup delay David Laight
2026-11-11 11:59 ` [PATCH v3 next 06/13] kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output David Laight
2026-11-11 23:17   ` bot+bpf-ci [this message]
2026-11-11 11:59 ` [PATCH v3 next 07/13] kallsyms: Match compressed tokens on the fly during binary search David Laight
2026-11-11 11:59 ` [PATCH v3 next 08/13] kallsyms: Optimise symbol name search David Laight
2026-11-11 11:59 ` [PATCH v3 next 09/13] kallsyms: Add a kernel parameter to change the kallsyms_markers[] density David Laight
2026-11-11 23:33   ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 10/13] scripts/kallsyms: Keep full expansion of tokens David Laight
2026-11-11 11:59 ` [PATCH v3 next 11/13] scripts/kallsyms: Optimise compress_symbols() David Laight
2026-11-11 11:59 ` [PATCH v3 next 12/13] scripts/kallsyms: Reuse tokens that have no references David Laight
2026-11-11 23:34   ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 13/13] scripts/kallsyms: Reuse little-used compression tokens David Laight

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=54d7eddad4b50bbaa72bc31ea3219ce9a944548da1fef3eabbc1e7337d37e5f2@mail.kernel.org \
    --to=bot+bpf-ci@kernel.org \
    --cc=andrey.grodzovsky@crowdstrike.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=david.laight.linux@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jim.cromie@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=mason@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=wusamuel@google.com \
    --cc=yonghong.song@linux.dev \
    /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

all inboxes | Powered by JetHome®