From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Guo Ren <guoren@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>
Subject: Re: [RFC PATCH 2/2] Revert "csky: Add support for restartable sequence"
Date: Sat, 10 Sep 2022 09:35:51 -0400 [thread overview]
Message-ID: <32422d2a-993e-c351-5f0e-788e28b09335@efficios.com> (raw)
In-Reply-To: <CAJF2gTRbn-JiUMiX_s52geJSiTs7qYV3oEkW1+NC8Vwp1YAKvg@mail.gmail.com>
On 2022-09-09 22:35, Guo Ren wrote:
> On Sat, Sep 10, 2022 at 4:01 AM Mathieu Desnoyers
[
>> A friendly ping after 1.5 year about the fact that the selftests code is
>> still missing for the csky architecture. So there is no way to validate
>> that the kernel pieces that were merged actually work on that architecture.
>>
>> What is the timeline for contribution of the missing bits needed to enable
>> those tests ?
> I would send the 1st version of patchset before 2022/10/30, or just
> revert it from csky.
OK. I can help by answering questions or with code review. I'm not
fluent in csky assembly, but I'll try to learn as I go.
>
> 1. a patch for fixup the bug:
> diff --git a/arch/csky/kernel/signal.c b/arch/csky/kernel/signal.c
> index b7b3685283d7..434dcf2e8e37 100644
> --- a/arch/csky/kernel/signal.c
> +++ b/arch/csky/kernel/signal.c
> @@ -179,8 +179,6 @@ static void handle_signal(struct ksignal *ksig,
> struct pt_regs *regs)
> sigset_t *oldset = sigmask_to_save();
> int ret;
>
> - rseq_signal_deliver(ksig, regs);
> -
> /* Are we from a system call? */
> if (in_syscall(regs)) {
> /* Avoid additional syscall restarting via ret_from_exception */
> @@ -206,6 +204,8 @@ static void handle_signal(struct ksignal *ksig,
> struct pt_regs *regs)
> }
> }
>
> + rseq_signal_deliver(ksig, regs);
> +
> /* Set up the stack frame */
> ret = setup_rt_frame(ksig, oldset, regs);
Yes, this fix is really needed.
>
> 2. Add tools/testing/selftests/rseq/rseq-csky* codes.
It looks like a good plan,
Thanks,
Mathieu
>
>
>
>>
>> Here are the required header files:
>>
>> tools/testing/selftests/rseq/rseq-csky.h
>> tools/testing/selftests/rseq/rseq-csky-thread-pointer.h (only if __builtin_thread_pointer is not implemented by gcc)
>>
>> I'm open to suggestions from other rseq co-maintainers on how to best address
>> this situation.
>>
>> Thanks,
>>
>> Mathieu
>>
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
>> https://www.efficios.com
>
>
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2022-09-10 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 16:15 [RFC PATCH 1/2] Revert "csky: Fixup CONFIG_DEBUG_RSEQ" Mathieu Desnoyers
2021-07-23 16:16 ` [RFC PATCH 2/2] Revert "csky: Add support for restartable sequence" Mathieu Desnoyers
2021-07-26 16:10 ` Guo Ren
2021-07-26 16:28 ` Mathieu Desnoyers
2022-09-09 20:02 ` Mathieu Desnoyers
2022-09-10 2:35 ` Guo Ren
2022-09-10 13:35 ` Mathieu Desnoyers [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=32422d2a-993e-c351-5f0e-788e28b09335@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=boqun.feng@gmail.com \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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®