From: "Zhouwen (Jonathan, Turing)" <jonathan.zhouwen@huawei.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Zhangshaokun <zhangshaokun@hisilicon.com>,
Lizixian <lizixian@hisilicon.com>,
Mike Leach <mike.leach@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH] coresight: etm4x: fix mis-usage of nr_resource in sysfs interface
Date: Fri, 4 Sep 2020 18:08:46 +0800 [thread overview]
Message-ID: <366a1ee2-cfce-ba58-a3e9-7d0efa546743@huawei.com> (raw)
In-Reply-To: <20200903172243.GB312784@xps15>
Hi Mathieu,
Thanks for your review.
在 2020/9/4 1:22, Mathieu Poirier 写道:
> On Wed, Sep 02, 2020 at 03:52:56PM +0800, Jonathan Zhou wrote:
>> The member @nr_resource represents how many resource selector pairs,
>> and the pair 0 is always implemented and reserved.
>> So let's multiply by 2 when displaying the implemented resource seletors
>> and resetting the seletor configuration .
>> And also update the validation of the input @idx.
>>
>> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
>> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Cc: Mike Leach <mike.leach@linaro.org>
>> Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
>> Cc: lizixian@hisilicon.com
>> Signed-off-by: Jonathan Zhou <jonathan.zhouwen@huawei.com>
>> ---
>> drivers/hwtracing/coresight/coresight-etm4x-sysfs.c | 15 ++++++++++-----
>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c b/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c
>> index b673e738bc9a..635b93d20efa 100644
>> --- a/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c
>> +++ b/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c
>> @@ -143,8 +143,10 @@ static ssize_t nr_resource_show(struct device *dev,
>> {
>> unsigned long val;
>> struct etmv4_drvdata *drvdata = dev_get_drvdata(dev->parent);
>> -
>> - val = drvdata->nr_resource;
>> + /* @nr_resource represents how many resource selector pairs,
>> + * hence multiply by 2.
>
> Your comment said it correctly, @nr_resource present the number of _pairs_. As
> such the code is correct and there is no need to multiply by 2.
>
Sorry for not mentioned the reason of modified this. From the function
@res_ctrl_store, we can see that only one individual resource selector
can be accessed via the ->res_idx. Therefore, it may be better to show
the number of individual resource selectors.
>> + */
>> + val = 2 * drvdata->nr_resource;
>> return scnprintf(buf, PAGE_SIZE, "%#lx\n", val);
>> }
>> static DEVICE_ATTR_RO(nr_resource);
>> @@ -236,7 +238,7 @@ static ssize_t reset_store(struct device *dev,
>> }
>>
>> config->res_idx = 0x0;
>> - for (i = 0; i < drvdata->nr_resource; i++)
>> + for (i = 2; i < 2 * drvdata->nr_resource; i++)
>> config->res_ctrl[i] = 0x0;
>
> This hunk is correct - please send a patch for it.
Ok.
>
>>
>> config->ss_idx = 0x0;
>> @@ -1663,8 +1665,11 @@ static ssize_t res_idx_store(struct device *dev,
>>
>> if (kstrtoul(buf, 16, &val))
>> return -EINVAL;
>> - /* Resource selector pair 0 is always implemented and reserved */
>> - if ((val == 0) || (val >= drvdata->nr_resource))
>> + /*
>> + * Resource selector pair 0 is always implemented and reserved,
>> + * namely an idx with 0 and 1 is illegal.
>> + */
>> + if ((val == 0) || (val == 1) || (val >= 2 * drvdata->nr_resource))
>> return -EINVAL;
>
> The index, i.e ->res_idx, represent pairs an not individual resource.
>
> Thanks,
> Mathieu
>
If we want all of the ->res_ctrl accessable, the ->res_idx should
represent individual resource. That's the reason.
Best regards.
Jonathan.
>>
>> /*
>> --
>> 1.9.1
>>
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-04 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 7:52 [PATCH] coresight: etm4x: fix mis-usage of nr_resource in sysfs interface Jonathan Zhou
2020-09-03 17:22 ` Mathieu Poirier
2020-09-04 10:08 ` Zhouwen (Jonathan, Turing) [this message]
2020-09-08 17:35 ` Mathieu Poirier
2020-09-09 6:19 ` Jonathan Zhou
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=366a1ee2-cfce-ba58-a3e9-7d0efa546743@huawei.com \
--to=jonathan.zhouwen@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lizixian@hisilicon.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=zhangshaokun@hisilicon.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