From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Andy Chiu <andy.chiu@sifive.com>
Cc: greentime.hu@sifive.com,
20230816155450.26200-4-andy.chiu@sifive.com, bjorn@kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Oleg Nesterov <oleg@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Vincent Chen <vincent.chen@sifive.com>,
Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor.dooley@microchip.com>,
Benjamin Gray <bgray@linux.ibm.com>,
Qing Zhang <zhangqing@loongson.cn>,
Baruch Siach <baruch@tkos.co.il>, Rolf Eike Beer <eb@emlix.com>,
Guo Ren <guoren@kernel.org>
Subject: Re: [v2] RISC-V: Add ptrace support for vectors
Date: Thu, 31 Aug 2023 14:58:26 -0700 [thread overview]
Message-ID: <169351910646.23657.443642645929304308.b4-ty@rivosinc.com> (raw)
In-Reply-To: <20230825050248.32681-1-andy.chiu@sifive.com>
On Fri, 25 Aug 2023 05:02:46 +0000, Andy Chiu wrote:
> This patch add back the ptrace support with the following fix:
> - Define NT_RISCV_CSR and re-number NT_RISCV_VECTOR to prevent
> conflicting with gdb's NT_RISCV_CSR.
> - Use struct __riscv_v_regset_state to handle ptrace requests
>
> Since gdb does not directly include the note description header in
> Linux and has already defined NT_RISCV_CSR as 0x900, we decide to
> sync with gdb and renumber NT_RISCV_VECTOR to solve and prevent future
> conflicts.
>
> [...]
Applied, thanks!
[1/1] RISC-V: Add ptrace support for vectors
https://git.kernel.org/palmer/c/1e4e7c306d52
Best regards,
--
Palmer Dabbelt <palmer@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-08-31 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 5:02 [v2] RISC-V: Add ptrace support for vectors Andy Chiu
2023-08-30 20:30 ` patchwork-bot+linux-riscv
2023-08-31 17:05 ` Nick Desaulniers
2023-08-31 17:17 ` Conor Dooley
2023-08-31 17:50 ` Thorsten Leemhuis
2023-08-31 17:59 ` Nick Desaulniers
2023-08-31 18:24 ` Thorsten Leemhuis
2023-09-05 13:22 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-31 21:58 ` Palmer Dabbelt [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=169351910646.23657.443642645929304308.b4-ty@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=20230816155450.26200-4-andy.chiu@sifive.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=baruch@tkos.co.il \
--cc=bgray@linux.ibm.com \
--cc=bjorn@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=eb@emlix.com \
--cc=ebiederm@xmission.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=keescook@chromium.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.com \
--cc=zhangqing@loongson.cn \
/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).