Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] coresight: etm3x: Correctly output counter values in sysfs node
Date: Sat, 8 Apr 2017 17:43:28 +0200	[thread overview]
Message-ID: <20170408154328.GB22401@kroah.com> (raw)
In-Reply-To: <1490634573-11068-3-git-send-email-mathieu.poirier@linaro.org>

On Mon, Mar 27, 2017 at 11:09:32AM -0600, Mathieu Poirier wrote:
> From: Olav Haugan <ohaugan@codeaurora.org>
> 
> cntr_val_show function does not print the intended information. It is only
> printing the latest counter value. Fix this.
> 
> Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
>  drivers/hwtracing/coresight/coresight-etm3x-sysfs.c | 18 ++++++++++++++----
>  1 file changed, 14 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/hwtracing/coresight/coresight-etm3x-sysfs.c b/drivers/hwtracing/coresight/coresight-etm3x-sysfs.c
> index 4cbbd1313331..62acf07d604b 100644
> --- a/drivers/hwtracing/coresight/coresight-etm3x-sysfs.c
> +++ b/drivers/hwtracing/coresight/coresight-etm3x-sysfs.c
> @@ -730,19 +730,29 @@ static ssize_t cntr_val_show(struct device *dev,
>  	u32 val;
>  	struct etm_drvdata *drvdata = dev_get_drvdata(dev->parent);
>  	struct etm_config *config = &drvdata->config;
> +	int buf_size = PAGE_SIZE;
>  
>  	if (!local_read(&drvdata->mode)) {
>  		spin_lock(&drvdata->spinlock);
> -		for (i = 0; i < drvdata->nr_cntr; i++)
> -			ret += scnprintf(buf, PAGE_SIZE, "counter %d: %x\n",
> -				       i, config->cntr_val[i]);
> +		for (i = 0; i < drvdata->nr_cntr; i++) {
> +			ret += scnprintf(&buf[ret], buf_size,
> +					 "counter %d: %x\n",
> +					 i, config->cntr_val[i]);
> +			buf_size -= ret;
> +			if (buf_size <= 0)
> +				break;
> +		}

This is NOT a one-value-per-file thing.  That needs to be fixed, don't
try to make it worse here.  You are not following the proper sysfs
rules.

I can't take this, sorry.

greg k-h

  reply	other threads:[~2017-04-08 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 17:09 [PATCH 0/3] coresight: next v4.11-rc4 Mathieu Poirier
2017-03-27 17:09 ` [PATCH 1/3] coresight: Replace sprintf with scnprintf Mathieu Poirier
2017-04-08 15:42   ` Greg KH
2017-04-24 22:26     ` Olav Haugan
2017-03-27 17:09 ` [PATCH 2/3] coresight: etm3x: Correctly output counter values in sysfs node Mathieu Poirier
2017-04-08 15:43   ` Greg KH [this message]
2017-03-27 17:09 ` [PATCH 3/3] coresight: Fixes coresight DT parse to get correct output port ID 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=20170408154328.GB22401@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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