From: James Clark <james.clark@arm.com>
To: Yabin Cui <yabinc@google.com>, Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Mike Leach <mike.leach@linaro.org>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH] coresight: tmc-etr: Don't enable ETR when it's not ready
Date: Wed, 25 Jan 2023 10:21:09 +0000 [thread overview]
Message-ID: <8200e62a-0038-ae83-4c94-5059110d448e@arm.com> (raw)
In-Reply-To: <CALJ9ZPNa41rO3iG1WhWAF5fBTUGF1ULUG62_zMTA0EwzGnw=8w@mail.gmail.com>
On 24/01/2023 20:09, Yabin Cui wrote:
> Ping for review. And I still can't reproduce it, even if I reduced the
> timeout to 2us and tried different workloads. Any suggestions for how
> to reproduce it?
>
Hi Yabin,
I just found this in my kernel log files from a few days ago.
Jan 19 15:03:35 n1-sdp kernel: [865337.521413] coresight tmc_etr0:
timeout while waiting for completion of Manual Flush
Jan 19 15:03:35 n1-sdp kernel: [865337.529351] coresight tmc_etr0:
timeout while waiting for TMC to be Ready
This is on N1SDP, and I've only been running "normal" perf commands like:
perf record -e cs_etm//k -- taskset -c 2 sleep 1
perf record -e cs_etm// -- stress -c 2 -t 1
I also haven't been able to reproduce it since
James
next prev parent reply other threads:[~2023-01-25 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 23:43 Yabin Cui
2023-01-10 9:30 ` James Clark
2023-01-10 17:48 ` Mike Leach
2023-01-10 18:04 ` Suzuki K Poulose
2023-01-10 21:06 ` Yabin Cui
2023-01-24 20:09 ` Yabin Cui
2023-01-25 10:21 ` James Clark [this message]
2023-01-25 10:27 ` Suzuki K Poulose
2023-01-27 23:10 ` [PATCH v2] coresight: tmc: Don't enable TMC " Yabin Cui
2023-02-01 20:43 ` Mike Leach
2023-02-02 11:24 ` Suzuki K Poulose
2023-02-02 20:54 ` Yabin Cui
2023-02-02 21:46 ` [PATCH v3] " Yabin Cui
2023-02-09 1:08 ` Yabin Cui
2023-02-09 10:31 ` Suzuki K Poulose
2023-02-10 23:43 ` [PATCH] coresight: tmc-etr: Handle enable failure in tmc_read_unprepare_etr Yabin Cui
2023-02-21 18:38 ` Yabin Cui
2023-02-22 9:33 ` Suzuki K Poulose
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=8200e62a-0038-ae83-4c94-5059110d448e@arm.com \
--to=james.clark@arm.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=yabinc@google.com \
/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
all inboxes | Powered by JetHome®