qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Weiwei Li <liweiwei@iscas.ac.cn>
To: qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Cc: palmer@dabbelt.com, alistair.francis@wdc.com,
	bin.meng@windriver.com, dbarboza@ventanamicro.com,
	zhiwei_liu@linux.alibaba.com, wangjunqiang@iscas.ac.cn,
	lazyparser@gmail.com, Weiwei Li <liweiwei@iscas.ac.cn>
Subject: [PATCH 0/2] target/riscv: Fix mstatus.MPP related support
Date: Thu, 30 Mar 2023 21:58:16 +0800	[thread overview]
Message-ID: <20230330135818.68417-1-liweiwei@iscas.ac.cn> (raw)

This patchset tries to fix some problems in current implementation for mstatus.MPP.
- set to the least-privileged supported mode (U if U-mode is implemented, else M) after executing mret
- legalize mpp when write to mstatus

The port is available here:
https://github.com/plctlab/plct-qemu/tree/plct-mpp-fix

Weiwei Li (2):
  target/riscv: Fix the mstatus.MPP value after executing MRET
  target/riscv: Legalize MPP value in write_mstatus

 target/riscv/cpu_helper.c |  5 +----
 target/riscv/csr.c        | 14 ++++++++++++++
 target/riscv/op_helper.c  |  3 ++-
 3 files changed, 17 insertions(+), 5 deletions(-)

-- 
2.25.1



             reply	other threads:[~2023-03-30 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:58 Weiwei Li [this message]
2023-03-30 13:58 ` [PATCH 1/2] target/riscv: Fix the mstatus.MPP value after executing MRET Weiwei Li
2023-04-06  0:43   ` Alistair Francis
2023-04-06  0:56     ` liweiwei
2023-04-06  1:46       ` Alistair Francis
2023-04-06  2:14         ` liweiwei
2023-04-06  2:24           ` Alistair Francis
2023-04-06  2:39             ` liweiwei
2023-04-06  3:01             ` liweiwei
2023-04-06  3:55               ` Alistair Francis
2023-03-30 13:58 ` [PATCH 2/2] target/riscv: Legalize MPP value in write_mstatus Weiwei Li
2023-04-06  1:26   ` Alistair Francis
2023-04-06  1:35     ` liweiwei

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=20230330135818.68417-1-liweiwei@iscas.ac.cn \
    --to=liweiwei@iscas.ac.cn \
    --cc=alistair.francis@wdc.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=lazyparser@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=wangjunqiang@iscas.ac.cn \
    --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).