linux-kernel - Re: [RFC 0/4] perf sched: Introduce schedstat tool

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAM9d7chvDczhMoOJFLz=MW0ojGm=Ex90CgHhfOsZuLre3vSE3g@mail.gmail.com>
Date: Thu, 9 May 2024 15:33:29 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Ravi Bangoria <ravi.bangoria@....com>
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org, 
	irogers@...gle.com, swapnil.sapkal@....com, mark.rutland@....com, 
	alexander.shishkin@...ux.intel.com, jolsa@...nel.org, rostedt@...dmis.org, 
	vincent.guittot@...aro.org, bristot@...hat.com, adrian.hunter@...el.com, 
	james.clark@....com, kan.liang@...ux.intel.com, gautham.shenoy@....com, 
	kprateek.nayak@....com, juri.lelli@...hat.com, yangjihong@...edance.com, 
	linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org, 
	santosh.shukla@....com, ananth.narayan@....com, sandipan.das@....com
Subject: Re: [RFC 0/4] perf sched: Introduce schedstat tool

On Wed, May 8, 2024 at 11:02 PM Ravi Bangoria <ravi.bangoria@....com> wrote:
>
> >> USAGE
> >> -----
> >>
> >>   # perf sched schedstat record
> >>   # perf sched schedstat report
> >
> > Hmm. I think we can remove the duplication in 'sched'. :)
>
> You mean `perf sched stat record/report` ?
>
> > Given you are thinking of taskstat, how about making it
> > 'cpustat' instead?
>
> Sure. How about:
>
>   # perf sched stat --cpu --task record

If you plan to support both cpu and task at the same time,
then I'm ok with this.  But if they're mutually exclusive, then
probably you want to have them as sub-commands.

Thanks,
Namhyung


>   # perf sched stat report
>
> > Also I think it'd be easier if you also provide 'live' mode so that
> > users can skip record + report steps and run the workload
> > directly like uftrace does. :)
> >
> > Something like this
> >
> >   # perf sched cpustat  myworkload
> >   (result here ...)
>
> Sure.
>
> Thanks for the feedback,
> Ravi