From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/5] perf: arm_cspmu: Support shared interrupts
Date: Fri, 2 Jun 2023 00:04:42 -0700 (PDT) [thread overview]
Message-ID: <77b19b2d-a84e-eb13-db38-78cb34a444a8@os.amperecomputing.com> (raw)
In-Reply-To: <e2f2c524-c7c5-7a55-aee5-699b069a445a@arm.com>
Hi Robin,
On Thu, 1 Jun 2023, Robin Murphy wrote:
> On 2023-06-01 04:01, Ilkka Koskinen wrote:
>> Some of the PMUs may share the interrupt. Support them by
>> setting IRQF_SHARED
>
> This has the usual problem of allowing any PMU instance to move the IRQ
> affinity to a different CPU without also migrating all the other PMU
> contexts, and thus breaking perf core's assumptions of mutual exclusion.
I see, I wasn't aware of such an assumption. Sounds like there isn't
necessarily an easy and clean solution for the shared interrupt case. I
drop the patch and get back on the issue if we come up with something
reasonable later.
Cheers, Ilkka
>
> Thanks,
> Robin.
>
>> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>> ---
>> drivers/perf/arm_cspmu/arm_cspmu.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/perf/arm_cspmu/arm_cspmu.c
>> b/drivers/perf/arm_cspmu/arm_cspmu.c
>> index 88547a2b73e6..cc5204d1b5fb 100644
>> --- a/drivers/perf/arm_cspmu/arm_cspmu.c
>> +++ b/drivers/perf/arm_cspmu/arm_cspmu.c
>> @@ -1067,8 +1067,8 @@ static int arm_cspmu_request_irq(struct arm_cspmu
>> *cspmu)
>> return irq;
>> ret = devm_request_irq(dev, irq, arm_cspmu_handle_irq,
>> - IRQF_NOBALANCING | IRQF_NO_THREAD,
>> dev_name(dev),
>> - cspmu);
>> + IRQF_NOBALANCING | IRQF_NO_THREAD |
>> IRQF_SHARED,
>> + dev_name(dev), cspmu);
>> if (ret) {
>> dev_err(dev, "Could not request IRQ %d\n", irq);
>> return ret;
>
next prev parent reply other threads:[~2023-06-02 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 3:01 [PATCH v2 0/5] perf: ampere: Add support for Ampere SoC PMUs Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 1/5] perf: arm_cspmu: Support 32-bit accesses to 64-bit registers Ilkka Koskinen
2023-06-01 14:49 ` Robin Murphy
2023-06-02 6:47 ` Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 2/5] perf: arm_cspmu: Support shared interrupts Ilkka Koskinen
2023-06-01 14:54 ` Robin Murphy
2023-06-02 7:04 ` Ilkka Koskinen [this message]
2023-06-02 11:25 ` Robin Murphy
2023-06-01 3:01 ` [PATCH v2 3/5] perf: arm_cspmu: Support implementation specific filters Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 4/5] perf: arm_cspmu: Support implementation specific event validation Ilkka Koskinen
2023-06-01 15:09 ` Robin Murphy
2023-06-02 7:09 ` Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 5/5] perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU Ilkka Koskinen
2023-06-01 15:23 ` Robin Murphy
2023-06-02 7:13 ` Ilkka Koskinen
2023-06-02 11:51 ` Robin Murphy
2023-06-03 1:16 ` kernel test robot
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=77b19b2d-a84e-eb13-db38-78cb34a444a8@os.amperecomputing.com \
--to=ilkka@os.amperecomputing.com \
--cc=bwicaksono@nvidia.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).