mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Chunyan Zhang <zhang.chunyan@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2/2] coresight: Fix reference count for software sources
Date: Tue, 14 Mar 2017 17:55:33 +0000	[thread overview]
Message-ID: <c6534dee-172b-24b0-0aee-84c9c8ccafaa@arm.com> (raw)
In-Reply-To: <CANLsYkwg_PRcL5Sqd15phOFS-L8-v3SdvF1kBFa9De-==tx9gw@mail.gmail.com>

On 14/03/17 17:40, Mathieu Poirier wrote:
> On 14 March 2017 at 11:32, Mathieu Poirier <mathieu.poirier@linaro.org> wrote:
>> From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
>>
>> For software sources (i.e STM), there could be multiple agents
>> generating the trace data, unlike the ETMs. So we need to
>> properly do the accounting for the active number of users
>> to disable the device when the last user goes away. Right
>> now, the reference counting is broken for sources as we skip
>> the actions when we detect that the source is enabled.
>>
>> This patch fixes the problem by adding the refcounting for
>> software sources, even when they are enabled.
>>
>> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
>> Reported-by: Robert Walker <robert.walker@arm.com>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> ---
>>  drivers/hwtracing/coresight/coresight.c | 13 +++++++++++--
>>  1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight.c b/drivers/hwtracing/coresight/coresight.c
>> index 34cd1ed..2da9e39 100644
>> --- a/drivers/hwtracing/coresight/coresight.c
>> +++ b/drivers/hwtracing/coresight/coresight.c
>> @@ -552,6 +552,7 @@ int coresight_enable(struct coresight_device *csdev)
>>         int cpu, ret = 0;
>>         struct coresight_device *sink;
>>         struct list_head *path;
>> +       enum coresight_dev_subtype_source subtype = csdev->subtype.source_subtype;
>
> Checkpatch.pl complains about a line over 80 characters.


Hmm, I think the name of the enum is unusually long. I could clean it up a little bit.
Also, it does look silly to split a simple variable assignment though.

What do you prefer ?

Suzuki

  reply	other threads:[~2017-03-14 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 15:27 [PATCH 0/2] coresight: Allow sharing of STM Suzuki K Poulose
2017-03-09 15:27 ` [PATCH 1/2] coresight: Disable the path only when the source is disabled Suzuki K Poulose
2017-03-14 17:37   ` [1/2] " Mathieu Poirier
2017-03-14 17:39     ` Suzuki K Poulose
2017-03-09 15:27 ` [PATCH 2/2] coresight: Fix reference count for software sources Suzuki K Poulose
2017-03-14 17:40   ` [2/2] " Mathieu Poirier
2017-03-14 17:55     ` Suzuki K Poulose [this message]
2017-03-14 19:32       ` Mathieu Poirier
2017-03-14 18:06     ` Suzuki K Poulose
2017-03-15  3:51       ` Chunyan Zhang
2017-03-15 16:00         ` Suzuki K Poulose
2017-03-16 12:13           ` Chunyan Zhang
2017-03-17 10:36             ` Suzuki K Poulose

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=c6534dee-172b-24b0-0aee-84c9c8ccafaa@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=zhang.chunyan@linaro.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

Powered by JetHome