Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Imre Kaloz <kaloz@kernel.org>
Cc: linux-mips@vger.kernel.org,
	Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: mm: Add an R10000 family cache error handler
Date: Tue, 17 Nov 2026 17:57:41 +0100	[thread overview]
Message-ID: <avyHhVQ1LzYa2a-T@alpha.franken.de> (raw)
In-Reply-To: <20261026132613.9875-1-kaloz@kernel.org>

On Mon, Oct 26, 2026 at 02:26:12PM +0100, Imre Kaloz wrote:
> cache_parity_error() does not decode the R10000 family's CacheErr
> layout, and panics with ERL set on every error.
> 
> Recover I-cache errors by rewriting both ways of the set, as
> invalidating leaves the bad word in the data array, and panic on
> others with ERL clear. The handler is built with CONFIG_CPU_R10000.
> 
> Signed-off-by: Imre Kaloz <kaloz@kernel.org>
> ---
>  arch/mips/include/asm/traps.h |   2 +
>  arch/mips/mm/Makefile         |   1 +
>  arch/mips/mm/c-r4k.c          |   9 +++
>  arch/mips/mm/cerr-r10k.c      | 141 ++++++++++++++++++++++++++++++++++
>  arch/mips/mm/cex-r10k.S       | 125 ++++++++++++++++++++++++++++++
>  5 files changed, 278 insertions(+)
>  create mode 100644 arch/mips/mm/cerr-r10k.c
>  create mode 100644 arch/mips/mm/cex-r10k.S

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 ]

      reply	other threads:[~2026-11-17 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 13:26 [PATCH] MIPS: mm: Add an R10000 family cache error handler Imre Kaloz
2026-11-17 16:57 ` Thomas Bogendoerfer [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=avyHhVQ1LzYa2a-T@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=enelsonmoore@gmail.com \
    --cc=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.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