From: Leo Yan <leo.yan@arm.com>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, suzuki.poulose@arm.com,
mike.leach@arm.com, james.clark@linaro.org,
alexander.shishkin@linux.intel.com, jie.gan@oss.qualcomm.com
Subject: Re: [PATCH v6 04/13] coresight: etm4x: exclude ss_status from drvdata->config
Date: Fri, 15 May 2026 11:05:54 +0100 [thread overview]
Message-ID: <20260515100554.GK34802@e132581.arm.com> (raw)
In-Reply-To: <af8gp9rsY6zyo5r7@e129823.arm.com>
On Sat, May 09, 2026 at 12:55:19PM +0100, Yeoreum Yun wrote:
> > > caps->nr_ss_cmp = FIELD_GET(TRCIDR4_NUMSSCC_MASK, etmidr4);
> > > for (i = 0; i < caps->nr_ss_cmp; i++) {
> > > - drvdata->config.ss_status[i] =
> > > - etm4x_relaxed_read32(csa, TRCSSCSRn(i));
> > > + drvdata->ss_status[i] = etm4x_relaxed_read32(csa, TRCSSCSRn(i));
> > > + drvdata->ss_status[i] &= (TRCSSCSRn_PC | TRCSSCSRn_DV |
> > > + TRCSSCSRn_DA | TRCSSCSRn_INST);
> >
> > It is fine for read these capacity bits when probe, but we need to clear
> > status when a session is starting to avoid the stale value left from
> > previous session:
> >
> > drvdata->ss_status[idx] &= ~(TRCSSCSRn_STATUS | TRCSSCSRn_PENDING);
> But, I want to clarify that the perf is one of exceptional case
> since the "etm4_parse_event_config()" is called at the "resume" of session
> for per-thread mode event.
Good point!
The right way would move etm4_parse_event_config() to setup AUX phase
(e.g., call it when build path).
> Anyway as we discussed, since now there have been no issue
> relavant for those bits, let the clear drvdata->ss_status at the
> etm4_parse_event_config().
I am fine to clear status in etm4_parse_event_config() in this series.
Thanks,
Leo
next prev parent reply other threads:[~2026-05-15 10:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 13:21 [PATCH v6 00/13] fix several inconsistencies with sysfs configuration in etmX Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 01/13] coresight: etm4x: fix wrong check of etm4x_sspcicrn_present() Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 02/13] coresight: etm4x: fix underflow for nrseqstate Yeoreum Yun
2026-05-05 16:19 ` Leo Yan
2026-05-15 11:10 ` Yeoreum Yun
2026-05-15 13:29 ` Leo Yan
2026-04-22 13:21 ` [PATCH v6 03/13] coresight: etm4x: introduce struct etm4_caps Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 04/13] coresight: etm4x: exclude ss_status from drvdata->config Yeoreum Yun
2026-05-06 8:48 ` Leo Yan
2026-05-08 15:27 ` Leo Yan
2026-05-09 11:55 ` Yeoreum Yun
2026-05-15 10:05 ` Leo Yan [this message]
2026-04-22 13:21 ` [PATCH v6 05/13] coresight: etm4x: remove redundant fields in etmv4_save_state Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 06/13] coresight: etm4x: fix leaked trace id Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 07/13] coresight: etm4x: fix inconsistencies with sysfs configuration Yeoreum Yun
2026-05-15 8:53 ` Leo Yan
2026-05-15 10:36 ` Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 08/13] coresight: etm4x: remove redundant call etm4_enable_hw() with hotplug Yeoreum Yun
2026-05-15 9:08 ` Leo Yan
2026-05-15 10:51 ` Yeoreum Yun
2026-04-22 13:21 ` [PATCH v6 09/13] coresight: etm4x: missing cscfg_csdev_disable_active_config() in perf enable Yeoreum Yun
2026-05-15 9:39 ` Leo Yan
2026-05-15 13:35 ` Yeoreum Yun
2026-04-22 13:22 ` [PATCH v6 10/13] coresight: etm3x: change drvdata->spinlock type to raw_spin_lock_t Yeoreum Yun
2026-04-22 13:22 ` [PATCH v6 11/13] coresight: etm3x: introduce struct etm_caps Yeoreum Yun
2026-04-22 13:22 ` [PATCH v6 12/13] coresight: etm3x: fix inconsistencies with sysfs configuration Yeoreum Yun
2026-04-22 13:22 ` [PATCH v6 13/13] coresight: etm3x: remove redundant call etm_enable_hw() with hotplug Yeoreum Yun
2026-05-01 12:55 ` [PATCH v6 00/13] fix several inconsistencies with sysfs configuration in etmX Yeoreum Yun
2026-05-01 13:53 ` 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=20260515100554.GK34802@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=jie.gan@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=yeoreum.yun@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.