[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b1127b63-6c6a-e42e-ce6c-cf4f24bbc5a1@intel.com>
Date: Fri, 14 Jul 2023 10:06:31 +0300
From: Adrian Hunter <adrian.hunter@...el.com>
To: Changbin Du <changbin.du@...wei.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Ian Rogers <irogers@...gle.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf: add new option '--workload-attr' to set workload
sched_policy/priority/mask
On 13/07/23 11:58, Changbin Du wrote:
> To get consistent benchmarking results, sometimes we need to set the
> sched_policy/priority/mask of the workload to reduce system noise.
>
> For example, CPU binding is required on big.little system.
>
> $ perf stat -r 10 -- taskset -c 0 ls
>
> Nevertheless, the 'taskset' is also counted here.
>
> To get away of the middleman, this adds a new option '--workload-attr' to
> do the same jobs for stat and record commands.
>
> $ sudo perf stat --workload-attr fifo,40,0x1 -- ls
>
> Above will make 'ls' run on CPU #0 with fifo scheduler and realtime
> priority is 40.
Aren't there ways to set up a process then start perf using -p <pid>
then let the process continue.
Powered by blists - more mailing lists