From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Orgad Shaneh <orgads@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] MIPS: OCTEON: require the Core-14449 workaround only on CN63XX pass 1
Date: Sat, 26 Sep 2026 11:35:41 +0200 [thread overview]
Message-ID: <areR7bJxN9YBgrn_@alpha.franken.de> (raw)
In-Reply-To: <20260915071306.15006-5-orgads@gmail.com>
On Tue, Sep 15, 2026 at 07:12:48AM +0000, Orgad Shaneh wrote:
> prom_free_prom_memory() probes the hint field of a compiler-emitted
> PREF and panics when it is not 28, which is what -Wa,-mfix-cn63xxp1
> (CONFIG_CAVIUM_CN63XXP1) rewrites every prefetch in the kernel to. The
> test is gated on OCTEON_IS_MODEL(OCTEON_CN6XXX), so it fires on every
> OCTEON II part, including the pass 2 chips that do not need the
> workaround:
>
> Kernel panic - not syncing: OCTEON II DCache prefetch workaround not
> in place (cfa00004).
> Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1).
>
> on a CN6335-AAP pass 2.2.
>
> Core-14449 is a CN63XX pass 1.x erratum, and the vendor's own runtime
> check says so: it errors out only for OCTEON_CN63XX_PASS1_X without the
> fix, and otherwise merely warns about lost performance when fixed code
> runs on a part that is not a CN63XX. Narrow the check to CN63XX pass
> 1.x to match.
>
> The alternative - enabling CONFIG_CAVIUM_CN63XXP1 to satisfy the check -
> is not free: the assembler flag rewrites every prefetch in the kernel
> (77 of them in this build) to pref 0x1c, which is worth avoiding on an
> in-order core whose receive path is dominated by memcpy.
>
> uasm_i_pref() keeps its OCTEON_CN6XXX condition: it only touches the
> handful of runtime-generated TLB handlers, where the cost does not
> matter.
>
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Orgad Shaneh <orgads@gmail.com>
> ---
> diff --git a/arch/mips/cavium-octeon/setup.c b/arch/mips/cavium-octeon/setup.c
> --- a/arch/mips/cavium-octeon/setup.c
> +++ b/arch/mips/cavium-octeon/setup.c
> @@ -1127,7 +1127,7 @@ EXPORT_SYMBOL(prom_putchar);
>
> void __init prom_free_prom_memory(void)
> {
> - if (OCTEON_IS_MODEL(OCTEON_CN6XXX)) {
> + if (OCTEON_IS_MODEL(OCTEON_CN63XX_PASS1_X)) {
> /* Check for presence of Core-14449 fix. */
> u32 insn;
> u32 *foo;
> --
> 2.47.0
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2026-09-26 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:12 [PATCH 1/5] MIPS: OCTEON: cvmx-l2c: use the OCTEON II register model on all CN6XXX Orgad Shaneh
2026-09-15 7:12 ` [PATCH 2/5] MIPS: OCTEON: cvmx-l2c: add the CN66XX L2 geometry Orgad Shaneh
2026-09-26 9:34 ` Thomas Bogendoerfer
2026-09-15 7:12 ` [PATCH 3/5] MIPS: OCTEON: read the L2 crippled fuses from MIO_FUS_DAT3 on OCTEON II Orgad Shaneh
2026-09-26 9:35 ` Thomas Bogendoerfer
2026-09-15 7:12 ` [PATCH 4/5] MIPS: OCTEON: program L2C_CTL, not L2C_CFG, " Orgad Shaneh
2026-09-26 9:35 ` Thomas Bogendoerfer
2026-09-15 7:12 ` [PATCH 5/5] MIPS: OCTEON: require the Core-14449 workaround only on CN63XX pass 1 Orgad Shaneh
2026-09-26 9:35 ` Thomas Bogendoerfer [this message]
2026-09-26 9:34 ` [PATCH 1/5] MIPS: OCTEON: cvmx-l2c: use the OCTEON II register model on all CN6XXX Thomas Bogendoerfer
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=areR7bJxN9YBgrn_@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=orgads@gmail.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®