From: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
To: "macro@orcam.me.uk" <macro@orcam.me.uk>
Cc: Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
Aleksa Paunovic <aleksa.paunovic@htecgroup.com>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"pjw@kernel.org" <pjw@kernel.org>
Subject: Re: [PATCH] riscv: Add ERRATA_MIPS_P8700_WFI to replace WFI with mips.pause
Date: Mon, 8 Jun 2026 15:12:48 +0000 [thread overview]
Message-ID: <e964f45a-7f6a-4fb8-b9ba-b79dae6d687c@htecgroup.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2605221220540.1450@angie.orcam.me.uk>
Hi Maciej,
On 5/22/26 13:22, Maciej W. Rozycki wrote:
> On Wed, 20 May 2026, Aleksa Paunovic wrote:
>
>>>> The MIPS P8700 has bugs with the WFI instruction.
>>> Has MIPS published an erratum for this? If so, could you add a link to
>>> it in the patch description? If not, could you please briefly describe
>>> the impact of the bug in the patch description, when WFI is used?
>> MIPS has not published an erratum for this. Briefly, a WFI instruction
>> after a mispredicted branch can result in erroneous address translation.
> Shouldn't this be recorded next to actual code rather just the commit
> description?
>
I added the full description of the issue in v2.
Best regards,
Aleksa
next prev parent reply other threads:[~2026-06-08 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 10:50 Aleksa Paunovic via B4 Relay
2026-05-13 18:25 ` Paul Walmsley
2026-05-20 13:44 ` Aleksa Paunovic
2026-05-22 11:22 ` Maciej W. Rozycki
2026-06-08 15:12 ` Aleksa Paunovic [this message]
2026-05-14 2:24 ` kernel test robot
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=e964f45a-7f6a-4fb8-b9ba-b79dae6d687c@htecgroup.com \
--to=aleksa.paunovic@htecgroup.com \
--cc=Djordje.Todorovic@htecgroup.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=palmer@dabbelt.com \
--cc=pjw@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
all inboxes | Powered by JetHome®