From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Christoph_M=C3=BCllner_=3Cchristoph=2Emuellner=40vrull=2Eeu=3E?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, philipp.tomsich@vrull.eu,
bjorn@kernel.org, dbarboza@ventanamicro.com, heiko@sntech.de,
cooper.qu@linux.alibaba.com, zhiwei_liu@linux.alibaba.com,
eric.huang@linux.alibaba.com, alistair.francis@wdc.com,
ajones@ventanamicro.com, conor@kernel.org, dqfext@gmail.com,
alex@ghiti.fr, samuel.holland@sifive.com
Subject: Re: [PATCH v3 0/2] RISC-V: Test th.sxstatus.MAEE bit before enabling MAEE
Date: Thu, 25 Apr 2024 23:00:30 +0000 [thread overview]
Message-ID: <171408603073.8761.4519771274981632479.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240407213236.2121592-1-christoph.muellner@vrull.eu>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 7 Apr 2024 23:32:34 +0200 you wrote:
> Currently, the Linux kernel suffers from a boot regression when running
> on the c906 QEMU emulation. Details have been reported here by Björn Töpel:
> https://lists.gnu.org/archive/html/qemu-devel/2024-01/msg04766.html
>
> The main issue is, that Linux enables XTheadMae for CPUs that have a T-Head
> mvendorid but QEMU maintainers don't want to emulate a CPU that uses
> reserved bits in PTEs. See also the following discussion for more
> context:
> https://lists.gnu.org/archive/html/qemu-devel/2024-02/msg00775.html
>
> [...]
Here is the summary with links:
- [v3,1/2] riscv: thead: Rename T-Head PBMT to MAE
https://git.kernel.org/riscv/c/6179d4a21300
- [v3,2/2] riscv: T-Head: Test availability bit before enabling MAE errata
https://git.kernel.org/riscv/c/65b71cc35cc6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-04-25 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 21:32 [PATCH v3 0/2] RISC-V: Test th.sxstatus.MAEE bit before enabling MAEE Christoph Müllner
2024-04-07 21:32 ` [PATCH v3 1/2] riscv: thead: Rename T-Head PBMT to MAE Christoph Müllner
2024-04-07 21:32 ` [PATCH v3 2/2] riscv: T-Head: Test availability bit before enabling MAE errata Christoph Müllner
2024-04-08 1:58 ` Yangyu Chen
2024-04-08 6:00 ` Christoph Müllner
2024-04-08 7:36 ` Yangyu Chen
2024-04-08 7:55 ` Christoph Müllner
2024-04-08 8:10 ` Conor Dooley
2024-04-08 8:21 ` Yangyu Chen
2024-04-08 9:06 ` Conor Dooley
2024-04-25 23:00 ` patchwork-bot+linux-riscv [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=171408603073.8761.4519771274981632479.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?q?Christoph_M=C3=BCllner_=3Cchristoph=2Emuellner=40vrull=2Eeu=3E?=@ci.codeaurora.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=alistair.francis@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=conor@kernel.org \
--cc=cooper.qu@linux.alibaba.com \
--cc=dbarboza@ventanamicro.com \
--cc=dqfext@gmail.com \
--cc=eric.huang@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=samuel.holland@sifive.com \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).