From: Eric Biggers <ebiggers@kernel.org>
To: linux-perf-users@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
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>,
Liang Kan <kan.liang@linux.intel.com>,
Yuzhuo Jing <yuzhuo@google.com>
Subject: [PATCH v3 0/4] perf: Remove libcrypto dependency
Date: Wed, 25 Jun 2025 13:23:07 -0700 [thread overview]
Message-ID: <20250625202311.23244-1-ebiggers@kernel.org> (raw)
This is a reworked version of
https://lore.kernel.org/all/20250521225307.743726-1-yuzhuo@google.com/.
I've changed it to add a new minimal SHA-1 implementation, instead of
trying to pull in the kernel's SHA-1 implementation which is not really
designed to be extracted into userspace programs. I also added a test.
Changed in v3:
- Rebased onto perf-tools-next
- Removed unnecessary parentheses in array indices in sha1.c
- Updated my email address. I've started consistently using my
kernel.org email address.
Eric Biggers (2):
perf build: enable -fno-strict-aliasing
perf util: add a basic SHA-1 implementation
Yuzhuo Jing (2):
perf genelf: Remove libcrypto dependency and use built-in sha1()
tools: Remove libcrypto dependency
tools/build/Makefile.feature | 2 -
tools/build/feature/Makefile | 4 -
tools/build/feature/test-all.c | 5 --
tools/build/feature/test-libcrypto.c | 25 -------
tools/perf/Documentation/perf-check.txt | 1 -
tools/perf/Makefile.config | 17 +----
tools/perf/Makefile.perf | 3 -
tools/perf/builtin-check.c | 1 -
tools/perf/tests/make | 4 +-
tools/perf/tests/util.c | 45 +++++++++++-
tools/perf/util/Build | 1 +
tools/perf/util/genelf.c | 85 +---------------------
tools/perf/util/sha1.c | 97 +++++++++++++++++++++++++
tools/perf/util/sha1.h | 6 ++
14 files changed, 156 insertions(+), 140 deletions(-)
delete mode 100644 tools/build/feature/test-libcrypto.c
create mode 100644 tools/perf/util/sha1.c
create mode 100644 tools/perf/util/sha1.h
base-commit: 9c9f4a27eb1096beb650f312a1ce996a9960b56c
--
2.50.0
next reply other threads:[~2025-06-25 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 20:23 Eric Biggers [this message]
2025-06-25 20:23 ` [PATCH v3 1/4] perf build: enable -fno-strict-aliasing Eric Biggers
2025-06-27 16:38 ` Namhyung Kim
2025-06-25 20:23 ` [PATCH v3 2/4] perf util: add a basic SHA-1 implementation Eric Biggers
2025-06-25 20:23 ` [PATCH v3 3/4] perf genelf: Remove libcrypto dependency and use built-in sha1() Eric Biggers
2025-06-25 20:23 ` [PATCH v3 4/4] tools: Remove libcrypto dependency Eric Biggers
2025-06-25 21:33 ` [PATCH v3 0/4] perf: " Ian Rogers
2025-06-27 18:53 ` 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=20250625202311.23244-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yuzhuo@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.