From: <Conor.Dooley@microchip.com>
To: <f.fainelli@gmail.com>, <linux-kernel@vger.kernel.org>
Cc: <sudeep.holla@arm.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <ionela.voinescu@arm.com>
Subject: Re: [PATCH] arch_topology: Silence early cacheinfo errors when non-existent
Date: Sat, 6 Aug 2022 18:27:33 +0000 [thread overview]
Message-ID: <9bfc7145-86d7-dc69-bfa0-f36c4c8b42d5@microchip.com> (raw)
In-Reply-To: <20220805230736.1562801-1-f.fainelli@gmail.com>
On 06/08/2022 00:07, Florian Fainelli wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Architectures which do not have cacheinfo such as ARM 32-bit would spit
> out the following during boot:
>
> Early cacheinfo failed, ret = -2
>
> Treat -ENOENT specifically to silence this error since it means that the
> platform does not support reporting its cache information.
Makes sense to me. Maybe we could soften the wording for failures on the
platforms that do support it since early cacheinfo failures (at least on
RISC-V) appear harmless - but that's for another day.
FWIW:
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Fixes: 3fcbf1c77d08 ("arch_topology: Fix cache attributes detection in the CPU hotplug path")
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> drivers/base/arch_topology.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> index 0424b59b695e..eaa1b8d2d39d 100644
> --- a/drivers/base/arch_topology.c
> +++ b/drivers/base/arch_topology.c
> @@ -735,7 +735,7 @@ void update_siblings_masks(unsigned int cpuid)
> int cpu, ret;
>
> ret = detect_cache_attributes(cpuid);
> - if (ret)
> + if (ret && ret != -ENOENT)
> pr_info("Early cacheinfo failed, ret = %d\n", ret);
>
> /* update core and thread sibling masks */
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-08-06 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 23:07 Florian Fainelli
2022-08-06 17:45 ` Sudeep Holla
2022-08-06 18:27 ` Conor.Dooley [this message]
2022-08-10 11:16 ` Michael Walle
2022-08-15 8:57 ` Geert Uytterhoeven
2022-08-15 13:08 ` Sudeep Holla
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=9bfc7145-86d7-dc69-bfa0-f36c4c8b42d5@microchip.com \
--to=conor.dooley@microchip.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®