From: Ben Horgan <ben.horgan@arm.com>
To: Thorsten Blum <blum@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: cacheinfo: Simplify init_cache_level()
Date: Wed, 4 Nov 2026 11:19:04 +0000 [thread overview]
Message-ID: <33d55cde-9dc1-4d61-8053-f1c1a2e95179@arm.com> (raw)
In-Reply-To: <ausSAhn0qRagNcrz@kernel.org>
Hi Thorsten,
On 04/11/2026 11:07, Thorsten Blum wrote:
> Hi Ben,
>
> On Wed, Nov 04, 2026 at 10:32:58AM +0000, Ben Horgan wrote:
>> Hi Thorsten,
>>
>> On 04/11/2026 08:36, Thorsten Blum wrote:
>>> acpi_get_cache_info() already sets fw_level to 0 on failure, so drop the
>>> redundant check and the manual assignment.
>>
>> This doesn't seem to be the case when CONFIG_ACPI_PPTT is not defined. Can the dummy implementation
>> in include/linux/cacheinfo.h be called from init_cache_level()? For the implementation in
>
> On arm64, ACPI_PPTT is selected when ACPI is enabled. When ACPI is
> disabled, acpi_disabled = 1 and init_cache_level() won't call the stub.
Ok, that's true.
>
>> drivers/acpi/pptt.c levels is documented as "Number of levels if success." and so would be good to
>> mention what happens in the error case if it needs to be relied on.
>
> Below the parameter descriptions, it already says:
>
> "Errors caused by lack of a PPTT table, or otherwise, return 0
> indicating we didn't find any cache levels."
Ah yes, I should have read on.
Thanks,
Ben
>
> Thanks,
> Thorsten
prev parent reply other threads:[~2026-11-04 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:36 Thorsten Blum
2026-11-04 10:32 ` Ben Horgan
2026-11-04 11:07 ` Thorsten Blum
2026-11-04 11:19 ` Ben Horgan [this message]
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=33d55cde-9dc1-4d61-8053-f1c1a2e95179@arm.com \
--to=ben.horgan@arm.com \
--cc=blum@kernel.org \
--cc=catalin.marinas@arm.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®