From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Mike Leach <mike.leach@linaro.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Coresight ML <coresight@lists.linaro.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"Suzuki K. Poulose" <suzuki.poulose@arm.com>
Subject: Re: [PATCH v4 5/6] coresight: cti: Add in sysfs links to other coresight devices.
Date: Wed, 26 Feb 2020 14:20:32 -0700 [thread overview]
Message-ID: <20200226212032.GB30754@xps15> (raw)
In-Reply-To: <CAJ9a7VjLxTjH7OhRCoPSfiv28kSJ8=LEKSMRfwu41Du+HCh9pA@mail.gmail.com>
On Wed, Feb 26, 2020 at 01:37:17PM +0000, Mike Leach wrote:
> Hi Mathieu,
>
> On Fri, 14 Feb 2020 at 22:58, Mathieu Poirier
> <mathieu.poirier@linaro.org> wrote:
> >
> > On Tue, Feb 11, 2020 at 10:58:07AM +0000, Mike Leach wrote:
> > > Adds in sysfs links for connections where the connected device is another
> > > coresight device. This allows examination of the coresight topology.
> > >
> > > Non-coresight connections remain just as a reference name.
> > >
> > > Signed-off-by: Mike Leach <mike.leach@linaro.org>
> > > ---
> > > drivers/hwtracing/coresight/coresight-cti.c | 41 ++++++++++++++++++++-
> > > 1 file changed, 40 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/hwtracing/coresight/coresight-cti.c b/drivers/hwtracing/coresight/coresight-cti.c
> > > index 9e18e176831c..f620e9460e7d 100644
> > > --- a/drivers/hwtracing/coresight/coresight-cti.c
> > > +++ b/drivers/hwtracing/coresight/coresight-cti.c
> > > @@ -441,6 +441,37 @@ int cti_channel_setop(struct device *dev, enum cti_chan_set_op op,
> > > return err;
> > > }
> > >
> > > +static void cti_add_sysfs_link(struct cti_drvdata *drvdata,
> > > + struct cti_trig_con *tc)
> > > +{
> > > + struct coresight_sysfs_link link_info;
> > > +
> > > + link_info.orig = drvdata->csdev;
> > > + link_info.orig_name = tc->con_dev_name;
> > > + link_info.target = tc->con_dev;
> > > + link_info.target_name = dev_name(&drvdata->csdev->dev);
> > > + coresight_add_sysfs_link(&link_info);
> >
> > I understand there isn't much to do if a problem occurs so just catch the error
> > and add a comment to assert you're doing this on purpose.
> >
>
> When I revisited this code I saw an imbalance between the case where
> the CTI is created first and the associated CSdev is created first.
> The result could be shutdown path where the CTI removes sysfs links
> after the csdev has been removed - which really shouldn't happen.
> Also we could try to remove a sysfs link that we failed to set in the
> first place - again not ideal
>
> I've reworked this code to fix this, and now if the sysfs link fails
> to be set, then we do not set the association between CTI and csdev
> components.
Ok
> This is not sufficient to fail either component from registering, as
> we may have successfully registered previous associations with the
> same CTI.
>
That is also my opinion.
> It seems unlikely that the sysfs link could fail, but if it does, is
> it worth using a dev_warn() to at least log the failure?
>
Yes, that would surely be helpful.
> Regards
>
> Mike
>
>
> > > +}
> > > +
> > > +static void cti_remove_all_sysfs_links(struct cti_drvdata *drvdata)
> > > +{
> > > + struct cti_trig_con *tc;
> > > + struct cti_device *ctidev = &drvdata->ctidev;
> > > + struct coresight_sysfs_link link_info;
> > > +
> > > + /* origin device and target link name constant for this cti */
> > > + link_info.orig = drvdata->csdev;
> > > + link_info.target_name = dev_name(&drvdata->csdev->dev);
> > > +
> > > + list_for_each_entry(tc, &ctidev->trig_cons, node) {
> > > + if (tc->con_dev) {
> > > + link_info.target = tc->con_dev;
> > > + link_info.orig_name = tc->con_dev_name;
> > > + coresight_remove_sysfs_link(&link_info);
> > > + }
> > > + }
> > > +}
> > > +
> > > /*
> > > * Look for a matching connection device name in the list of connections.
> > > * If found then swap in the csdev name, set trig con association pointer
> > > @@ -452,6 +483,8 @@ cti_match_fixup_csdev(struct cti_device *ctidev, const char *node_name,
> > > {
> > > struct cti_trig_con *tc;
> > > const char *csdev_name;
> > > + struct cti_drvdata *drvdata = container_of(ctidev, struct cti_drvdata,
> > > + ctidev);
> > >
> > > list_for_each_entry(tc, &ctidev->trig_cons, node) {
> > > if (tc->con_dev_name) {
> > > @@ -462,6 +495,7 @@ cti_match_fixup_csdev(struct cti_device *ctidev, const char *node_name,
> > > devm_kstrdup(&csdev->dev, csdev_name,
> > > GFP_KERNEL);
> > > tc->con_dev = csdev;
> > > + cti_add_sysfs_link(drvdata, tc);
> > > return true;
> > > }
> > > }
> > > @@ -546,10 +580,12 @@ static void cti_update_conn_xrefs(struct cti_drvdata *drvdata)
> > > struct cti_device *ctidev = &drvdata->ctidev;
> > >
> > > list_for_each_entry(tc, &ctidev->trig_cons, node) {
> > > - if (tc->con_dev)
> > > + if (tc->con_dev) {
> > > /* set tc->con_dev->ect_dev */
> > > coresight_set_assoc_ectdev_mutex(tc->con_dev,
> > > drvdata->csdev);
> > > + cti_add_sysfs_link(drvdata, tc);
> > > + }
> > > }
> > > }
> > >
> > > @@ -602,6 +638,9 @@ static void cti_device_release(struct device *dev)
> > > mutex_lock(&ect_mutex);
> > > cti_remove_conn_xrefs(drvdata);
> > >
> > > + /* clear the dynamic sysfs associate with connections */
> >
> > s/associate/associated
> >
> > > + cti_remove_all_sysfs_links(drvdata);
> > > +
> > > /* remove from the list */
> > > list_for_each_entry_safe(ect_item, ect_tmp, &ect_net, node) {
> > > if (ect_item == drvdata) {
> >
> > With the above:
> >
> > Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> >
> > > --
> > > 2.17.1
> > >
>
>
>
> --
> Mike Leach
> Principal Engineer, ARM Ltd.
> Manchester Design Centre. UK
next prev parent reply other threads:[~2020-02-26 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 10:58 [PATCH v4 0/6] Describe CoreSight topology using sysfs links Mike Leach
2020-02-11 10:58 ` [PATCH v4 1/6] coresight: Pass coresight_device for coresight_release_platform_data Mike Leach
2020-02-11 10:58 ` [PATCH v4 2/6] coresight: add return value for fixup connections Mike Leach
2020-02-11 10:58 ` [PATCH v4 3/6] coresight: Add generic sysfs link creation functions Mike Leach
2020-02-14 23:17 ` Mathieu Poirier
2020-02-25 15:46 ` Mike Leach
2020-02-25 17:07 ` Mathieu Poirier
2020-02-11 10:58 ` [PATCH v4 4/6] coresight: Expose device connections via sysfs Mike Leach
2020-02-14 22:31 ` Mathieu Poirier
2020-02-26 14:32 ` Mike Leach
2020-02-26 21:23 ` Mathieu Poirier
2020-02-11 10:58 ` [PATCH v4 5/6] coresight: cti: Add in sysfs links to other coresight devices Mike Leach
2020-02-14 22:58 ` Mathieu Poirier
2020-02-26 13:37 ` Mike Leach
2020-02-26 21:20 ` Mathieu Poirier [this message]
2020-02-11 10:58 ` [PATCH v4 6/6] coresight: docs: Add information about the topology representations Mike Leach
2020-02-14 23:10 ` Mathieu Poirier
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=20200226212032.GB30754@xps15 \
--to=mathieu.poirier@linaro.org \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).