linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>,
	John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] perf cs-etm: Respect timestamp option
Date: Mon, 4 Sep 2023 16:25:38 +0100	[thread overview]
Message-ID: <2a7f6d40-6502-d389-f691-488e3d9b9005@arm.com> (raw)
In-Reply-To: <20230827133557.112494-3-leo.yan@linaro.org>



On 27/08/2023 14:35, Leo Yan wrote:
> When users pass the option '--timestamp' or '-T' in the record command,
> all events will set the PERF_SAMPLE_TIME bit in the attribution.  In
> this case, the AUX event will record the kernel timestamp, but it
> doesn't mean Arm CoreSight enables timestamp packets in its hardware
> tracing.
> 
> If the option '--timestamp' or '-T' is set, this patch always enables
> Arm CoreSight timestamp, as a result, the bit 28 in event's config is to
> be set.
> 
> Before:
> 
>   # perf record -e cs_etm// --per-thread --timestamp -- ls
>   # perf script --header-only
>   ...
>   # event : name = cs_etm//, , id = { 69 }, type = 12, size = 136,
>   config = 0, { sample_period, sample_freq } = 1,
>   sample_type = IP|TID|TIME|CPU|IDENTIFIER, read_format = ID|LOST,
>   disabled = 1, enable_on_exec = 1, sample_id_all = 1, exclude_guest = 1
>   ...
> 
> After:
> 
>   # perf record -e cs_etm// --per-thread --timestamp -- ls
>   # perf script --header-only
>   ...
>   # event : name = cs_etm//, , id = { 49 }, type = 12, size = 136,
>   config = 0x10000000, { sample_period, sample_freq } = 1,
>   sample_type = IP|TID|TIME|CPU|IDENTIFIER, read_format = ID|LOST,
>   disabled = 1, enable_on_exec = 1, sample_id_all = 1, exclude_guest = 1
>   ...
> 
> Signed-off-by: Leo Yan <leo.yan@linaro.org>

Reviewed-by: James Clark <james.clark@arm.com>

> ---
>  tools/perf/arch/arm/util/cs-etm.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/tools/perf/arch/arm/util/cs-etm.c b/tools/perf/arch/arm/util/cs-etm.c
> index cf9ef9ba800b..58c506e9788d 100644
> --- a/tools/perf/arch/arm/util/cs-etm.c
> +++ b/tools/perf/arch/arm/util/cs-etm.c
> @@ -442,6 +442,15 @@ static int cs_etm_recording_options(struct auxtrace_record *itr,
>  					   "contextid", 1);
>  	}
>  
> +	/*
> +	 * When the option '--timestamp' or '-T' is enabled, the PERF_SAMPLE_TIME
> +	 * bit is set for all events.  In this case, always enable Arm CoreSight
> +	 * timestamp tracing.
> +	 */
> +	if (opts->sample_time_set)
> +		evsel__set_config_if_unset(cs_etm_pmu, cs_etm_evsel,
> +					   "timestamp", 1);
> +
>  	/* Add dummy event to keep tracking */
>  	err = parse_event(evlist, "dummy:u");
>  	if (err)

      reply	other threads:[~2023-09-04 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27 13:35 [PATCH v1 0/2] perf cs-etm: Improve timestamp tracing Leo Yan
2023-08-27 13:35 ` [PATCH v1 1/2] perf cs-etm: Validate timestamp tracing in per-thread mode Leo Yan
2023-09-04 15:23   ` James Clark
2023-09-05  1:33     ` Leo Yan
2023-08-27 13:35 ` [PATCH v1 2/2] perf cs-etm: Respect timestamp option Leo Yan
2023-09-04 15:25   ` James Clark [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a7f6d40-6502-d389-f691-488e3d9b9005@arm.com \
    --to=james.clark@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=irogers@google.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).