qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	alistair.francis@wdc.com, bmeng@tinylab.org,
	liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com
Subject: Re: [PATCH v2 00/11] enable write_misa() and RISCV_FEATURE_* cleanups
Date: Wed, 15 Feb 2023 14:45:41 +0100	[thread overview]
Message-ID: <20230215134541.hxaspacyttcytod5@orel> (raw)
In-Reply-To: <20230214192356.319991-1-dbarboza@ventanamicro.com>

On Tue, Feb 14, 2023 at 04:23:45PM -0300, Daniel Henrique Barboza wrote:
> Hi,
> 
> This new version contains suggestions made by Weiwei Li in v1. Most
> notable change is patch 4 from v1, moving up to patch 2 now,  to allow
> the riscv_cpu_cfg() helper to be used in the MISA CSR patch.
> 
> 
> Changes in v2:
> - former patch 4 moved to patch 2
> - patch 3 (former 2):
>   - use riscv_cpu_cfg()
> - patch 9:
>   - remove the uneeded RISCVCPUConfig and access mmu via
>     cpu_cfg->cfg.mmu
> - v1 link: https://lists.gnu.org/archive/html/qemu-devel/2023-02/msg02780.html
> 
> Daniel Henrique Barboza (11):
>   target/riscv: do not mask unsupported QEMU extensions in write_misa()
>   target/riscv: introduce riscv_cpu_cfg()
>   target/riscv: allow users to actually write the MISA CSR
>   target/riscv: remove RISCV_FEATURE_MISA
>   target/riscv: remove RISCV_FEATURE_DEBUG
>   target/riscv/cpu.c: error out if EPMP is enabled without PMP
>   target/riscv: remove RISCV_FEATURE_EPMP
>   target/riscv: remove RISCV_FEATURE_PMP
>   hw/riscv/virt.c: do not use RISCV_FEATURE_MMU in
>     create_fdt_socket_cpus()
>   target/riscv: remove RISCV_FEATURE_MMU
>   target/riscv/cpu: remove CPUArchState::features and friends
> 
>  hw/riscv/virt.c           |  7 ++++---
>  target/riscv/cpu.c        | 20 +++++---------------
>  target/riscv/cpu.h        | 29 ++++++-----------------------
>  target/riscv/cpu_helper.c |  6 +++---
>  target/riscv/csr.c        | 15 ++++++---------
>  target/riscv/machine.c    | 11 ++++-------
>  target/riscv/monitor.c    |  2 +-
>  target/riscv/op_helper.c  |  2 +-
>  target/riscv/pmp.c        |  8 ++++----
>  9 files changed, 34 insertions(+), 66 deletions(-)
> 
> -- 
> 2.39.1
> 
>

For the series

Reviewed-by: Andrew Jones <ajones@ventanamicro.com>


      parent reply	other threads:[~2023-02-15 13:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 19:23 [PATCH v2 00/11] enable write_misa() and RISCV_FEATURE_* cleanups Daniel Henrique Barboza
2023-02-14 19:23 ` [PATCH v2 01/11] target/riscv: do not mask unsupported QEMU extensions in write_misa() Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 02/11] target/riscv: introduce riscv_cpu_cfg() Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 03/11] target/riscv: allow users to actually write the MISA CSR Daniel Henrique Barboza
2023-02-15  8:45   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 04/11] target/riscv: remove RISCV_FEATURE_MISA Daniel Henrique Barboza
2023-02-14 19:23 ` [PATCH v2 05/11] target/riscv: remove RISCV_FEATURE_DEBUG Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 06/11] target/riscv/cpu.c: error out if EPMP is enabled without PMP Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 07/11] target/riscv: remove RISCV_FEATURE_EPMP Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 08/11] target/riscv: remove RISCV_FEATURE_PMP Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 09/11] hw/riscv/virt.c: do not use RISCV_FEATURE_MMU in create_fdt_socket_cpus() Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 10/11] target/riscv: remove RISCV_FEATURE_MMU Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-14 19:23 ` [PATCH v2 11/11] target/riscv/cpu: remove CPUArchState::features and friends Daniel Henrique Barboza
2023-02-15 11:22   ` Bin Meng
2023-02-15 13:45 ` Andrew Jones [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=20230215134541.hxaspacyttcytod5@orel \
    --to=ajones@ventanamicro.com \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng@tinylab.org \
    --cc=dbarboza@ventanamicro.com \
    --cc=liweiwei@iscas.ac.cn \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --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).