mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v1 1/1] perf/smmuv3: Don't cast parameter in bit operations
Date: Wed, 9 Feb 2022 21:45:54 +0000	[thread overview]
Message-ID: <9d0d5c82-f609-576f-b1ed-d4c2b4f2340e@arm.com> (raw)
In-Reply-To: <20220209184758.56578-1-andriy.shevchenko@linux.intel.com>

On 2022-02-09 18:47, Andy Shevchenko wrote:
> While in this particular case it would not be a (critical) issue,
> the pattern itself is bad and error prone in case somebody blindly
> copies to their code.
> 
> Don't cast parameter to unsigned long pointer in the bit operations.
> Instead copy to a local variable on stack of a proper type and use.

Seems reasonable, in fact in my build it appears to save a spill and 
reload from the stack so the code actually gets a teeny bit better. Not 
sure a cleanup warrants a "Fixes" tag, but either way,

Reviewed-by: Robin Murphy <robin.murphy@arm.com>

> Note, new compilers might warn on this line for potential outbound access.
> 
> Fixes: 7d839b4b9e00 ("perf/smmuv3: Add arm64 smmuv3 pmu driver")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>   drivers/perf/arm_smmuv3_pmu.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/perf/arm_smmuv3_pmu.c b/drivers/perf/arm_smmuv3_pmu.c
> index c49108a72865..00d4c45a8017 100644
> --- a/drivers/perf/arm_smmuv3_pmu.c
> +++ b/drivers/perf/arm_smmuv3_pmu.c
> @@ -654,6 +654,7 @@ static int smmu_pmu_offline_cpu(unsigned int cpu, struct hlist_node *node)
>   static irqreturn_t smmu_pmu_handle_irq(int irq_num, void *data)
>   {
>   	struct smmu_pmu *smmu_pmu = data;
> +	DECLARE_BITMAP(ovs, BITS_PER_TYPE(u64));
>   	u64 ovsr;
>   	unsigned int idx;
>   
> @@ -663,7 +664,8 @@ static irqreturn_t smmu_pmu_handle_irq(int irq_num, void *data)
>   
>   	writeq(ovsr, smmu_pmu->reloc_base + SMMU_PMCG_OVSCLR0);
>   
> -	for_each_set_bit(idx, (unsigned long *)&ovsr, smmu_pmu->num_counters) {
> +	bitmap_from_u64(ovs, ovsr);
> +	for_each_set_bit(idx, ovs, smmu_pmu->num_counters) {
>   		struct perf_event *event = smmu_pmu->events[idx];
>   		struct hw_perf_event *hwc;
>   

  reply	other threads:[~2022-02-09 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 18:47 Andy Shevchenko
2022-02-09 21:45 ` Robin Murphy [this message]
2022-02-15 23:18 ` Will Deacon

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=9d0d5c82-f609-576f-b1ed-d4c2b4f2340e@arm.com \
    --to=robin.murphy@arm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®