qemu-riscv.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tommy Wu <tommy.wu@sifive.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: frank.chang@sifive.com, alistair.francis@wdc.com,
	apatel@ventanamicro.com, palmer@rivosinc.com,
	dbarboza@ventanamicro.com, bin.meng@windriver.com,
	liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com,
	Tommy Wu <tommy.wu@sifive.com>
Subject: [PATCH 0/2] Refresh the dynamic CSR xml after updating the state of the cpu.
Date: Tue, 23 May 2023 04:44:52 -0700	[thread overview]
Message-ID: <20230523114454.717708-1-tommy.wu@sifive.com> (raw)

The realize function of IMSIC will force select AIA feature and setup CSRs,
but the dynamic CSR xml is not updated, so we cannot print the AIA CSRs
in the remote gdb debugger.

In the patches, we provide a function to refresh the dynamic CSR xml,
and refresh the xml in the realize function of IMSIC.

Tommy Wu (2):
  target/riscv: Add a function to refresh the dynamic CSRs xml.
  hw/intc: riscv_imsic: Refresh the CSRs xml after updating the state of
    the cpu.

 hw/intc/riscv_imsic.c  |  4 ++++
 target/riscv/cpu.h     |  2 ++
 target/riscv/gdbstub.c | 12 ++++++++++++
 3 files changed, 18 insertions(+)

-- 
2.38.1



             reply	other threads:[~2023-05-23 11:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 11:44 Tommy Wu [this message]
2023-05-23 11:44 ` [PATCH 1/2] target/riscv: Add a function to refresh the dynamic CSRs xml Tommy Wu
2023-05-23 14:37   ` Weiwei Li
2023-05-24  1:59     ` Tommy Wu
2023-05-24  2:10       ` Weiwei Li
2023-05-24  5:35         ` Tommy Wu
2023-05-24  6:18           ` Weiwei Li
2023-05-25  2:33   ` Alistair Francis
2023-06-09  8:37     ` Tommy Wu
2023-06-12  2:52       ` Alistair Francis
2023-05-23 11:44 ` [PATCH 2/2] hw/intc: riscv_imsic: Refresh the CSRs xml after updating the state of the cpu Tommy Wu
2023-05-23 14:43   ` Weiwei Li
2023-05-24  1:51     ` Tommy Wu
2023-05-24  2:34       ` Weiwei Li
2023-05-24  5:46         ` Tommy Wu

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=20230523114454.717708-1-tommy.wu@sifive.com \
    --to=tommy.wu@sifive.com \
    --cc=alistair.francis@wdc.com \
    --cc=apatel@ventanamicro.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=frank.chang@sifive.com \
    --cc=liweiwei@iscas.ac.cn \
    --cc=palmer@rivosinc.com \
    --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).