[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50399556C9727B4D88A595C8584AAB37526515F5@GSjpTKYDCembx32.service.hitachi.net>
Date: Fri, 11 Dec 2015 02:15:43 +0000
From: 平松雅巳 / HIRAMATU,MASAMI
<masami.hiramatsu.pt@...achi.com>
To: "'Arnaldo Carvalho de Melo'" <acme@...nel.org>,
"Wangnan (F)" <wangnan0@...wei.com>
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Adrian Hunter <adrian.hunter@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-perf-users@...r.kernel.org" <linux-perf-users@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
"Namhyung Kim" <namhyung@...nel.org>, Jiri Olsa <jolsa@...hat.com>,
Alexei Starovoitov <ast@...mgrid.com>
Subject: RE: [PATCH perf/core 00/22] perf refcnt debugger API and fixes
From: 'Arnaldo Carvalho de Melo' [mailto:acme@...nel.org]
>
>But this requires having these special refcnt__ routines, that will make
>tools/perf/ code patterns for reference counts look different that the
>refcount patterns in the kernel :-\
BTW, I think even without the refcnt debugger, we'd better introduce this
kind API to unify the refcnt operation in perf code. As I said, we have many
miscodings on current implementation. Unifying the API can enforce developers
to avoid such miscodings.
Thank you,
Powered by blists - more mailing lists