From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] perf check: Add 'system' subcommand
Date: Thu, 18 Sep 2025 17:12:03 -0300 [thread overview]
Message-ID: <aMxnk8dQrXC-q5dD@x1> (raw)
In-Reply-To: <CAP-5=fVAsDN50X07zpnxikS_tA2cw92YJwHR2f9RVs0fc8j-Ng@mail.gmail.com>
On Thu, Sep 18, 2025 at 08:48:10AM -0700, Ian Rogers wrote:
> On Wed, Sep 17, 2025 at 11:39 PM Namhyung Kim <namhyung@kernel.org> wrote:
> > +/**
> > + * Usage: 'perf check system <settings>'
> > + *
> > + * Show system settings that affect perf behavior.
> > + */
> > +static int subcommand_system(int argc, const char **argv)
> > +{
> > +#define PERF_SYSCTL(name) { #name, system_help_##name }
> > + struct {
> > + const char *name;
> > + const char *(*help)(int value);
> > + } sysctls[] = {
> > + PERF_SYSCTL(perf_event_paranoid),
> > + PERF_SYSCTL(perf_event_max_stack),
> > + PERF_SYSCTL(perf_event_mlock_kb),
> > + PERF_SYSCTL(nmi_watchdog),
> > + PERF_SYSCTL(kptr_restrict),
> > + };
> > +#undef PERF_SYSCTL
> > +
> > + argc = parse_options(argc, argv, check_system_options,
> > + check_system_usage, 0);
> > +
> > + for (size_t i = 0; i < ARRAY_SIZE(sysctls); i++) {
> > + int value;
> > +
> > + if (argc) {
> > + bool found = false;
> > +
> > + /* only show entries match to command line arguments */
> > + for (int k = 0; k < argc; k++) {
> > + if (strstr(sysctls[i].name, argv[k])) {
> > + found = true;
> > + break;
> > + }
> > + }
> > + if (!found)
> > + continue;
> > + }
> > +
> > + value = read_sysctl_kernel_int(sysctls[i].name);
> > + printf("%-20s = %d", sysctls[i].name, value);
> > + if (!quiet)
> > + printf("\t# %s", sysctls[i].help(value));
> > + printf("\n");
> > + }
> > +
> > + return 0;
>
> This looks useful! Rather than returning 0 should this return
> something indicating whether perf does or doesn't have the permission?
> In that case, what about root? We have this pattern in our shell
> tests:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/tests/shell/lib/stat_output.sh?h=perf-tools-next
> ```
> function ParanoidAndNotRoot()
> {
> [ "$(id -u)" != 0 ] && [ "$(cat /proc/sys/kernel/perf_event_paranoid)" -gt $1 ]
> }
> ```
> I wonder things like this can use these values instead.
Yeah, I thought about that as well, to use these checks in the perf test
shell entries.
- Arnaldo
next prev parent reply other threads:[~2025-09-18 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 6:39 Namhyung Kim
2025-09-18 6:39 ` [RFC/PATCH 2/2] perf check: Add 'pmu' subcommand Namhyung Kim
2025-09-18 15:33 ` Ian Rogers
2025-09-19 20:27 ` Namhyung Kim
2025-09-20 14:04 ` Ian Rogers
2025-09-18 15:48 ` [RFC/PATCH 1/2] perf check: Add 'system' subcommand Ian Rogers
2025-09-18 20:12 ` Arnaldo Carvalho de Melo [this message]
2025-09-19 20:21 ` 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=aMxnk8dQrXC-q5dD@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@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=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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
all inboxes | Powered by JetHome®