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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 67756C433B4 for ; Mon, 3 May 2021 14:56:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 28531611BF for ; Mon, 3 May 2021 14:56:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230042AbhECO5f (ORCPT ); Mon, 3 May 2021 10:57:35 -0400 Received: from mga11.intel.com ([192.55.52.93]:46980 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229607AbhECO5c (ORCPT ); Mon, 3 May 2021 10:57:32 -0400 IronPort-SDR: KxQsdmD2Xnw4wMDFHhAUWP77swj1/8kOj8ZF2nFfV88aGbX6KHyuiGjTenA0wdS1ekxWWAOHww VRAsOckh+nIw== X-IronPort-AV: E=McAfee;i="6200,9189,9973"; a="194614527" X-IronPort-AV: E=Sophos;i="5.82,270,1613462400"; d="scan'208";a="194614527" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 May 2021 07:56:39 -0700 IronPort-SDR: RE/xa3+o+iHwkdx65ezadGIgFW85JCcG0zwz3wNxR5kLyBF+8N0Db864L+r0AY+adPMo8sJ5pN mL4Pr4mXBz1w== X-IronPort-AV: E=Sophos;i="5.82,270,1613462400"; d="scan'208";a="428397588" Received: from tassilo.jf.intel.com ([10.54.74.11]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 May 2021 07:56:39 -0700 Date: Mon, 3 May 2021 07:56:37 -0700 From: Andi Kleen To: Adrian Hunter Cc: Arnaldo Carvalho de Melo , Jiri Olsa , linux-kernel@vger.kernel.org Subject: Re: [PATCH] perf record: Set timestamp boundary for AUX area events Message-ID: <20210503145637.GN4032392@tassilo.jf.intel.com> References: <20210503064222.5319-1-adrian.hunter@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210503064222.5319-1-adrian.hunter@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 03, 2021 at 09:42:22AM +0300, Adrian Hunter wrote: > AUX area data is not processed by 'perf record' and consequently the > --timestamp-boundary option may result in no values for "time of first > sample" and "time of last sample". However there are non-sample events > that can be used instead, namely 'itrace_start' and 'aux'. > 'itrace_start' is issued before tracing starts, and 'aux' is issued > every time data is ready. Hmm, what happens when some other non PT events are in the same perf record? And those maybe run at different times than PT (e.g. due to some PT specific filter). Does this all work correctly then? -Andi