From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
irogers@google.com, swapnil.sapkal@amd.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
rostedt@goodmis.org, vincent.guittot@linaro.org,
bristot@redhat.com, adrian.hunter@intel.com, james.clark@arm.com,
kan.liang@linux.intel.com, gautham.shenoy@amd.com,
kprateek.nayak@amd.com, juri.lelli@redhat.com,
yangjihong@bytedance.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, santosh.shukla@amd.com,
ananth.narayan@amd.com, sandipan.das@amd.com,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [RFC 0/4] perf sched: Introduce schedstat tool
Date: Fri, 10 May 2024 10:16:13 +0530 [thread overview]
Message-ID: <218f9d7c-135a-16a2-3585-4b13d2d39526@amd.com> (raw)
In-Reply-To: <CAM9d7chvDczhMoOJFLz=MW0ojGm=Ex90CgHhfOsZuLre3vSE3g@mail.gmail.com>
>>>> 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.
Sure, will think about it while preparing next version.
Thanks,
Ravi
prev parent reply other threads:[~2024-05-10 4:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 6:04 [RFC 0/4] perf sched: Introduce schedstat tool Ravi Bangoria
2024-05-08 6:04 ` [RFC 1/4] perf sched: Make `struct perf_sched sched` a global variable Ravi Bangoria
2024-05-08 6:04 ` [RFC 2/4] perf sched: Add template code for schedstat subcommand Ravi Bangoria
2024-05-08 6:04 ` [RFC 3/4] perf sched schedstat: Add record and rawdump support Ravi Bangoria
2024-05-08 6:04 ` [RFC 4/4] perf sched schedstat: Add support for report subcommand Ravi Bangoria
2024-05-11 7:45 ` Chen Yu
2024-05-13 3:13 ` Ravi Bangoria
2024-05-08 22:21 ` [RFC 0/4] perf sched: Introduce schedstat tool Ian Rogers
2024-05-09 5:09 ` Ravi Bangoria
2024-05-09 5:08 ` Namhyung Kim
2024-05-09 6:02 ` Ravi Bangoria
2024-05-09 22:33 ` Namhyung Kim
2024-05-10 4:46 ` Ravi Bangoria [this message]
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=218f9d7c-135a-16a2-3585-4b13d2d39526@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bristot@redhat.com \
--cc=gautham.shenoy@amd.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=swapnil.sapkal@amd.com \
--cc=vincent.guittot@linaro.org \
--cc=yangjihong@bytedance.com \
/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;
as well as URLs for NNTP newsgroup(s).