From: baturo.alexey@gmail.com
Cc: baturo.alexey@gmail.com, richard.henderson@linaro.org,
zhiwei_liu@linux.alibaba.com, dbarboza@ventanamicro.com,
liwei1518@gmail.com, alistair23@gmail.com,
frank.chang@sifive.com, palmer@dabbelt.com,
Alistair.Francis@wdc.com, sagark@eecs.berkeley.edu,
kbastian@mail.uni-paderborn.de, qemu-devel@nongnu.org,
qemu-riscv@nongnu.org
Subject: [PATCH 0/7] Pointer Masking update for Zjpm v1.0
Date: Fri, 8 Nov 2024 09:01:09 +0300 [thread overview]
Message-ID: <20241108060116.37397-1-baturo.alexey@gmail.com> (raw)
From: Alexey Baturo <baturo.alexey@gmail.com>
Hi,
As Pointer Masking is finally ratified, these patches intend to update the existing code to the final version.
These patches have been submitted previously and I tried to address all the suggestions, but I'd suggest to review them from the clean slate and then finally push them to the repo.
Thanks.
Alexey Baturo (7):
target/riscv: Remove obsolete pointer masking extension code.
target/riscv: Add new CSR fields for S{sn,mn,m}pm extensions as part
of Zjpm v1.0
target/riscv: Add helper functions to calculate current number of
masked bits for pointer masking
target/riscv: Add pointer masking tb flags
target/riscv: Update address modify functions to take into account
pointer masking
target/riscv: Apply pointer masking for virtualized memory accesses
target/riscv: Enable updates for pointer masking variables and thus
enable pointer masking extension
target/riscv/cpu.c | 19 +-
target/riscv/cpu.h | 51 ++--
target/riscv/cpu_bits.h | 91 +-----
target/riscv/cpu_cfg.h | 3 +
target/riscv/cpu_helper.c | 124 ++++++---
target/riscv/csr.c | 356 ++----------------------
target/riscv/insn_trans/trans_rvh.c.inc | 11 +
target/riscv/machine.c | 17 +-
target/riscv/pmp.c | 14 +-
target/riscv/pmp.h | 1 +
target/riscv/tcg/tcg-cpu.c | 5 +-
target/riscv/translate.c | 51 ++--
target/riscv/vector_helper.c | 18 +-
13 files changed, 224 insertions(+), 537 deletions(-)
--
2.39.5
next reply other threads:[~2024-11-08 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 6:01 baturo.alexey [this message]
2024-11-08 6:01 ` [PATCH 1/7] target/riscv: Remove obsolete pointer masking extension code baturo.alexey
2024-11-08 6:01 ` [PATCH 2/7] target/riscv: Add new CSR fields for S{sn, mn, m}pm extensions as part of Zjpm v1.0 baturo.alexey
2024-11-11 15:27 ` [PATCH 2/7] target/riscv: Add new CSR fields for S{sn,mn,m}pm " Richard Henderson
2024-11-08 6:01 ` [PATCH 3/7] target/riscv: Add helper functions to calculate current number of masked bits for pointer masking baturo.alexey
2024-11-08 6:01 ` [PATCH 4/7] target/riscv: Add pointer masking tb flags baturo.alexey
2024-11-08 6:01 ` [PATCH 5/7] target/riscv: Update address modify functions to take into account pointer masking baturo.alexey
2024-11-08 6:01 ` [PATCH 6/7] target/riscv: Apply pointer masking for virtualized memory accesses baturo.alexey
2024-11-08 6:01 ` [PATCH 7/7] target/riscv: Enable updates for pointer masking variables and thus enable pointer masking extension baturo.alexey
2024-11-11 17:14 ` Daniel Henrique Barboza
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=20241108060116.37397-1-baturo.alexey@gmail.com \
--to=baturo.alexey@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=frank.chang@sifive.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sagark@eecs.berkeley.edu \
--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 NNTP newsgroup(s).