linux-kernel - [PATCH v2 perf-tools-next 0/4] 'perf test' fixes/improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241105142616.761042-1-acme@kernel.org>
Date: Tue,  5 Nov 2024 11:26:12 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jiri Olsa <jolsa@...nel.org>,
	Ian Rogers <irogers@...gle.com>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Kan Liang <kan.liang@...ux.intel.com>,
	Clark Williams <williams@...hat.com>,
	linux-kernel@...r.kernel.org,
	linux-perf-users@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Athira Rajeev <atrajeev@...ux.vnet.ibm.com>,
	Howard Chu <howardchu95@...il.com>,
	James Clark <james.clark@...aro.org>,
	Leo Yan <leo.yan@...ux.dev>,
	Thomas Richter <tmricht@...ux.ibm.com>,
	Veronika Molnarova <vmolnaro@...hat.com>
Subject: [PATCH v2 perf-tools-next 0/4] 'perf test' fixes/improvements

Hi,

        While evaluating what is needed for having shell tests that test
python functionality conditionally, i.e. so that we don't try to test
the python binding if NO_LIBPYTHON=1 is used, I stumbled into these
problems.

        The first patch its more for documenting that strange system()
behaviour and to check if this was something that would have
implications in other 'perf test' cases besides this python one, maybe
somebody will spot the problem, but at least it seems more compact now
using 'python -c inline-python-source'.

v2:

- Don't suppress the python binding test, instead skip it and tell the
  reason: the binding isn't available.

- Treat NO_LIBTRACEVENT=1 like NO_LIBPYTHON=1, not suppressing tests, just
  skipping them, warn the user on explicit suppression of the library.

- Also reduce a patch description verbosity, as noted by Ian.

- Arnaldo

Arnaldo Carvalho de Melo (4):
  perf test python: Robustify the 'perf test python' test case
  perf test: Skip the python binding builtin test case with NO_LIBPYTHON=1
  perf test: Don't suppress the libtraceevent tests, skip them
  perf build: Emit a warning when libtraceevent is explicitely disabled

 tools/perf/Makefile.config                  |  4 +++-
 tools/perf/tests/Build                      | 12 +++++-----
 tools/perf/tests/builtin-test.c             |  6 -----
 tools/perf/tests/evsel-tp-sched.c           | 16 +++++++++++--
 tools/perf/tests/mmap-basic.c               | 26 +++++++++++++++++++--
 tools/perf/tests/openat-syscall-all-cpus.c  | 11 ++++++++-
 tools/perf/tests/openat-syscall-tp-fields.c | 11 ++++++++-
 tools/perf/tests/openat-syscall.c           | 11 ++++++++-
 tools/perf/tests/python-use.c               | 24 ++++++++++++++++---
 tools/perf/tests/switch-tracking.c          | 23 +++++++++++++++++-
 10 files changed, 120 insertions(+), 24 deletions(-)

-- 
2.47.0