From: Eric Biggers <ebiggers@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Fangrui Song <maskray@sourceware.org>,
Pablo Galindo <pablogsal@gmail.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] perf genelf: Switch from SHA-1 to BLAKE2s for build ID generation
Date: Thu, 4 Dec 2025 20:39:24 -0800 [thread overview]
Message-ID: <20251205043924.GA6421@sol> (raw)
In-Reply-To: <20251205043121.62356-1-ebiggers@kernel.org>
On Thu, Dec 04, 2025 at 08:31:21PM -0800, Eric Biggers wrote:
> ---
> tools/perf/tests/util.c | 78 ++++++++++++--------
> tools/perf/util/Build | 2 +-
> tools/perf/util/blake2s.c | 151 ++++++++++++++++++++++++++++++++++++++
> tools/perf/util/blake2s.h | 73 ++++++++++++++++++
> tools/perf/util/genelf.c | 58 +++++++--------
> tools/perf/util/sha1.c | 97 ------------------------
> tools/perf/util/sha1.h | 6 --
> 7 files changed, 302 insertions(+), 163 deletions(-)
> create mode 100644 tools/perf/util/blake2s.c
> create mode 100644 tools/perf/util/blake2s.h
> delete mode 100644 tools/perf/util/sha1.c
> delete mode 100644 tools/perf/util/sha1.h
Forgot to mention: this applies to next-20251204, or alternatively to
the latest perf-tools-next (d509d14fff783969904954eaf5d94f092c6fce19)
- Eric
next prev parent reply other threads:[~2025-12-05 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 4:31 [PATCH] perf genelf: Switch from SHA-1 to BLAKE2s for build ID generation Eric Biggers
2025-12-05 4:39 ` Eric Biggers [this message]
2025-12-05 18:53 ` Ian Rogers
2025-12-09 1:19 ` Eric Biggers
2025-12-05 21:23 ` Namhyung Kim
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=20251205043924.GA6421@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maskray@sourceware.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pablogsal@gmail.com \
--cc=peterz@infradead.org \
/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).