From: Alistair Francis <alistair.francis@wdc.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: alistair23@gmail.com, palmer@sifive.com, alistair.francis@wdc.com
Subject: [Qemu-devel] [PATCH v3 0/7] RISC-V: Hypervisor prep work part 2
Date: Thu, 15 Aug 2019 14:34:45 -0700 [thread overview]
Message-ID: <cover.1565904855.git.alistair.francis@wdc.com> (raw)
The first three patches are ones that I have pulled out of my original
Hypervisor series at an attempt to reduce the number of patches in the
series.
These three patches all make sense without the Hypervisor series so can
be merged seperatley and will reduce the review burden of the next
version of the patches.
The fource patch is a prep patch for the new v0.4 Hypervisor spec.
The fifth patch is unreleated to Hypervisor that I'm just slipping in
here because it seems easier then sending it by itself.
The final two patches are issues I discovered while adding the v0.4
Hypervisor extension.
v3:
- Change names of all GP registers
- Add two more patches
v2:
- Small corrections based on feedback
- Remove the CSR permission check patch
Alistair Francis (6):
target/riscv: Don't set write permissions on dirty PTEs
riscv: plic: Remove unused interrupt functions
target/riscv: Create function to test if FP is enabled
target/riscv: Update the Hypervisor CSRs to v0.4
target/riscv: Fix mstatus dirty mask
target/riscv: Convert mip to target_ulong
Atish Patra (1):
target/riscv: Use both register name and ABI name
hw/riscv/sifive_plic.c | 12 ------------
include/hw/riscv/sifive_plic.h | 3 ---
target/riscv/cpu.c | 19 ++++++++++--------
target/riscv/cpu.h | 8 ++++++--
target/riscv/cpu_bits.h | 35 +++++++++++++++++-----------------
target/riscv/cpu_helper.c | 16 ++++++++++++----
target/riscv/csr.c | 22 +++++++++++----------
7 files changed, 59 insertions(+), 56 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-15 21:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 21:34 Alistair Francis [this message]
2019-08-15 21:34 ` [Qemu-devel] [PATCH v3 1/7] target/riscv: Don't set write permissions on dirty PTEs Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:34 ` [Qemu-devel] [PATCH v3 2/7] riscv: plic: Remove unused interrupt functions Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:34 ` [Qemu-devel] [PATCH v3 3/7] target/riscv: Create function to test if FP is enabled Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:34 ` [Qemu-devel] [PATCH v3 4/7] target/riscv: Update the Hypervisor CSRs to v0.4 Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:34 ` [Qemu-devel] [PATCH v3 5/7] target/riscv: Use both register name and ABI name Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:35 ` [Qemu-devel] [PATCH v3 6/7] target/riscv: Fix mstatus dirty mask Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-15 21:35 ` [Qemu-devel] [PATCH v3 7/7] target/riscv: Convert mip to target_ulong Alistair Francis
2019-08-16 13:59 ` Bin Meng
2019-08-23 15:18 ` Alistair Francis
2019-08-15 22:13 ` [Qemu-devel] [PATCH v3 0/7] RISC-V: Hypervisor prep work part 2 no-reply
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=cover.1565904855.git.alistair.francis@wdc.com \
--to=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.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 NNTP newsgroup(s).