From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Richard Henderson <richard.henderson@linaro.org>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Andrew Jones <ajones@ventanamicro.com>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>
Subject: [PATCH 0/2] RISC-V: Add Ztso extension
Date: Wed, 7 Feb 2024 13:22:53 +0100 [thread overview]
Message-ID: <20240207122256.902627-1-christoph.muellner@vrull.eu> (raw)
The first patch of this series picks up an earlier v2 Ztso patch from Palmer,
which can be found here:
https://patchwork.kernel.org/project/qemu-devel/patch/20220917072635.11616-1-palmer@rivosinc.com/
This patch did not apply cleanly but the necessary changes were trivial.
There was a request to extend the commit message, which is part of the
posted patch of this series. As this patch was reviewed a year ago,
I believe it could be merged.
The second patch simply exposes Ztso via hwprobe.
Relevant in this context might be also, that Richard's patch to improve
TCG's memory barrier selection depending on host and guest memory ordering
landed in June 2023:
https://lore.kernel.org/all/a313b36b-dcc1-f812-ccbd-afed1cbd523b@linaro.org/T/
The first patch was already sent as part of an RFC series for Ssdtso:
https://lists.nongnu.org/archive/html/qemu-devel/2023-11/msg02962.html
Since I don't want to keep this patch until the ratification of Ssdtso,
I would like to get this merged independent of Ssdtso.
This series is based on today's riscv-to-apply.next with my other series
that adds the new hwprobe keys
(https://lists.gnu.org/archive/html/qemu-devel/2024-02/msg01293.html).
This series can also be found here:
https://github.com/cmuellner/qemu/tree/ztso
Christoph Müllner (1):
linux-user/riscv: Add Ztso extension to hwprobe
Palmer Dabbelt (1):
RISC-V: Add support for Ztso
linux-user/syscall.c | 3 +++
target/riscv/cpu.c | 2 ++
target/riscv/cpu_cfg.h | 1 +
target/riscv/insn_trans/trans_rva.c.inc | 11 ++++++++---
target/riscv/insn_trans/trans_rvi.c.inc | 16 ++++++++++++++--
target/riscv/insn_trans/trans_rvv.c.inc | 20 ++++++++++++++++++++
target/riscv/translate.c | 3 +++
7 files changed, 51 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-07 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 12:22 Christoph Müllner [this message]
2024-02-07 12:22 ` [PATCH 1/2] RISC-V: Add support for Ztso Christoph Müllner
2024-02-26 1:29 ` Alistair Francis
2024-02-07 12:22 ` [PATCH 2/2] linux-user/riscv: Add Ztso extension to hwprobe Christoph Müllner
2024-02-14 13:33 ` Daniel Henrique Barboza
2024-02-26 1:30 ` Alistair Francis
2024-02-14 13:35 ` [PATCH 0/2] RISC-V: Add Ztso extension Daniel Henrique Barboza
2024-02-14 13:38 ` Christoph Müllner
2024-02-14 13:42 ` Daniel Henrique Barboza
2024-02-14 16:24 ` Andrew Jones
2024-02-15 9:53 ` Christoph Müllner
2024-02-15 11:54 ` Daniel Henrique Barboza
2024-02-26 1:31 ` Alistair Francis
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=20240207122256.902627-1-christoph.muellner@vrull.eu \
--to=christoph.muellner@vrull.eu \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).