From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org, rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/3] Make rcutorture safe(r) for arm64
Date: Fri, 9 May 2025 13:57:06 -0400 [thread overview]
Message-ID: <45dc2f1e-112e-4973-909e-c65a387c35bf@nvidia.com> (raw)
In-Reply-To: <da86a280-f402-499f-a4ba-df626ca4c748@paulmck-laptop>
On 5/8/2025 7:42 PM, Paul E. McKenney wrote:
> Hello!
>
> This series makes a few small updates to make rcutorture run better
> on arm64 servers. Remaining issues include TREE07 .config issues
> that are addressed by Mark Rutland's porting of PREEMPT_LAZY to arm64
> and by upcoming work to handle the fact that arm64 kernels cannot be
> built with CONFIG_SMP=n. In the meantime, the CONFIG_SMP=n issue can
> be worked around by explictly specifying the TREE01, TREE02, TREE03,
> TREE04, TREE05, TREE07, SRCU-L, SRCU-N, SRCU-P, TASKS01, TASKS03, RUDE01,
> TRACE01, and TRACE02 scenarios, preferably in a script. (But if you
> want typing practice, don't let me stand in your way!)
>
> 1. Check for "Call trace:" as well as "Call Trace:".
>
> 2. Reduce TREE01 CPU overcommit.
>
> 3. Remove MAXSMP and CPUMASK_OFFSTACK from TREE01.
>
Tested-by: Joel Fernandes <joelagnelf@nvidia.com>
Applied for 6.16, thanks!
- Joel
prev parent reply other threads:[~2025-05-09 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 23:42 Paul E. McKenney
2025-05-08 23:42 ` [PATCH 1/3] torture: Check for "Call trace:" as well as "Call Trace:" Paul E. McKenney
2025-05-08 23:42 ` [PATCH 2/3] rcutorture: Reduce TREE01 CPU overcommit Paul E. McKenney
2025-05-08 23:42 ` [PATCH 3/3] rcutorture: Remove MAXSMP and CPUMASK_OFFSTACK from TREE01 Paul E. McKenney
2025-05-09 13:18 ` [PATCH 0/3] Make rcutorture safe(r) for arm64 Joel Fernandes
2025-05-09 14:32 ` Paul E. McKenney
2025-05-09 17:57 ` Joel Fernandes [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=45dc2f1e-112e-4973-909e-c65a387c35bf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®