From: Andreas Schwab <schwab@suse.de>
To: Yipeng Zou <zouyipeng@huawei.com>
Cc: <linux-riscv@lists.infradead.org>, <oleg@redhat.com>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <guoren@kernel.org>
Subject: Re: [PATCH -next 0/2] riscv: ptrace: implement PTRACE_{PEEK,POKE}USR
Date: Mon, 22 Aug 2022 10:19:03 +0200 [thread overview]
Message-ID: <mvmzgfwelmw.fsf@suse.de> (raw)
In-Reply-To: <20220822030105.16053-1-zouyipeng@huawei.com> (Yipeng Zou's message of "Mon, 22 Aug 2022 11:01:03 +0800")
On Aug 22 2022, Yipeng Zou wrote:
> The PTRACE_{PEEK,POKE}USR going to get/set tracee's user register.
> This patch sets add PTRACE_{PEEK,POKE}USR and compat implement to
> riscv.
>
> I notice this issuse when transplanting some app form x86 to riscv
> recently.
> I don't know why these two function are not implemented now, and I
> found few talk about that.
>
> The {PEEK,POKE}USR are both defined in include\uapi\linux\ptrace.h,
> So I was thinking maybe these two function shouled be implemented.
There are PTRACE_[GS]ETREGSET. I think PTRACE_{PEEK,POKE}USR are
legacy-only.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-08-22 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 3:01 [PATCH -next 0/2] riscv: ptrace: implement PTRACE_{PEEK,POKE}USR Yipeng Zou
2022-08-22 3:01 ` [PATCH -next 1/2] riscv: ptrace: Implement PTRACE_{PEEK,POKE}USR Yipeng Zou
2022-08-22 3:01 ` [PATCH -next 2/2] riscv: ptrace: Implement Compat PTRACE_{PEEK,POKE}USR Yipeng Zou
2022-08-22 8:19 ` Andreas Schwab [this message]
2022-10-06 1:26 ` [PATCH -next 0/2] riscv: ptrace: implement PTRACE_{PEEK,POKE}USR Palmer Dabbelt
2022-10-08 1:24 ` Yipeng Zou
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=mvmzgfwelmw.fsf@suse.de \
--to=schwab@suse.de \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zouyipeng@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.