public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: jiangshuai_li@c-sky.com, Maciej Rozycki <macro@wdc.com>
Cc: "Andrew Burgess" <andrew.burgess@embecosm.com>,
	guoren@kernel.org, gdb-patches@sourceware.org,
	夏立方 <lifang_xia@c-sky.com>, yunhai_shang <yunhai_shang@c-sky.com>
Subject: Re: [PATCH] riscv: add gdbserver support
Date: Mon, 20 Jan 2020 23:33:00 -0000	[thread overview]
Message-ID: <CAFyWVaa7ADP_SmBVoan9AOkWK9parEz5EENZZL5vY+_GcD9SrA@mail.gmail.com> (raw)
In-Reply-To: <00e401d5cb52$63a4d000$2aee7000$@c-sky.com>

On Tue, Jan 14, 2020 at 7:18 PM <jiangshuai_li@c-sky.com> wrote:
> This patch is a base support for Riscv32 and Riscv64  arch. It implemented
> how to
> r/w gprs and fprs, identify the software bkpt insns and the *.dat files for
> regs_info.
> I have tested it on kernel 5.1.15, and it works normally.

I believe that Maciej has a RISC-V gdbserver port also.  It would be
nice to see some comment from him.

> Some requirements may be implemented later:
> 1. if fpu has 64bits in riscv32

This is common, and will have to be fixed, but not necessarily fixed
in the first version.  We also have riscv32 linux targets with no FP
registers.  I don't know what the *.dat files are for, but I think the
general registers and the FP registers should be separate files if
possible.  If not, then we need 6 dat files, as we have 2 general reg
sizes and 3 FP reg sizes, and 2*3=6.

> 2. hardware bkpt/watchpoint support

As far as I know, the linux kernel can't set hardware breakpoints with
the current design of the RISC-V debug standard.  They can only be set
via jtag.  So I don't see this as a problem.

> 3. vector regitsers r/w

The vector registers are still in draft form, and are subject to
change.  I'd rather not add support for draft features upstream, as
then we are stuck supporting draft versions of the ISA forever.  Also,
we still don't have a proposal for DWARF register numbers for the
vector registers.

Jim

  reply	other threads:[~2020-01-20 23:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  5:01 jiangshuai_li
2020-01-20 23:33 ` Jim Wilson [this message]
2020-01-21  0:30   ` Maciej W. Rozycki
2020-01-21  2:13     ` Simon Marchi
2020-01-21  2:17       ` Maciej W. Rozycki
2020-01-21 13:01       ` Andrew Burgess
2020-01-21 13:28         ` Andrew Burgess
2020-01-21 13:47           ` Andreas Schwab
2020-01-22  0:11             ` Jim Wilson
2020-01-22  0:45           ` Jim Wilson
2020-01-22 10:19             ` Jim Wilson
2020-01-22 14:08               ` Andrew Burgess
2020-01-21 17:11         ` Maciej W. Rozycki
2020-01-21 23:56     ` Jim Wilson
2020-01-22  5:26   ` Guo Ren
2020-01-22  6:15     ` Jim Wilson

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=CAFyWVaa7ADP_SmBVoan9AOkWK9parEz5EENZZL5vY+_GcD9SrA@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guoren@kernel.org \
    --cc=jiangshuai_li@c-sky.com \
    --cc=lifang_xia@c-sky.com \
    --cc=macro@wdc.com \
    --cc=yunhai_shang@c-sky.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 read-only IMAP folder(s) and NNTP newsgroup(s).