From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
mingo@kernel.org, jiangshanlai@gmail.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org,
valentin.schneider@arm.com
Subject: [PATCH rcu/urgent 0/2] Adjust for updated scheduler CPU-affinity semantics
Date: Wed, 14 Jul 2021 13:49:28 -0700 [thread overview]
Message-ID: <20210714204928.GA2033276@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello!
This series converts smp_processor_id() calls to raw_smp_processor_id()
calls in kthreads that are intended to be bound to a single CPU, but
which are subject to human rebinding. While in the area, it warns if
set_cpus_allowed_ptr() returns failure. The patches are as follows:
1. Avoid false-positive warnings in scftorture_invoker().
2. Avoid false-positive warnings in ref_scale_reader().
Thanx, Paul
------------------------------------------------------------------------
rcu/refscale.c | 6 +++---
scftorture.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2021-07-14 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 20:49 Paul E. McKenney [this message]
2021-07-14 20:50 ` [PATCH rcu/urgent 1/2] scftorture: Avoid false-positive warnings in scftorture_invoker() Paul E. McKenney
2021-07-14 20:50 ` [PATCH rcu/urgent 2/2] refscale: Avoid false-positive warnings in ref_scale_reader() 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=20210714204928.GA2033276@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
/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).