From: Charlie Jenkins <charlie@rivosinc.com>
To: Aleksandar Rikalo <arikalo@gmail.com>
Cc: linux-riscv@lists.infradead.org,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
linux-kernel@vger.kernel.org,
"Djordje Todorovic" <djordje.todorovic@htecgroup.com>
Subject: Re: [PATCH v3] riscv: Fix the PAUSE Opcode for MIPS P8700.
Date: Thu, 30 Jan 2025 15:00:41 -0800 [thread overview]
Message-ID: <Z5wEmX2ykQJmvnTV@ghost> (raw)
In-Reply-To: <20250129131703.733098-1-arikalo@gmail.com>
On Wed, Jan 29, 2025 at 02:17:03PM +0100, Aleksandar Rikalo wrote:
> From: Djordje Todorovic <djordje.todorovic@htecgroup.com>
>
> The riscv MIPS P8700 uses a different opcode for PAUSE.
> It is a ‘hint’ encoding of the SLLI instruction, with rd=0, rs1=0 and
> imm=5. It will behave as a NOP instruction if no additional behavior
> beyond that of SLLI is implemented.
>
> Add ERRATA_MIPS and ERRATA_MIPS_P8700_PAUSE_OPCODE configs.
> Handle errata for MIPS CPUs.
>
> Signed-off-by: Djordje Todorovic <djordje.todorovic@htecgroup.com>
> Signed-off-by: Aleksandar Rikalo <arikalo@gmail.com>
> Signed-off-by: Raj Vishwanathan4 <rvishwanathan@mips.com>
Please copy people who commented on previous versions of patches in the
new versions!
- Charlie
next prev parent reply other threads:[~2025-01-30 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 13:17 [PATCH v3] riscv: Fix the PAUSE Opcode for MIPS P8700 Aleksandar Rikalo
2025-01-29 16:19 ` Conor Dooley
2025-01-30 22:58 ` Charlie Jenkins
2025-01-31 0:43 ` Conor Dooley
2025-01-31 0:59 ` Charlie Jenkins
2025-01-31 7:20 ` Andrew Jones
2025-01-30 23:00 ` Charlie Jenkins [this message]
2025-02-05 15:44 ` Palmer Dabbelt
2025-03-19 12:26 ` Djordje Todorovic
2025-03-25 9:12 ` Alexandre Ghiti
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=Z5wEmX2ykQJmvnTV@ghost \
--to=charlie@rivosinc.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=arikalo@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=djordje.todorovic@htecgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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