public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org, yangyicong@huawei.com,
	Sami Mujawar <sami.mujawar@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	James Clark <james.clark@arm.com>,
	coresight@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device()
Date: Tue, 8 Aug 2023 14:16:35 +0100	[thread overview]
Message-ID: <20230808131634.GA2369@willie-the-truck> (raw)
In-Reply-To: <8bef9c5a-eede-f78f-4418-da10c99a5bef@arm.com>

On Tue, Aug 08, 2023 at 09:48:16AM +0100, Suzuki K Poulose wrote:
> On 08/08/2023 09:22, 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 | 105 ++++++++++++++++++++++--------------
> >   1 file changed, 65 insertions(+), 40 deletions(-)
> > 
> > diff --git a/drivers/perf/arm_pmu_acpi.c b/drivers/perf/arm_pmu_acpi.c
> > index 90815ad762eb..72454bef2a70 100644
> > --- a/drivers/perf/arm_pmu_acpi.c
> > +++ b/drivers/perf/arm_pmu_acpi.c
> > @@ -69,6 +69,63 @@ static void arm_pmu_acpi_unregister_irq(int cpu)
> >   		acpi_unregister_gsi(gsi);
> >   }
> > +static int __maybe_unused
> > +arm_acpi_register_pmu_device(struct platform_device *pdev, u8 len,
> > +			     u16 (*parse_gsi)(struct acpi_madt_generic_interrupt *))
> > +{
> > +	int cpu, this_hetid, hetid, irq, ret;
> > +	u16 this_gsi, 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;
> > +
> > +		gicc = acpi_cpu_get_madt_gicc(cpu);
> > +		if (gicc->header.length < len)
> > +			return gsi ? -ENXIO : 0;
> > +
> > +		this_gsi = parse_gsi(gicc);
> > +		if (!this_gsi)
> > +			return gsi ? -ENXIO : 0;
> > +
> > +		this_hetid = find_acpi_cpu_topology_hetero_id(cpu);
> > +		if (!gsi) {
> > +			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;
> 
> A postivie return value here could confuse the caller. Also, with my comment
> below, we don't really need to return something from here.

How does this return a positive value?

> > +	int ret = arm_acpi_register_pmu_device(&spe_dev, ACPI_MADT_GICC_SPE,
> > +					       arm_spe_parse_gsi);
> > +	if (ret)
> >   		pr_warn("ACPI: SPE: Unable to register device\n");
> 
> With this change, a system without SPE interrupt description always
> generates the above message. Is this intended ?

If there are no irqs, why doesn't this return 0?
arm_acpi_register_pmu_device() should only fail if either:

  - The static resources passed in are broken
  - The tables are not homogeneous
  - We fail to register the interrupt

so something is amiss.

> Could we not drop the above message as all the other possible error
> scenarios are reported. We could simply make the above helper void, see my
> comment above.

I disagree. If the ACPI tables are borked, we should print a message saying
so.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-08 13:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  8:22 [PATCH V4 0/4] coresight: trbe: Enable ACPI based devices Anshuman Khandual
2023-08-08  8:22 ` [PATCH V4 1/4] arm_pmu: acpi: Refactor arm_spe_acpi_register_device() Anshuman Khandual
2023-08-08  8:48   ` Suzuki K Poulose
2023-08-08 13:16     ` Will Deacon [this message]
2023-08-09 12:54       ` Suzuki K Poulose
2023-08-11  5:02         ` Anshuman Khandual
2023-08-11 10:19         ` Will Deacon
2023-08-16  6:56           ` Anshuman Khandual
2023-08-11  8:43   ` Anshuman Khandual
2023-08-11 10:12     ` Will Deacon
2023-08-11 10:25       ` Anshuman Khandual
2023-08-11 11:00         ` Will Deacon
2023-08-16  6:30           ` Anshuman Khandual
2023-08-08  8:22 ` [PATCH V4 2/4] arm_pmu: acpi: Add a representative platform device for TRBE Anshuman Khandual
2023-08-08  8:22 ` [PATCH V4 3/4] coresight: trbe: Add a representative coresight_platform_data " Anshuman Khandual
2023-08-08  8:22 ` [PATCH V4 4/4] coresight: trbe: Enable ACPI based TRBE devices 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=20230808131634.GA2369@willie-the-truck \
    --to=will@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@arm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@linaro.org \
    --cc=sami.mujawar@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=yangyicong@huawei.com \
    /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