From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4EB41C4167D for ; Tue, 7 Nov 2023 07:25:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233360AbjKGHZj (ORCPT ); Tue, 7 Nov 2023 02:25:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33784 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233439AbjKGHZh (ORCPT ); Tue, 7 Nov 2023 02:25:37 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 63CF1FC; Mon, 6 Nov 2023 23:25:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1699341935; x=1730877935; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=llRoDtmc+r5SempaBzUob7pMWwccBv60/lBawAuIIt4=; b=BlBNxAUERdLlh2QTQvBwai1bvyuzGETDhvhearQ1oXH8sWO4wh6IcGyF VTFbMCbu4CCPy5uNnLNnDme2DfzbHolnsqOTSF3uwfwXSiAQjxNqBRmXD deLWdY51hj56jdXFQwnrwHIqclJFSSPBstDQ5FY4MpYIqbIyknJvHQEtp +WbZ8DvuEpbrazpP3QV4bLR+EKv/i4jUT2SiJ32EM5OhsQE8INfxIsUh4 ZiTJG8Hn4c9yz84Xsq8alfVgg2K/zK6dTjLMg4osNgbv+CAqBniX3Yfsu KDc7AScB8OgAYIBL+nKKcEOlr6ZUy6RSylpJ+xeNpKwB5vxPa1DNbT5Nc A==; X-IronPort-AV: E=McAfee;i="6600,9927,10886"; a="388327626" X-IronPort-AV: E=Sophos;i="6.03,282,1694761200"; d="scan'208";a="388327626" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Nov 2023 23:19:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10886"; a="1009795977" X-IronPort-AV: E=Sophos;i="6.03,282,1694761200"; d="scan'208";a="1009795977" Received: from ahunter6-mobl1.ger.corp.intel.com (HELO [10.0.2.15]) ([10.252.52.31]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Nov 2023 23:19:14 -0800 Message-ID: <2940af18-8bcd-4456-a8ed-e77cade1b160@intel.com> Date: Tue, 7 Nov 2023 09:19:10 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1 1/2] perf auxtrace: Add 'T' itrace option for timestamp trace To: Arnaldo Carvalho de Melo Cc: Leo Yan , James Clark , Suzuki K Poulose , Mike Leach , John Garry , Will Deacon , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Ian Rogers , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org References: <20231014074513.1668000-1-leo.yan@linaro.org> <20231014074513.1668000-2-leo.yan@linaro.org> <8a2ea58f-f835-4d1a-8bd6-3a63b3b0db94@intel.com> Content-Language: en-US From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/11/23 23:52, Arnaldo Carvalho de Melo wrote: > Em Thu, Oct 19, 2023 at 01:47:15PM +0300, Adrian Hunter escreveu: >> On 14/10/23 10:45, Leo Yan wrote: >>> An AUX trace can contain timestamp, but in some situations, the hardware >>> trace module (e.g. Arm CoreSight) cannot decide the traced timestamp is >>> the same source with CPU's time, thus the decoder can not use the >>> timestamp trace for samples. >>> >>> This patch introduces 'T' itrace option. If users know the platforms >> >> "If users know" <- how would users know? Could the kernel >> or tools also figure it out? > > Adrian, I'm trying to go all the outstanding patches, do you still have > any issues with this series? No, although the question wasn't actually answered. I presume users just have to try the 'T' option and see if it helps.