Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752647AbbGMTCR (ORCPT ); Mon, 13 Jul 2015 15:02:17 -0400 Received: from mga02.intel.com ([134.134.136.20]:3200 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751918AbbGMTCP (ORCPT ); Mon, 13 Jul 2015 15:02:15 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,464,1432623600"; d="scan'208";a="746341887" 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: AQHQuZcJraDu1Cw7CUiJ8ppxaHjzkJ3Y5hkAgACnhfA= Date: Mon, 13 Jul 2015 19:01:51 +0000 Message-ID: <37D7C6CF3E00A74B8858931C1DB2F0770188BEF4@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> In-Reply-To: <20150713132742.GA9917@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 t6DJ2QcI020166 Content-Length: 1520 Lines: 35 > Hi, > > (CC-ing Adrian) > > On Wed, Jul 08, 2015 at 04:44:55AM -0400, kan.liang@intel.com wrote: > > From: Kan Liang > > > > When multiple events are sampled it may not be needed to collect fine > > grained time stamps on all events. The sample sites are usually nearby. > > It's enough to have time stamps on the regular reference events. > > This patchkit adds the ability to turn off time stamps per event. This > > in term can reduce sampling overhead and the size of the perf.data. > > So this patch makes the PERF_SAMPLE_TIME bit set or not independently, > right? But AFAIK we sometimes just use first evsel for checking > sample_type value, especially for evlist->id_pos. I'm not sure it'll work for > all cases of mixed time/notime events.. > If the sample_type is different, IDENTIFIER will be set to make sure id is in a fixed position. So we don't need to worry about evlist->id_pos here. I think the only unsupported case should be that the kernel doesn't support IDENTIFIER. If so, under my test, perf record will print warning " failed to process type". Perf report will also print warning " non matching sample_type". So the user can switch back to full time support. If you think the warning is not good enough, we can show specific warning and error out when non IDENTIFIER support is detected. Thanks, Kan ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?