From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753656AbbGOTF0 (ORCPT ); Wed, 15 Jul 2015 15:05:26 -0400 Received: from mga01.intel.com ([192.55.52.88]:30915 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753637AbbGOTFW (ORCPT ); Wed, 15 Jul 2015 15:05:22 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,482,1432623600"; d="scan'208";a="765132903" From: "Liang, Kan" To: Namhyung Kim CC: "acme@kernel.org" , "jolsa@kernel.org" , "ak@linux.intel.com" , "linux-kernel@vger.kernel.org" , "Hunter, Adrian" Subject: RE: [PATCH RFC V3 3/5] perf,tool: partial time support Thread-Topic: [PATCH RFC V3 3/5] perf,tool: partial time support Thread-Index: AQHQuZcJraDu1Cw7CUiJ8ppxaHjzkJ3Y5hkAgACnhfCAABtBgIADMufw Date: Wed, 15 Jul 2015 19:03:38 +0000 Message-ID: <37D7C6CF3E00A74B8858931C1DB2F0770188D0BB@SHSMSX103.ccr.corp.intel.com> References: <1436345097-11113-1-git-send-email-kan.liang@intel.com> <1436345097-11113-4-git-send-email-kan.liang@intel.com> <20150713132742.GA9917@danjae.kornet> <37D7C6CF3E00A74B8858931C1DB2F0770188BEF4@SHSMSX103.ccr.corp.intel.com> <20150714010449.GB16880@danjae.kornet> In-Reply-To: <20150714010449.GB16880@danjae.kornet> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] 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 t6FJ5Wkt003496 > > However, perf_evlist__id_hdr_size() seems to be affected also. Are you > sure it's okay too? > Yes. id_hdr_size is calculated according to the first event. It impacts perf tool generated COMM, MMAP and FORK events. But all of these events have same and position fixed IDENTIFIER, 0. When parsing the events by perf_evlist__event2evsel, id 0 always return first event. So only first event will be involved to parse perf tool generated COMM, MMAP and FORK events. TIME setting from other events doesn’t impact. Thanks, Kan {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I