From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device()
Date: Wed, 2 Aug 2023 08:14:36 +0530 [thread overview]
Message-ID: <e0c378fc-15f8-0f7f-1fa7-9b498294b9bb@arm.com> (raw)
In-Reply-To: <20230801144936.GE26253@willie-the-truck>
On 8/1/23 20:19, Will Deacon wrote:
> On Tue, Aug 01, 2023 at 03:10:49PM +0530, Anshuman Khandual wrote:
>> Sanity checking all the GICC tables for same interrupt number, and ensuring
>> a homogeneous ACPI based machine, could be used for other platform devices
>> as well. Hence this refactors arm_spe_acpi_register_device() into a common
>> helper arm_acpi_register_pmu_device().
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Co-developed-by: Will Deacon <will@kernel.org>
>> Signed-off-by: Will Deacon <will@kernel.org>
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>> drivers/perf/arm_pmu_acpi.c | 110 +++++++++++++++++++++++-------------
>> 1 file changed, 70 insertions(+), 40 deletions(-)
>>
>> diff --git a/drivers/perf/arm_pmu_acpi.c b/drivers/perf/arm_pmu_acpi.c
>> index 90815ad762eb..d9d5a7bbb92f 100644
>> --- a/drivers/perf/arm_pmu_acpi.c
>> +++ b/drivers/perf/arm_pmu_acpi.c
>> @@ -70,6 +70,68 @@ static void arm_pmu_acpi_unregister_irq(int cpu)
>> }
>>
>> #if IS_ENABLED(CONFIG_ARM_SPE_PMU)
>> +static int
>> +arm_acpi_register_pmu_device(struct platform_device *pdev, u8 len,
>> + u16 (*parse_gsi)(struct acpi_madt_generic_interrupt *))
>> +{
>> + int cpu, hetid, irq, ret;
>> + bool matched = false;
>> + u16 gsi = 0;
>> +
>> + /*
>> + * Ensure that platform device must have IORESOURCE_IRQ
>> + * resource to hold gsi interrupt.
>> + */
>> + if (pdev->num_resources != 1)
>> + return -ENXIO;
>> +
>> + if (pdev->resource[0].flags != IORESOURCE_IRQ)
>> + return -ENXIO;
>> +
>> + /*
>> + * Sanity check all the GICC tables for the same interrupt
>> + * number. For now, only support homogeneous ACPI machines.
>> + */
>> + for_each_possible_cpu(cpu) {
>> + struct acpi_madt_generic_interrupt *gicc;
>> + u16 this_gsi;
>> +
>> + gicc = acpi_cpu_get_madt_gicc(cpu);
>> + if (gicc->header.length < len)
>> + return matched ? -ENXIO : 0;
>> +
>> + this_gsi = parse_gsi(gicc);
>> + if (!this_gsi)
>> + return matched ? -ENXIO : 0;
>
> I think you can push this check into the conditional below...
>
>> +
>> + if (!matched) {
>> + hetid = find_acpi_cpu_topology_hetero_id(cpu);
>
> ... i.e. add a:
>
> if (!this_gsi)
> return -ENXIO;
>
> here.
>
>> + gsi = this_gsi;
>> + matched = true;
>
> And then, come to think of it, can we get rid of 'matched' altogether?
> Since a gsi of 0 is treated as invalid, we could just check that instead,
> no? So this becomes:
>
>
> gicc = acpi_cpu_get_madt_gicc(cpu);
> if (gicc->header.length < len)
> return gsi ? -ENXIO : 0;
>
> this_hetid = find_acpi_cpu_topology_hetero_id(cpu);
> this_gsi = parse_gsi(gicc);
> if (!gsi) {
> if (!this_gsi)
> return -ENXIO;
Unlike before, this returns -ENXIO on the very first instance itself without
a match. Previously this returned 0 in such cases. But I guess that is okay.
> gsi = this_gsi;
> hetid = this_hetid;
> } else if (hetid != this_hetid || gsi != this_gsi) {
> pr_warn("ACPI: %s: must be homogeneous\n", pdev->name);
> return -ENXIO;
> }
>
>
> What do you reckon?
This makes sense, and the modified function will look something like
arm_acpi_register_pmu_device(struct platform_device *pdev, u8 len,
u16 (*parse_gsi)(struct acpi_madt_generic_interrupt *))
{
int cpu, irq, ret;
u16 gsi = 0;
/*
* Ensure that platform device must have IORESOURCE_IRQ
* resource to hold gsi interrupt.
*/
if (pdev->num_resources != 1)
return -ENXIO;
if (pdev->resource[0].flags != IORESOURCE_IRQ)
return -ENXIO;
/*
* Sanity check all the GICC tables for the same interrupt
* number. For now, only support homogeneous ACPI machines.
*/
for_each_possible_cpu(cpu) {
struct acpi_madt_generic_interrupt *gicc;
int this_hetid, hetid;
u16 this_gsi;
gicc = acpi_cpu_get_madt_gicc(cpu);
if (gicc->header.length < len)
return gsi ? -ENXIO : 0;
this_hetid = find_acpi_cpu_topology_hetero_id(cpu);
this_gsi = parse_gsi(gicc);
if (!gsi) {
if (!this_gsi)
return -ENXIO;
hetid = this_hetid;
gsi = this_gsi;
} else if (hetid != this_hetid || gsi != this_gsi) {
pr_warn("ACPI: %s: must be homogeneous\n", pdev->name);
return -ENXIO;
}
}
irq = acpi_register_gsi(NULL, gsi, ACPI_LEVEL_SENSITIVE, ACPI_ACTIVE_HIGH);
if (irq < 0) {
pr_warn("ACPI: %s Unable to register interrupt: %d\n", pdev->name, gsi);
return -ENXIO;
}
pdev->resource[0].start = irq;
ret = platform_device_register(pdev);
if (ret < 0) {
pr_warn("ACPI: %s: Unable to register device\n", pdev->name);
acpi_unregister_gsi(gsi);
}
return ret;
}
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-02 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:40 [PATCH V2 0/4] coresight: trbe: Enable ACPI based devices Anshuman Khandual
2023-08-01 9:40 ` [PATCH V2 1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device() Anshuman Khandual
2023-08-01 14:49 ` Will Deacon
2023-08-02 2:44 ` Anshuman Khandual [this message]
2023-08-01 9:40 ` [PATCH V2 2/4] arm_pmu: acpi: Add a representative platform device for TRBE Anshuman Khandual
2023-08-01 14:51 ` Will Deacon
2023-08-02 1:07 ` Anshuman Khandual
2023-08-02 10:11 ` Suzuki K Poulose
2023-08-03 4:06 ` Anshuman Khandual
2023-08-01 9:40 ` [PATCH V2 3/4] coresight: trbe: Add a representative coresight_platform_data " Anshuman Khandual
2023-08-01 9:40 ` [PATCH V2 4/4] coresight: trbe: Enable ACPI based TRBE devices Anshuman Khandual
2023-08-01 14:52 ` [PATCH V2 0/4] coresight: trbe: Enable ACPI based devices Will Deacon
2023-08-02 0:51 ` Anshuman Khandual
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=e0c378fc-15f8-0f7f-1fa7-9b498294b9bb@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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