public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: coresight@lists.linaro.org, denik@chromium.org,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.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>,
	John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] perf cs-etm: Track exception level
Date: Mon, 5 Jun 2023 16:44:45 -0300	[thread overview]
Message-ID: <ZH47LeSnwY2uKs//@kernel.org> (raw)
In-Reply-To: <20230524131958.2139331-1-james.clark@arm.com>

Em Wed, May 24, 2023 at 02:19:54PM +0100, James Clark escreveu:
> Some fixes to support an issue reported by Denis Nikitin where decoding
> trace that contains different EL1 and EL2 kernels can crash or go into
> an infinite loop because the wrong kernel maps are used for the decode.
> 
> This still doesn't support distinguishing guest and host userspace,
> we'd still have to fix the timestamps and do a bit more work to
> correlate that. And I've removed PERF_RECORD_MISC_HYPERVISOR as a
> possible outcome of cs_etm__cpu_mode(). As far as I know this could
> never have been returned anyway because machine__is_host(machine) was
> always true due to session.machines.host being hard coded. And I'm not
> sure of the relevance of the difference between PERF_RECORD_MISC_KERNEL
> and PERF_RECORD_MISC_HYPERVISOR in this scenario.
> 
> The first commit is a tidy up, second fixes a bug that I found when
> comparing the exception level and thread of branch records, the third
> is the main fix, and the last commit is some extra error checking. 
> 
> Applies to acme/perf-tools (4e111f0cf0)

So there seems to be agreement the first two patches can be applied? May
I go ahead and do that now?

- Arnaldo
 
> James Clark (4):
>   perf cs-etm: Only track threads instead of PID and TIDs
>   perf cs-etm: Use previous thread for branch sample source IP
>   perf cs-etm: Track exception level
>   perf cs-etm: Add exception level consistency check
> 
>  .../perf/util/cs-etm-decoder/cs-etm-decoder.c |  13 +-
>  .../perf/util/cs-etm-decoder/cs-etm-decoder.h |   4 +-
>  tools/perf/util/cs-etm.c                      | 220 +++++++++---------
>  tools/perf/util/cs-etm.h                      |   5 +-
>  4 files changed, 126 insertions(+), 116 deletions(-)
> 
> -- 
> 2.34.1
> 

-- 

- Arnaldo

  parent reply	other threads:[~2023-06-05 19:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 13:19 [PATCH 0/4] perf cs-etm: Track exception level James Clark
2023-05-24 13:19 ` [PATCH 1/4] perf cs-etm: Only track threads instead of PID and TIDs James Clark
2023-05-25 10:17   ` Mike Leach
2023-05-27  8:45   ` Leo Yan
2023-06-05 22:11   ` Suzuki K Poulose
2023-05-24 13:19 ` [PATCH 2/4] perf cs-etm: Use previous thread for branch sample source IP James Clark
2023-05-25 11:01   ` Mike Leach
2023-05-27  9:06   ` Leo Yan
2023-05-30 14:28     ` James Clark
2023-06-06  0:44       ` Leo Yan
2023-06-08  9:34       ` James Clark
2023-06-08 10:25         ` Leo Yan
2023-06-08 10:32           ` Leo Yan
2023-06-09 11:00           ` James Clark
2023-06-10  1:20             ` Leo Yan
2023-05-24 13:19 ` [PATCH 3/4] perf cs-etm: Track exception level James Clark
2023-05-25 11:16   ` Mike Leach
2023-05-30  9:24     ` James Clark
2023-05-30 13:16       ` Leo Yan
2023-05-28 11:05   ` Leo Yan
2023-05-30  9:43     ` James Clark
2023-05-24 13:19 ` [PATCH 4/4] perf cs-etm: Add exception level consistency check James Clark
2023-05-25 11:39   ` Mike Leach
2023-05-30  9:12     ` James Clark
2023-05-30 10:40       ` Mike Leach
2023-06-07  9:14         ` James Clark
2023-06-05 19:44 ` Arnaldo Carvalho de Melo [this message]
2023-06-06  0:46   ` [PATCH 0/4] perf cs-etm: Track exception level Leo Yan
2023-06-06 18:07     ` Arnaldo Carvalho de Melo

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=ZH47LeSnwY2uKs//@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=denik@chromium.org \
    --cc=irogers@google.com \
    --cc=james.clark@arm.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