From: Conor Dooley <conor.dooley@microchip.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Pierre Gondois <pierre.gondois@arm.com>,
<linux-kernel@vger.kernel.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gavin Shan <gshan@redhat.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v4 6/6] arch_topology: Build cacheinfo from primary CPU
Date: Tue, 24 Jan 2023 14:39:19 +0000 [thread overview]
Message-ID: <Y8/tl999NQwbPL/R@wendy> (raw)
In-Reply-To: <20230124140420.4srnufcvamvff77v@bogus>
[-- Attachment #1.1: Type: text/plain, Size: 2649 bytes --]
On Tue, Jan 24, 2023 at 02:04:20PM +0000, Sudeep Holla wrote:
> Conor might help me remember the details.
And I can't shirk either since you know I just replied to Pierre!
> On Tue, Jan 24, 2023 at 02:50:16PM +0100, Geert Uytterhoeven wrote:
> > > @@ -840,6 +840,14 @@ void __init init_cpu_topology(void)
> > > reset_cpu_topology();
> > > return;
> > > }
> > > +
> > > + for_each_possible_cpu(cpu) {
> > > + ret = fetch_cache_info(cpu);
> > > + if (ret) {
> > > + pr_err("Early cacheinfo failed, ret = %d\n", ret);
> >
> > This triggers on all my RV64 platforms (K210, Icicle, Starlight,
> > RZ/Five).
> >
> > This seems to be a respin of
> > https://lore.kernel.org/all/CAMuHMdUBZ791fxCPkKQ6HCwLE4GJB2S35QC=SQ+X8w5Q4C_70g@mail.gmail.com
> > which had the same issue.
> >
>
> I need to recollect my memories reading all the thread, but even after the
> fixes there were few platforms that failed with so early allocation but were
> fine with initcalls. Are these such platforms or am I mixing up things here ?
> Do you still see all the cacheinfo in the sysfs with initcalls that happen
> later in the boot ?
IIRC that stuff was failing back then because riscv calls
init_cpu_topology() far sooner in boot than arm64 does, and therefore
caused allocation failures. You made that warning go away in the below
patch by moving detect_cache_attributes() to update_siblings_masks(),
which both arches call later during boot IIRC:
https://lore.kernel.org/all/20220713133344.1201247-1-sudeep.holla@arm.com
Pierre's patch has added fetch_cache_info() to the problematic
init_cpu_topology() which is called before we can actually do any
allocation in smp_prepare_boot_cpu() or something like that.
That's what I get for only reviewing the patch that was specifically for
riscv, and not the rest of the series... D'oh.
This actually came up a few weeks ago, although I kinda considered the
reason it was triggered to be a bit bogus there, since that dmips property
is not (yet?) a valid property on RISC-V. The patch for that is here:
https://patchwork.kernel.org/project/linux-riscv/patch/20230105033705.3946130-1-leyfoon.tan@starfivetech.com/
I tried it on a PolarFire SoC (unfortunately not an Icicle, I just went
and bricked mine an hour ago) & it should be a fix for this problem too.
My suggested commit message for that is somewhat prophetic now that I
look back at it:
https://lore.kernel.org/all/Y7V4byskevAWKM3G@spud/
I'll ping Palmer about that patch I guess...
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-01-24 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 18:30 [PATCH v4 0/6] arch_topology: Build cacheinfo from primary CPU Pierre Gondois
2023-01-04 18:30 ` [PATCH v4 1/6] cacheinfo: Use RISC-V's init_cache_level() as generic OF implementation Pierre Gondois
2023-01-04 18:30 ` [PATCH v4 2/6] cacheinfo: Return error code in init_of_cache_level() Pierre Gondois
2023-01-04 18:30 ` [PATCH v4 3/6] cacheinfo: Check 'cache-unified' property to count cache leaves Pierre Gondois
2023-01-09 16:13 ` Krzysztof Kozlowski
2023-01-04 18:30 ` [PATCH v4 4/6] ACPI: PPTT: Remove acpi_find_cache_levels() Pierre Gondois
2023-01-04 18:30 ` [PATCH v4 5/6] ACPI: PPTT: Update acpi_find_last_cache_level() to acpi_get_cache_info() Pierre Gondois
2023-01-04 18:30 ` [PATCH v4 6/6] arch_topology: Build cacheinfo from primary CPU Pierre Gondois
2023-01-24 13:50 ` Geert Uytterhoeven
2023-01-24 14:04 ` Sudeep Holla
2023-01-24 14:39 ` Conor Dooley [this message]
2023-01-24 14:48 ` Sudeep Holla
2023-01-24 14:55 ` Sudeep Holla
2023-01-25 14:54 ` Sudeep Holla
2023-01-25 15:28 ` Geert Uytterhoeven
2023-01-25 16:36 ` Sudeep Holla
2023-01-26 8:54 ` Pierre Gondois
2023-01-18 11:55 ` [PATCH v4 0/6] " Sudeep Holla
2023-01-18 12:07 ` Sudeep Holla
2023-01-18 14:12 ` Pierre Gondois
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=Y8/tl999NQwbPL/R@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=gshan@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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