All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Jesse Taube <jtaubepe@redhat.com>
Subject: Re: [PATCH] riscv: Add support for early boot errata application on MIPS chips
Date: Thu, 20 Aug 2026 19:53:29 -0600 (MDT)	[thread overview]
Message-ID: <1bd31b3c-bdbe-37e1-0f0a-3cf152ff81d5@kernel.org> (raw)
In-Reply-To: <20260810-p8700-early-boot-v1-1-5c4aa08d500f@htecgroup.com>

On Mon, 10 Aug 2026, Aleksa Paunovic via B4 Relay wrote:

> From: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> 
> MIPS errata implementation previously skipped early boot application
> entirely. Although the only currently existing MIPS erratum does not
> require this, amending this now should make any future addition easier to
> implement.
> 
> This commit was based on the existing T-Head implementation.
> 
> Suggested-by: Jesse Taube <jtaubepe@redhat.com>
> Link: https://lore.kernel.org/linux-riscv/CADRr4bcbD57hmR0XGgo8BjgNp4shEADOondZEtwscCJ9-nxXRQ@mail.gmail.com/
> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> ---
> The patch was motivated by Jesse's suggestion to implement [2] as an early boot erratum.
> However, since it's in conflict with [1] as well, I decided against sending this one and the ZALRSC patch as a series,
> opting for rebasing [1] and [2] once it's clear we should move forward with this approach.
> 
> I tested this on an eight-hart QEMU config. The testing was done by rebasing [1] and [2] onto the patch
> and running most of the same tests used to verify those patches. This includes: coremark testing, futex kselftests
> and GDB to check errata application. The same tests were run on the Boston board, configured with a single P8700 core.
> 
> Links:
> [1] https://lore.kernel.org/linux-riscv/20260608-p8700-wfi-v2-1-77efc7459f3d@htecgroup.com/
> [2] https://lore.kernel.org/linux-riscv/20260723-p8700-zalrsc-v4-1-59c21b252e29@htecgroup.com/

Thanks, queued for v7.4.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Jesse Taube <jtaubepe@redhat.com>
Subject: Re: [PATCH] riscv: Add support for early boot errata application on MIPS chips
Date: Thu, 20 Aug 2026 19:53:29 -0600 (MDT)	[thread overview]
Message-ID: <1bd31b3c-bdbe-37e1-0f0a-3cf152ff81d5@kernel.org> (raw)
In-Reply-To: <20260810-p8700-early-boot-v1-1-5c4aa08d500f@htecgroup.com>

On Mon, 10 Aug 2026, Aleksa Paunovic via B4 Relay wrote:

> From: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> 
> MIPS errata implementation previously skipped early boot application
> entirely. Although the only currently existing MIPS erratum does not
> require this, amending this now should make any future addition easier to
> implement.
> 
> This commit was based on the existing T-Head implementation.
> 
> Suggested-by: Jesse Taube <jtaubepe@redhat.com>
> Link: https://lore.kernel.org/linux-riscv/CADRr4bcbD57hmR0XGgo8BjgNp4shEADOondZEtwscCJ9-nxXRQ@mail.gmail.com/
> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> ---
> The patch was motivated by Jesse's suggestion to implement [2] as an early boot erratum.
> However, since it's in conflict with [1] as well, I decided against sending this one and the ZALRSC patch as a series,
> opting for rebasing [1] and [2] once it's clear we should move forward with this approach.
> 
> I tested this on an eight-hart QEMU config. The testing was done by rebasing [1] and [2] onto the patch
> and running most of the same tests used to verify those patches. This includes: coremark testing, futex kselftests
> and GDB to check errata application. The same tests were run on the Boston board, configured with a single P8700 core.
> 
> Links:
> [1] https://lore.kernel.org/linux-riscv/20260608-p8700-wfi-v2-1-77efc7459f3d@htecgroup.com/
> [2] https://lore.kernel.org/linux-riscv/20260723-p8700-zalrsc-v4-1-59c21b252e29@htecgroup.com/

Thanks, queued for v7.4.


- Paul

  reply	other threads:[~2026-08-21  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 15:09 [PATCH] riscv: Add support for early boot errata application on MIPS chips Aleksa Paunovic via B4 Relay
2026-08-10 15:09 ` Aleksa Paunovic
2026-08-10 15:09 ` Aleksa Paunovic via B4 Relay
2026-08-21  1:53 ` Paul Walmsley [this message]
2026-08-21  1:53   ` Paul Walmsley

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=1bd31b3c-bdbe-37e1-0f0a-3cf152ff81d5@kernel.org \
    --to=pjw@kernel.org \
    --cc=Djordje.Todorovic@htecgroup.com \
    --cc=aleksa.paunovic@htecgroup.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=jtaubepe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.