From: Georg Kotheimer <georg.kotheimer@kernkonzept.com>
To: Jim Wilson <jimw@sifive.com>, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, Palmer Dabbelt <palmer@sifive.com>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [Qemu-devel] [PATCH v2] RISC-V: Select FPU gdb xml file based on the supported extensions
Date: Wed, 21 Aug 2019 18:26:55 +0200 [thread overview]
Message-ID: <2129929.Dvzsi9MTMp@tweek> (raw)
In-Reply-To: <79a82be5-38a2-edeb-66a6-25d34246aea3@sifive.com>
On Tuesday, 20 August 2019 22:06:51 CEST Jim Wilson wrote:
> The current XML files were identical to the XML files in gdb when
> implemented. This seems to be existing practice, as this is true of all
> of the other targets I looked at when I implemented this. Also, the
> file names are the same with a / replaced with a -. These files are in
> the gdb/features/riscv dir in a gdb source tree. It would be a shame to
> break this. I'm not sure if they are still identical. The gdb copies
> might have been updated since then, and may need to be copied into qemu
> to update qemu, but we don't have a dedicated gdb/qemu maintainer to do
> this.
>
> 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.
>
> Fixing the rvf/rvd 32/64-bit support is good. That is a bug in my
> original implementation.
>
> Jim
My motivation behind renaming the xml files was to work against the
misconception that e.g. 64bit-cpu and 64bit-fpu are related to one another.
But of course, 32bit-fpu and 64bit-fpu is technically not incorrect.
Regarding the removal of the fp csrs from the csr list: I found it confusing
that the fp csr registers were listed in two files. In addition the bitsize of
the fp csr registers was stated as 64 in riscv-64bit-csr.xml, wheras the other
xml files (32bit-csr, 32bit-fpu and 64bit-fpu) stated 32, in accordance with
the RISC-V ISA specification.
Then I had a look at the gdb source code, and came to the conclusion that gdb
does not use the fp csr registers from the org.gnu.gdb.riscv.csr feaure set,
but instead the ones from org.gnu.gdb.riscv.fpu. Therefore, I decided to
remove the fp csr registers from the csr list.
However, as I don't have any prior experience with QEMU or gdb development is
quite likely that I misinterpreted or overlooked something.
For now I prepared a third version of the patch that only fixes the rvf/rvd
32/64-bit support.
Georg
prev parent reply other threads:[~2019-08-21 16:51 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
2019-08-21 16:26 ` Georg Kotheimer [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=2129929.Dvzsi9MTMp@tweek \
--to=georg.kotheimer@kernkonzept.com \
--cc=alistair.francis@wdc.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).