[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mxcws2wtnrar2kiswwlkmdl2mqkbv3zvek3lx7qe7bpejea3aa@5ymqftm6zli7>
Date: Sun, 27 Aug 2023 12:47:30 +0530
From: Aditya Gupta <adityag@...ux.ibm.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: acme@...nel.org, jolsa@...nel.org, irogers@...gle.com,
linux-perf-users@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
maddy@...ux.ibm.com, atrajeev@...ux.vnet.ibm.com,
kjain@...ux.ibm.com, disgoel@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Introduce perf build subcommand
Hello,
On Fri, Aug 25, 2023 at 10:07:28AM -0700, Namhyung Kim wrote:
> Hello,
>
> On Thu, Aug 24, 2023 at 11:11 PM Aditya Gupta <adityag@...ux.ibm.com> wrote:
> >
> > <...>
> >
> > Proposed solution
> > =================
> >
> > As suggested by contributors in:
> > https://lore.kernel.org/linux-perf-users/ZMPWk5K63tadmDlU@kernel.org/
> >
> > Introduce a subcommand "perf build --has", with which
> > scripts can test for presence of a feature, such as:
> >
> > perf build --has HAVE_FEATURE
> >
> > <...>
>
> I'm not sure 'perf build' is a good name, it sounds like it needs to build
> something. Maybe 'perf check --feature XXX' ?
>
> Then we can extend the perf check command to *check* system
> settings like perf_event_paranoid, kptr_restrict, nmi_watchdog
> and so on, and possibly provides some advice or even change
> the values easily.
>
> What do you think?
>
Sure, the said confusion due to 'build' makes sense. I will discuss with athira
also and post a V2 with suggested change.
And, since a new subcommand is being introduced, where do I add a
documentation, such that it can be visible in a manpage etc, similar to
perf-version(1) ?
Thanks,
Aditya Gupta
Powered by blists - more mailing lists