mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Leo Yan <leo.yan@linaro.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Mike Leach <mike.leach@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Daniel Kiss <Daniel.Kiss@arm.com>,
	Denis Nikitin <denik@chromium.org>,
	coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Al Grant <al.grant@arm.com>
Subject: Re: [PATCH v2 2/7] coresight: etm-perf: Support PID tracing for kernel at EL2
Date: Tue, 2 Feb 2021 23:06:16 +0000	[thread overview]
Message-ID: <3c0a0641-a375-c7c3-d72d-e1d626e60ad6@arm.com> (raw)
In-Reply-To: <20210202163842.134734-3-leo.yan@linaro.org>

On 2/2/21 4:38 PM, Leo Yan wrote:
> From: Suzuki K Poulose <suzuki.poulose@arm.com>
> 
> When the kernel is running at EL2, the PID is stored in CONTEXTIDR_EL2.
> So, tracing CONTEXTIDR_EL1 doesn't give us the pid of the process.
> Thus we should trace the VMID with VMIDOPT set to trace CONTEXTIDR_EL2
> instead of CONTEXTIDR_EL1.  Given that we have an existing config
> option "contextid" and this will be useful for tracing virtual machines
> (when we get to support virtualization).
> 
> So instead, this patch extends option CTXTID with an extra bit
> ETM_OPT_CTXTID2 (bit 15), thus on an EL2 kernel, we will have another
> bit available for the perf tool: ETM_OPT_CTXTID is for kernel running in
> EL1, ETM_OPT_CTXTID2 is used when kernel runs in EL2 with VHE enabled.
> 
> The tool must be backward compatible for users, i.e, "contextid" today
> traces PID and that should remain the same; for this purpose, the perf
> tool is updated to automatically set corresponding bit for the
> "contextid" config, therefore, the user doesn't have to bother which EL
> the kernel is running.
> 
>    i.e, perf record -e cs_etm/contextid/u --
> 
> will always do the "pid" tracing, independent of the kernel EL.
> 
> The driver parses the format "contextid", which traces CONTEXTIDR_EL1
> for ETM_OPT_CTXTID (on EL1 kernel) and traces CONTEXTIDR_EL2 for
> ETM_OPT_CTXTID2 (on EL2 kernel).
> 
> Besides the enhancement for format "contexid", extra two formats are
> introduced: "contextid1" and "contextid2".  This considers to support
> tracing both CONTEXTIDR_EL1 and CONTEXTIDR_EL2 when the kernel is
> running at EL2.  Finally, the PMU formats are defined as follow:
> 
>    "contextid1": Available on both EL1 kernel and EL2 kernel.  When the
>                  kernel is running at EL1, "contextid1" enables the PID
> 		tracing; when the kernel is running at EL2, this enables
> 		tracing the PID of guest applications.
> 
>    "contextid2": Only usable when the kernel is running at EL2.  When
>                  selected, enables PID tracing on EL2 kernel.
> 
>    "contextid":  Will be an alias for the option that enables PID
>                  tracing.  I.e,
>                  contextid == contextid1, on EL1 kernel.
>                  contextid == contextid2, on EL2 kernel.
> 
> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> Cc: Al Grant <al.grant@arm.com>
> Cc: Mike Leach <mike.leach@linaro.org>
> Cc: Leo Yan <leo.yan@linaro.org>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

You may add the following line here :

[ Added two config formats: contextid1, contextid2 ]

> Signed-off-by: Leo Yan <leo.yan@linaro.org>

The patch as such looks good to me.

Suzuki

  reply	other threads:[~2021-02-02 23:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 16:38 [PATCH v2 0/7] coresight: etm-perf: Fix pid tracing with VHE Leo Yan
2021-02-02 16:38 ` [PATCH v2 1/7] coresight: etm-perf: Clarify comment on perf options Leo Yan
2021-02-02 23:00   ` Suzuki K Poulose
2021-02-04  3:36     ` Leo Yan
2021-02-02 16:38 ` [PATCH v2 2/7] coresight: etm-perf: Support PID tracing for kernel at EL2 Leo Yan
2021-02-02 23:06   ` Suzuki K Poulose [this message]
2021-02-05 13:47     ` Mike Leach
2021-02-02 16:38 ` [PATCH v2 3/7] perf cs-etm: Fix bitmap for option Leo Yan
2021-02-05 11:47   ` Mike Leach
2021-02-02 16:38 ` [PATCH v2 4/7] perf cs-etm: Support PID tracing in config Leo Yan
2021-02-05 13:48   ` Mike Leach
2021-02-02 16:38 ` [PATCH v2 5/7] perf cs-etm: Add helper cs_etm__get_pid_fmt() Leo Yan
2021-02-02 23:19   ` Suzuki K Poulose
2021-02-04  3:47     ` Leo Yan
2021-02-04 10:54       ` Suzuki K Poulose
2021-02-04 11:23         ` Leo Yan
2021-02-02 16:38 ` [PATCH v2 6/7] perf cs-etm: Detect pid in VMID for kernel running at EL2 Leo Yan
2021-02-02 23:29   ` Suzuki K Poulose
2021-02-04  4:00     ` Leo Yan
2021-02-04 10:57       ` Suzuki K Poulose
2021-02-02 16:38 ` [PATCH v2 7/7] Documentation: coresight: Add PID tracing description Leo Yan
2021-02-02 23:24   ` Suzuki K Poulose
2021-02-04  4:02     ` Leo Yan
2021-02-03 17:39   ` Mike Leach
2021-02-04  4:09     ` Leo Yan
2021-02-04 11:08       ` Suzuki K Poulose
2021-02-04 12:14         ` Mike Leach
2021-02-05  5:42           ` Leo Yan

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=3c0a0641-a375-c7c3-d72d-e1d626e60ad6@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=Daniel.Kiss@arm.com \
    --cc=acme@kernel.org \
    --cc=al.grant@arm.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=coresight@lists.linaro.org \
    --cc=denik@chromium.org \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --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

Powered by JetHome