From: Leo Yan <leo.yan@arm.com>
To: Yabin Cui <yabinc@google.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] coresight: core: Disable helpers for devices that fail to enable
Date: Wed, 2 Apr 2025 14:32:32 +0100 [thread overview]
Message-ID: <20250402133232.GJ115840@e132581.arm.com> (raw)
In-Reply-To: <CALJ9ZPOvcxswvfbpWkXgJ=WL+HLa33nm0ZzHogYNZ9keXfi1MA@mail.gmail.com>
On Tue, Apr 01, 2025 at 06:22:46PM -0700, Yabin Cui wrote:
> On Tue, Apr 1, 2025 at 6:19 PM Yabin Cui <yabinc@google.com> wrote:
> >
> > When enabling a SINK or LINK type coresight device fails, the
> > associated helpers should be disabled.
> >
> > Signed-off-by: Yabin Cui <yabinc@google.com>
> > Suggested-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> > ---
> > drivers/hwtracing/coresight/coresight-core.c | 12 ++++--------
> > 1 file changed, 4 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/hwtracing/coresight/coresight-core.c
> > index fb43ef6a3b1f..e3270d9b46c9 100644
> > --- a/drivers/hwtracing/coresight/coresight-core.c
> > +++ b/drivers/hwtracing/coresight/coresight-core.c
> > @@ -465,7 +465,7 @@ int coresight_enable_path(struct coresight_path *path, enum cs_mode mode,
> > /* Enable all helpers adjacent to the path first */
> > ret = coresight_enable_helpers(csdev, mode, path);
> > if (ret)
> > - goto err;
> > + goto err_helper;
> > /*
> > * ETF devices are tricky... They can be a link or a sink,
> > * depending on how they are configured. If an ETF has been
> > @@ -480,14 +480,8 @@ int coresight_enable_path(struct coresight_path *path, enum cs_mode mode,
> > switch (type) {
> > case CORESIGHT_DEV_TYPE_SINK:
> > ret = coresight_enable_sink(csdev, mode, sink_data);
> > - /*
> > - * Sink is the first component turned on. If we
> > - * failed to enable the sink, there are no components
> > - * that need disabling. Disabling the path here
> > - * would mean we could disrupt an existing session.
> > - */
> > if (ret)
> > - goto out;
> > + goto err;
> > break;
> > case CORESIGHT_DEV_TYPE_SOURCE:
> > /* sources are enabled from either sysFS or Perf */
> > @@ -507,6 +501,8 @@ int coresight_enable_path(struct coresight_path *path, enum cs_mode mode,
> > out:
> > return ret;
> > err:
> > + coresight_disable_helpers(csdev);
Given it is unconditionally to enable helpers, I would suggest we
disable helper unconditionally. Thus, we don't need to add a new
'err_helper' tag, simply reuse the 'err' tag would be fine.
I would like to know if mainatiners have different opinions.
Thanks,
Leo
> > +err_helper:
> > coresight_disable_path_from(path, nd);
> > goto out;
> > }
> > --
> > 2.49.0.472.ge94155a9ec-goog
> >
next prev parent reply other threads:[~2025-04-02 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 1:18 [PATCH v2 0/3] coresight: catu: Introduce refcount and spinlock for enabling/disabling Yabin Cui
2025-04-02 1:18 ` [PATCH v2 1/3] " Yabin Cui
2025-04-02 1:21 ` Yabin Cui
2025-04-02 13:01 ` Leo Yan
2025-04-03 17:53 ` Yabin Cui
2025-04-04 9:46 ` Suzuki K Poulose
2025-04-02 1:18 ` [PATCH v2 2/3] coresight: catu: Prevent concurrent PERF and SYSFS mode enablement Yabin Cui
2025-04-02 13:47 ` Leo Yan
2025-04-03 17:58 ` Yabin Cui
2025-04-02 1:18 ` [PATCH v2 3/3] coresight: core: Disable helpers for devices that fail to enable Yabin Cui
2025-04-02 1:22 ` Yabin Cui
2025-04-02 13:32 ` Leo Yan [this message]
2025-04-02 13:50 ` Mike Leach
2025-04-02 14:12 ` Leo Yan
2025-04-03 0:53 ` Jie Gan
2025-04-03 18:28 ` Yabin Cui
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=20250402133232.GJ115840@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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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