linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@wdc.com>
To: linux-riscv@lists.infradead.org
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	linux-kernel@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH 0/2] riscv: ptrace: NT_PRFPREG regset access fixes
Date: Fri, 24 Jul 2020 00:21:57 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2007232038170.24175@redsun52.ssa.fujisawa.hgst.com> (raw)

Hi,

 In the course of adding RISC-V/Linux support to `gdbserver' I examined 
our Linux regset code to make sure I get the userland side right and 
discovered a discrepancy between how our internal `user_regset_copyout' 
and `user_regset_copyout' API has been defined and how we call it in the 
RISC-V backend in the handling of the NT_PRFPREG regset.  Additionally I 
found that code violating our coding style.

 To address these issues I made this small patch set, addressing each of 
them separately.  See individual change descriptions for details.

 These changes are hopefully obviously correct, however to make sure I 
have verified them manually with a HiFive Unleashed board running 
`gdbserver' controlled remotely by GDB and also by running the full GDB 
testsuite in the same environment using the lp64d ABI, without and with 
the changes applied.

 Please apply.

  Maciej

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2020-07-23 23:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 23:21 Maciej W. Rozycki [this message]
2020-07-23 23:22 ` [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access Maciej W. Rozycki
2020-08-05  2:01   ` Palmer Dabbelt
2020-08-05  2:07     ` Al Viro
2020-08-05  2:20       ` Palmer Dabbelt
2020-08-05  2:48         ` Al Viro
2020-08-05  3:15           ` Palmer Dabbelt
2020-08-05 10:25           ` Maciej W. Rozycki
2020-08-05 19:48             ` Palmer Dabbelt
2020-08-19 20:00               ` Maciej W. Rozycki
2020-07-23 23:22 ` [PATCH 2/2] riscv: ptrace: Improve the style in NT_PRFPREG regset handling Maciej W. Rozycki
2020-08-05  2:01   ` Palmer Dabbelt

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=alpine.LFD.2.21.2007232038170.24175@redsun52.ssa.fujisawa.hgst.com \
    --to=macro@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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).