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,
paul.gortmaker@windriver.com
Subject: [PATCH tip/core/rcu 0/9] Add bitmap (thus CPU) ranges
Date: Wed, 3 Mar 2021 15:55:26 -0800 [thread overview]
Message-ID: <20210303235526.GA21868@paulmck-ThinkPad-P72> (raw)
Hello!
This series adds ranges to bitmaps, and thus to CPU numbers, so that a
kernel boot parameter such as "rcu_nocbs=2-N" is now permitted.
1. test_bitmap: clearly separate ERANGE from EINVAL tests, courtesy
of Paul Gortmaker.
2. test_bitmap: add tests to trigger ERANGE case, courtesy of
Paul Gortmaker.
3. test_bitmap: add more start-end:offset/len tests, courtesy of
Paul Gortmaker.
4. bitmap: fold nbits into region struct, courtesy of Paul Gortmaker.
5. bitmap: move ERANGE check from set_region to check_region,
courtesy of Paul Gortmaker.
6. bitmap: support "N" as an alias for size of bitmap, courtesy of
Paul Gortmaker.
7. test_bitmap: add tests for "N" alias, courtesy of Paul Gortmaker.
8. deprecate "all" option to rcu_nocbs=, courtesy of Paul Gortmaker.
9. Use "all" and "N" in "nohz_full" and "rcu_nocbs".
Thanx, Paul
------------------------------------------------------------------------
Documentation/admin-guide/kernel-parameters.rst | 7 +
Documentation/admin-guide/kernel-parameters.txt | 4
kernel/rcu/tree_plugin.h | 6 -
lib/bitmap.c | 55 +++++++------
lib/test_bitmap.c | 46 +++++++++-
tools/testing/selftests/rcutorture/configs/rcu/TREE04.boot | 2
tools/testing/selftests/rcutorture/configs/rcu/TREE08.boot | 2
7 files changed, 84 insertions(+), 38 deletions(-)
next reply other threads:[~2021-03-04 0:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 23:55 Paul E. McKenney [this message]
2021-03-03 23:56 ` [PATCH lib/bitmap 1/9] lib: test_bitmap: clearly separate ERANGE from EINVAL tests paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 2/9] lib: test_bitmap: add tests to trigger ERANGE case paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 3/9] lib: test_bitmap: add more start-end:offset/len tests paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 4/9] lib: bitmap: fold nbits into region struct paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 5/9] lib: bitmap: move ERANGE check from set_region to check_region paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 6/9] lib: bitmap: support "N" as an alias for size of bitmap paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 7/9] lib: test_bitmap: add tests for "N" alias paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 8/9] rcu: deprecate "all" option to rcu_nocbs= paulmck
2021-03-03 23:56 ` [PATCH lib/bitmap 9/9] rcutorture: Use "all" and "N" in "nohz_full" and "rcu_nocbs" paulmck
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=20210303235526.GA21868@paulmck-ThinkPad-P72 \
--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=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®