[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0689aa59-426e-2f37-dcc4-d79b1e89403c@amd.com>
Date: Thu, 9 May 2024 11:32:12 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: Namhyung Kim <namhyung@...nel.org>
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,
Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [RFC 0/4] perf sched: Introduce schedstat tool
>> 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
# 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
Powered by blists - more mailing lists