From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Raag Jadav <raag.jadav@intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: arm_cspmu: Don't touch interrupt registers if no interrupt was assigned
Date: Fri, 5 Apr 2024 15:33:47 -0700 (PDT) [thread overview]
Message-ID: <89d7ff41-ce2a-fd95-ebfc-4df914efd4c8@os.amperecomputing.com> (raw)
In-Reply-To: <042bbb32-481e-40d8-a46a-472b724ec33f@arm.com>
On Fri, 5 Apr 2024, Robin Murphy wrote:
> On 2024-03-07 7:31 pm, Ilkka Koskinen wrote:
>> The driver enabled and disabled interrupts even if no interrupt was
>> assigned to the device.
>
> Why's that a concern - if the interrupt isn't routed anywhere, surely it
> makes no difference what happens at the source end?
The issue is that we have two PMUs attached to the same interrupt line.
Unfortunately, I just don't seem to find time to add support for shared
interrupts to the cspmu driver. Meanwhile, I assigned the interrupt
to one of the PMUs while the other one has zero in the APMT table. Without
the patch, I can trigger "ghost interrupt" in the latter PMU.
Cheers, Ilkka
>
> Thanks,
> Robin.
>
>> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>> ---
>> drivers/perf/arm_cspmu/arm_cspmu.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/perf/arm_cspmu/arm_cspmu.c
>> b/drivers/perf/arm_cspmu/arm_cspmu.c
>> index 50b89b989ce7..2cbdb5dcb6ff 100644
>> --- a/drivers/perf/arm_cspmu/arm_cspmu.c
>> +++ b/drivers/perf/arm_cspmu/arm_cspmu.c
>> @@ -795,7 +795,8 @@ static void arm_cspmu_enable_counter(struct arm_cspmu
>> *cspmu, int idx)
>> inten_off = PMINTENSET + (4 * reg_id);
>> cnten_off = PMCNTENSET + (4 * reg_id);
>> - writel(BIT(reg_bit), cspmu->base0 + inten_off);
>> + if (cspmu->irq)
>> + writel(BIT(reg_bit), cspmu->base0 + inten_off);
>> writel(BIT(reg_bit), cspmu->base0 + cnten_off);
>> }
>> @@ -810,7 +811,8 @@ static void arm_cspmu_disable_counter(struct
>> arm_cspmu *cspmu, int idx)
>> cnten_off = PMCNTENCLR + (4 * reg_id);
>> writel(BIT(reg_bit), cspmu->base0 + cnten_off);
>> - writel(BIT(reg_bit), cspmu->base0 + inten_off);
>> + if (cspmu->irq)
>> + writel(BIT(reg_bit), cspmu->base0 + inten_off);
>> }
>> static void arm_cspmu_event_update(struct perf_event *event)
>
next prev parent reply other threads:[~2024-04-05 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:31 [PATCH] perf: arm_cspmu: Don't touch interrupt registers if no interrupt was assigned Ilkka Koskinen
2024-04-04 20:35 ` Ilkka Koskinen
2024-04-05 10:33 ` Robin Murphy
2024-04-05 22:33 ` Ilkka Koskinen [this message]
2024-04-08 12:05 ` Robin Murphy
2024-04-09 1:05 ` Ilkka Koskinen
2024-04-09 12:53 ` Robin Murphy
2024-04-11 7:35 ` Ilkka Koskinen
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=89d7ff41-ce2a-fd95-ebfc-4df914efd4c8@os.amperecomputing.com \
--to=ilkka@os.amperecomputing.com \
--cc=bwicaksono@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=raag.jadav@intel.com \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@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