Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: KxQsdmD2Xnw4wMDFHhAUWP77swj1/8kOj8ZF2nFfV88aGbX6KHyuiGjTenA0wdS1ekxWWAOHww
 VRAsOckh+nIw==
IronPort-SDR: RE/xa3+o+iHwkdx65ezadGIgFW85JCcG0zwz3wNxR5kLyBF+8N0Db864L+r0AY+adPMo8sJ5pN
 mL4Pr4mXBz1w==
Date:   Mon, 3 May 2021 07:56:37 -0700
From:   Andi Kleen <ak@linux.intel.com>
To:     Adrian Hunter <adrian.hunter@intel.com>
Cc:     Arnaldo Carvalho de Melo <acme@kernel.org>,
        Jiri Olsa <jolsa@redhat.com>, 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

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