linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Guo Ren <guoren@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>
Cc: 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: Fri, 9 Sep 2022 16:02:04 -0400	[thread overview]
Message-ID: <cbd08ae8-4558-60e3-17e4-988e625984a1@efficios.com> (raw)
In-Reply-To: <2070284546.6496.1627316900287.JavaMail.zimbra@efficios.com>

On 2021-07-26 12:28, Mathieu Desnoyers wrote:
> ----- On Jul 26, 2021, at 12:10 PM, Guo Ren guoren@kernel.org wrote:
> 
>> Hi Mathieu,
>>
>> Sorry for forgetting to CC you in the last patch, and that patch has
>> been merged into master which has the problem of syscall restart.
>>
>> I still want to keep rseq feature for csky, and implement the
>> RSEQ_SKIP_FASTPATH for self-test, it that okay?
> 
> No, the RSEQ_SKIP_FASTPATH is the one special-case of test build which
> skips building rseq critical sections entirely. This leaves out any
> relevant testing of rseq per-se. With what we have in the upstream
> selftests, I expect this test configuration to abort at runtime because
> no slow-path fallbacks are available when the fastpath is disabled.
> 
> The asm glue to test rseq user-space really needs to be implemented
> for any useful testing to be done here.
> 
> Unless that asm glue is contributed, none of the rseq logic is actually
> tested on that architecture.
> 
> Considering the extremely-hard-to-debug nature of races with a broken
> rseq kernel implementation, proper testing coverage is paramount, so I
> still recommend the revert unless the selftests user-space asm glue is
> contributed for C-Sky.

Hi Guo,

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 ?

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

  reply	other threads:[~2022-09-09 20:01 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 [this message]
2022-09-10  2:35         ` Guo Ren
2022-09-10 13:35           ` Mathieu Desnoyers

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=cbd08ae8-4558-60e3-17e4-988e625984a1@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;
as well as URLs for NNTP newsgroup(s).