Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753116AbbLKCPt (ORCPT ); Thu, 10 Dec 2015 21:15:49 -0500 Received: from mail9.hitachi.co.jp ([133.145.228.44]:39451 "EHLO mail9.hitachi.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752484AbbLKCPr (ORCPT ); Thu, 10 Dec 2015 21:15:47 -0500 From: =?utf-8?B?5bmz5p2+6ZuF5bezIC8gSElSQU1BVFXvvIxNQVNBTUk=?= To: "'Arnaldo Carvalho de Melo'" , "Wangnan (F)" CC: Peter Zijlstra , Adrian Hunter , "linux-kernel@vger.kernel.org" , "linux-perf-users@vger.kernel.org" , Ingo Molnar , "Namhyung Kim" , Jiri Olsa , Alexei Starovoitov Subject: RE: [PATCH perf/core 00/22] perf refcnt debugger API and fixes Thread-Topic: [PATCH perf/core 00/22] perf refcnt debugger API and fixes Thread-Index: AQHRMifqdrp25x+uR0WYuBPwTEPEhp7CE3gAgAGJXGD///sdAIAAJ0qAgAFPCEA= Date: Fri, 11 Dec 2015 02:15:43 +0000 Message-ID: <50399556C9727B4D88A595C8584AAB37526515F5@GSjpTKYDCembx32.service.hitachi.net> References: <20151209021047.10245.8918.stgit@localhost.localdomain> <20151209134138.GB15864@kernel.org> <50399556C9727B4D88A595C8584AAB375264FB48@GSjpTKYDCembx32.service.hitachi.net> <56697572.90701@huawei.com> <20151210151239.GB17996@kernel.org> In-Reply-To: <20151210151239.GB17996@kernel.org> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.198.220.44] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id tBB2Ft0K005732 Content-Length: 673 Lines: 15 From: 'Arnaldo Carvalho de Melo' [mailto:acme@kernel.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, ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?