From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Huang Pei <huangpei@loongson.cn>, Huacai Chen <chenhuacai@loongson.cn>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] LoongArch: Add RSEQ_SIG break code definition
Date: Thu, 26 Oct 2023 14:07:28 -0400 [thread overview]
Message-ID: <0e0cbc68-2b4c-462d-aff4-abd795b3b63d@efficios.com> (raw)
In-Reply-To: <20231026114446.5932-2-huangpei@loongson.cn>
On 2023-10-26 07:44, Huang Pei wrote:
> Signed-off-by: Huang Pei <huangpei@loongson.cn>
> ---
> arch/loongarch/include/uapi/asm/break.h | 2 ++
Why is this part of the uapi ? None of the other architecture has this
as part of uapi. It's only defined in the rseq selftest arch-specific
header file.
Thanks,
Mathieu
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/loongarch/include/uapi/asm/break.h b/arch/loongarch/include/uapi/asm/break.h
> index bb9b82ba59f2..e0fcfc304834 100644
> --- a/arch/loongarch/include/uapi/asm/break.h
> +++ b/arch/loongarch/include/uapi/asm/break.h
> @@ -20,4 +20,6 @@
> #define BRK_UPROBE_BP 12 /* See <asm/uprobes.h> */
> #define BRK_UPROBE_XOLBP 13 /* See <asm/uprobes.h> */
>
> +#define BRK_RSEQ_SIG 16 /* See rseq */
> +
> #endif /* __UAPI_ASM_BREAK_H */
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-10-26 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:44 [PATCH 1/3] selftests/rseq: Add 64bit LoongArch support Huang Pei
2023-10-26 11:44 ` [PATCH 2/3] LoongArch: Add RSEQ_SIG break code definition Huang Pei
2023-10-26 18:07 ` Mathieu Desnoyers [this message]
2023-10-27 1:40 ` Huacai Chen
2023-10-26 12:07 ` [PATCH 1/3] selftests/rseq: Add 64bit LoongArch support Huacai Chen
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=0e0cbc68-2b4c-462d-aff4-abd795b3b63d@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=chenhuacai@loongson.cn \
--cc=huangpei@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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
all inboxes | Powered by JetHome®