Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 10/10] perf build: Default JEVENTS_ARCH to all
Date: Mon, 16 Nov 2026 07:16:39 +0000	[thread overview]
Message-ID: <sashiko-outbox-216400@kernel.org> (raw)
In-Reply-To: <20261116070038.2968725-11-irogers@google.com>

> Because block-indexed string compression packs PMU event and metric
> strings into independently compressed ~8 KiB blocks decompressed on
> demand via (block_id << 16) | sub_offset, bundling non-host
> architectures' compressed blocks in .rodata incurs zero runtime
> decompression CPU or heap memory unless those architectures are queried.
> With zstd enabled, bundling PMU event and metric tables for all
> architectures (JEVENTS_ARCH=all) is 5.77 MiB smaller overall than an
> uncompressed x86-only build (JEVENTS_ARCH=x86 JEVENTS_COMPRESS=none),
> cutting the stripped perf binary nearly in half (-45.4%) while enabling
> cross-architecture perf.data analysis out of the box:
> 
>   Component                   x86 + none      all + zstd      Delta
>   -----------------------------------------------------------------
>   pmu-events-string.o (dec)   6,901,987 B      794,032 B    -88.5%
>   pmu-events.o (dec)            257,987 B      314,940 B    +22.1%
> [ ... ]
> to NO_JEVENTS=1 if that architecture lacks mapfile.csv), and update
> tools/perf/tests/make to exercise JEVENTS_ARCH=$(SRCARCH) alongside the
> new default.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261116070038.2968725-1-irogers@google.com?part=10


      reply	other threads:[~2026-11-16  7:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  7:00 [PATCH v2 00/10] perf jevents: Block-indexed string compression and default JEVENTS_ARCH=all Ian Rogers
2026-11-16  7:00 ` [PATCH v2 01/10] perf jevents: Store raw bytes in BigCString instead of C-escaped strings Ian Rogers
2026-11-16  7:09   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 02/10] perf jevents: Sort BigCString entries alphabetically Ian Rogers
2026-11-16  7:05   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 03/10] perf jevents: Store PMU names as string literals in struct pmu_table_entry Ian Rogers
2026-11-16  7:06   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 04/10] perf jevents: Encapsulate big_c_string lookups behind pmu_events__get_string() Ian Rogers
2026-11-16  7:06   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 05/10] perf jevents: Add block-indexed string packing and --compress=zlib Ian Rogers
2026-11-16  7:07   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 06/10] perf jevents: Add --compress=lzma block compression backend Ian Rogers
2026-11-16  7:04   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 07/10] perf jevents: Add --compress=zstd " Ian Rogers
2026-11-16  7:08   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 08/10] perf build: Enable jevents string compression when available Ian Rogers
2026-11-16  7:10   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 09/10] perf tests pmu-events: Test metricgroup descriptions and concurrent lookups Ian Rogers
2026-11-16  7:13   ` sashiko-bot
2026-11-16  7:00 ` [PATCH v2 10/10] perf build: Default JEVENTS_ARCH to all Ian Rogers
2026-11-16  7:16   ` sashiko-bot [this message]

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=sashiko-outbox-216400@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.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