[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3ac920f7-d8b1-fb90-ab6b-ba75bc8b5b2a@linux.intel.com>
Date: Tue, 4 Sep 2018 20:50:28 +0300
From: Alexey Budankov <alexey.budankov@...ux.intel.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 1/2]: perf util: map data buffer for preserving
collected data
Hi,
On 04.09.2018 20:34, Andi Kleen wrote:
>> .sample = process_sample_event,
>> @@ -1678,6 +1680,8 @@ static struct option __record_options[] = {
>> "signal"),
>> OPT_BOOLEAN(0, "dry-run", &dry_run,
>> "Parse options then exit"),
>> + OPT_INTEGER(0, "aio", &record.opts.nr_cblocks,
>> + "asynchronous trace write operations (min: 1, max: 32, default: 2)"),
>
> would need to be documented in the manpage. But I would rather make it an
> ~/.perfconfig option
Yep, make sense, it requires to be configurable w/o recompilation and
at the same time its meaning is not obvious to be on the command line for a user.
>
>
> -Andi
>
Powered by blists - more mailing lists