All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 15/19] perf tests: Introduce a 'needs_mlock' suite flag
Date: Fri, 16 Oct 2026 00:27:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-173527@kernel.org> (raw)
In-Reply-To: <20261016001843.71978-16-acme@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] perf test: missing stdio.h inclusion for musl libc compatibility
--

commit 0cd49c7e0c286b9d1bb7377465b008f3b907a53c
Author: Arnaldo Carvalho de Melo <acme@redhat.com>

perf tests: Introduce a 'needs_mlock' suite flag

This commit adds a 'needs_mlock' flag to 'struct test_suite' to distinguish
test suites that map ring buffers from those that do not, allowing them to
take turns using the kernel.perf_event_mlock_kb budget. It also introduces
a 'requisites' subcommand to list test requirements.

> diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
> index 98134b1c74cf8..acffa0d0d33d6 100644
> --- a/tools/perf/tests/builtin-test.c
> +++ b/tools/perf/tests/builtin-test.c
[ ... ]
> @@ -283,6 +285,30 @@ static const char *test_description(const struct test_suite *t, int test_case)
>  	return t->desc;
>  }
>  
> +static void requisites__fprintf(FILE *fp, const struct test_suite *t, int test_case)
> +{
> +	bool needs_mlock = t->needs_mlock, exclusive;

[Severity: Low]
Since this newly added function explicitly uses the FILE type and fprintf(),
should <stdio.h> be explicitly included at the top of the file to ensure
compatibility with musl libc?

> +
> +	if (test_case < 0)
> +		test_case = test_suite__num_test_cases(t) == 1 ? 0 : -1;
[ ... ]
> diff --git a/tools/perf/tests/tests-scripts.c b/tools/perf/tests/tests-scripts.c
> index 0370bc7013737..0bc84372eae09 100644
> --- a/tools/perf/tests/tests-scripts.c
> +++ b/tools/perf/tests/tests-scripts.c
[ ... ]
> @@ -187,7 +260,8 @@ static void append_script(int dir_fd, const char *name, char *desc,
>  	struct test_suite *test_suite, **result_tmp;
>  	struct test_case *tests;
>  	ssize_t len;
> -	char *exclusive;
> +	/* Shell tests run perf, that maps ring buffers, so they need the budget. */
> +	bool exclusive = false, needs_mlock = true;
>  
>  	snprintf(link, sizeof(link), "/proc/%d/fd/%d", getpid(), dir_fd);

[Severity: Low]
This isn't a bug in the patch logic, but the code relies on snprintf() here.
Would it make sense to explicitly include <stdio.h> in this file as well to
prevent potential build failures on systems using musl libc?

>  	len = readlink(link, filename, sizeof(filename) - 1);
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261016001843.71978-1-acme@kernel.org?part=15

  reply	other threads:[~2026-10-16  0:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  0:18 [PATCH v3 0/19] perf test attr: Report the failures again and cope with more than one core PMU Arnaldo Carvalho de Melo
2026-10-16  0:18 ` [PATCH v3 01/19] perf test attr: Fix record dwarf sample_type expectation Arnaldo Carvalho de Melo
2026-10-16  0:22   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 02/19] perf test attr: Allow tests to require a core PMU Arnaldo Carvalho de Melo
2026-10-16  0:26   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 03/19] perf test attr: Fix legacy event encodings in group tests Arnaldo Carvalho de Melo
2026-10-16  0:32   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 04/19] perf test attr: Fix default stat metrics expectations Arnaldo Carvalho de Melo
2026-10-16  0:21   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 05/19] perf test attr: Relax group checking for ungrouped expectations Arnaldo Carvalho de Melo
2026-10-16  0:23   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 06/19] perf evsel: Mark the event as supported when retrying an open Arnaldo Carvalho de Melo
2026-10-16  0:25   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 07/19] perf test attr: Ignore the core PMU type perf puts in 'config' Arnaldo Carvalho de Melo
2026-10-16  0:24   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 08/19] perf evsel: Don't dump probe events to PERF_TEST_ATTR Arnaldo Carvalho de Melo
2026-10-16  0:31   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 09/19] perf test attr: Introduce mask_bits(), generalizing hide_core_pmu_type() Arnaldo Carvalho de Melo
2026-10-16  0:23   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 10/19] perf test attr: Accept either sample id bit perf asks for Arnaldo Carvalho de Melo
2026-10-16  0:28   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 11/19] perf test attr: Ignore the dummy tracking event and the terms it carries Arnaldo Carvalho de Melo
2026-10-16  0:25   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 12/19] perf test attr: Leave out the events of the other core PMUs Arnaldo Carvalho de Melo
2026-10-16  0:24   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 13/19] perf test attr: Ignore the group read_format bit the PMU count can remove Arnaldo Carvalho de Melo
2026-10-16  0:24   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 14/19] perf test attr: State, spelled out in a line, why a test is skipped Arnaldo Carvalho de Melo
2026-10-16  0:24   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 15/19] perf tests: Introduce a 'needs_mlock' suite flag Arnaldo Carvalho de Melo
2026-10-16  0:27   ` sashiko-bot [this message]
2026-10-16  0:18 ` [PATCH v3 16/19] perf tests: Mark the C tests mapping perf ring buffers Arnaldo Carvalho de Melo
2026-10-16  0:24   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 17/19] perf tests: Mark the shell tests not " Arnaldo Carvalho de Melo
2026-10-16  0:26   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 18/19] perf mutex: Add a robust, process-shared mutex initializer Arnaldo Carvalho de Melo
2026-10-16  0:28   ` sashiko-bot
2026-10-16  0:18 ` [PATCH v3 19/19] perf test: Take turns using the perf mlock budget in the mmaping tests Arnaldo Carvalho de Melo
2026-10-16  0:28   ` sashiko-bot

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-173527@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=acme@kernel.org \
    --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 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.