From: Richard Henderson <richard.henderson@linaro.org>
To: Jim Wilson <jimw@sifive.com>,
Georg Kotheimer <georg.kotheimer@kernkonzept.com>,
qemu-devel@nongnu.org
Cc: Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
qemu-riscv@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] RISC-V: Select FPU gdb xml file based on the supported extensions
Date: Tue, 20 Aug 2019 13:21:59 -0700 [thread overview]
Message-ID: <cb6758b2-966f-2584-81db-8e4d499eabec@linaro.org> (raw)
In-Reply-To: <79a82be5-38a2-edeb-66a6-25d34246aea3@sifive.com>
On 8/20/19 1:06 PM, Jim Wilson wrote:
> I don't see a need to remove the fp csr's from the csr list. There are other
> extension dependent CSRs, like hypervisor ones. I think it makes more sense for
> the csr list to contain all of the csrs, and then disable access to them if
> that extension is not enabled. If there is a good reason to require changes to
> the csr XML files, then it probably should be discussed with the gdb developers
> too, so that the gdb and qemu copies of the files remain consistent.
Another possibility is to generate the list of csr's at runtime and export that
to the connecting gdb.
We do this in target/arm/gdbstub.c, arm_gen_dynamic_xml.
r~
next prev parent reply other threads:[~2019-08-20 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 14:39 [Qemu-devel] [PATCH v2] RISC-V: Select FPU gdb xml file based on the supported extensions Georg Kotheimer
2019-08-20 20:06 ` Jim Wilson
2019-08-20 20:21 ` Richard Henderson [this message]
2019-08-21 16:26 ` Georg Kotheimer
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=cb6758b2-966f-2584-81db-8e4d499eabec@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=georg.kotheimer@kernkonzept.com \
--cc=jimw@sifive.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).