[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <573F2DE0.8090003@huawei.com>
Date: Fri, 20 May 2016 23:31:44 +0800
From: "Wangnan (F)" <wangnan0@...wei.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
CC: <arnaldo.melo@...il.com>, <linux-kernel@...r.kernel.org>,
He Kuang <hekuang@...wei.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jiri Olsa <jolsa@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Zefan Li <lizefan@...wei.com>, <pi3orama@....com>
Subject: Re: [PATCH 09/17] perf tools: Detect avalibility of write_backward
On 2016/5/13 21:08, Arnaldo Carvalho de Melo wrote:
> Em Fri, May 13, 2016 at 07:56:06AM +0000, Wang Nan escreveu:
>> Detect avalibility of write_backward and save the result into
>> record_opts. With write_backward the start pointer of a ring
>> buffer mapped read only can be found reliably.
> We have perf_missing_features for that, please try to use it.
I'll try it, but write_backward can't fallback, if kernel doesn't
support it, I think we'd better throw an error earlier. Using
perf_missing_features we get error during opening the event, so if we want
to fail earlier we still need API probing.
Thank you.
Powered by blists - more mailing lists