Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <b1127b63-6c6a-e42e-ce6c-cf4f24bbc5a1@intel.com>
Date:   Fri, 14 Jul 2023 10:06:31 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Firefox/102.0 Thunderbird/102.13.0
Subject: Re: [PATCH] perf: add new option '--workload-attr' to set workload
 sched_policy/priority/mask
Content-Language: en-US
To:     Changbin Du <changbin.du@huawei.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>
Cc:     Mark Rutland <mark.rutland@arm.com>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Jiri Olsa <jolsa@kernel.org>,
        Namhyung Kim <namhyung@kernel.org>,
        Ian Rogers <irogers@google.com>,
        linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20230713085831.395112-1-changbin.du@huawei.com>
From:   Adrian Hunter <adrian.hunter@intel.com>
Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki,
 Business Identity Code: 0357606 - 4, Domiciled in Helsinki
In-Reply-To: <20230713085831.395112-1-changbin.du@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.