From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: bigeasy@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Typical PREEMPT_RT .config?
Date: Tue, 5 Apr 2022 09:40:48 -0400 [thread overview]
Message-ID: <20220405094048.30a75670@gandalf.local.home> (raw)
In-Reply-To: <20220404231654.GA3445712@paulmck-ThinkPad-P17-Gen-1>
On Mon, 4 Apr 2022 16:16:54 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> OK, now that PREEMPT_RT is mostly into mainline, I should probably create
> an rcutorture scenario more closely reflecting it. The closest at the
> moment is probably tools/testing/selftests/rcutorture/configs/rcu/TREE03,
> but I figured that before beating on it I should check to see if you
> already have a PREEMPT_RT rcutorture scenario file.
I don't have one.
-- Steve
next prev parent reply other threads:[~2022-04-05 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 23:16 Typical PREEMPT_RT .config? Paul E. McKenney
2022-04-05 13:40 ` Steven Rostedt [this message]
2022-04-05 13:42 ` Steven Rostedt
2022-04-05 14:57 ` Paul E. McKenney
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=20220405094048.30a75670@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
/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).