mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: paulmck@kernel.org, josh@joshtriplett.org
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	peterz@infradead.org, bigeasy@linutronix.de, tglx@linutronix.de,
	rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	jiangshanlai@gmail.com, joel@joelfernandes.org,
	rcu@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>
Subject: [PATCH v2 0/2] rcu: Make rcu_normal_after_boot writable again
Date: Tue, 10 Aug 2021 10:48:14 +0200	[thread overview]
Message-ID: <20210810084816.155203-1-juri.lelli@redhat.com> (raw)

Hi,

v2 of a proposed RCU change to make rcu_normal_after_boot feature usable
on PREEMPT_RT as well, as it turns out it's useful on RT as well on
NO_HZ_FULL configurations.

v2 gained an additional patch to revise rcu update module parameters
permissions (as suggested during v1 review [1]).

Changes wrt v1:

 - Restrict the option to !PREEMPT_RT || NO_HZ_FULL (Paul, Sebastian)
 - Change module params permissions (Paul) (02/02)

Thanks,
Juri

v1 - https://lore.kernel.org/lkml/20210805080123.16320-1-juri.lelli@redhat.com/

Juri Lelli (2):
  rcu: Make rcu_normal_after_boot writable again
  rcu: Make rcu update module parameters world-readable

 kernel/rcu/tree_exp.h | 1 -
 kernel/rcu/update.c   | 8 ++++----
 2 files changed, 4 insertions(+), 5 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-08-10  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  8:48 Juri Lelli [this message]
2021-08-10  8:48 ` [PATCH v2 1/2] " Juri Lelli
2021-08-10  8:48 ` [PATCH v2 2/2] rcu: Make rcu update module parameters world-readable Juri Lelli
2021-08-10 18:41 ` [PATCH v2 0/2] rcu: Make rcu_normal_after_boot writable again 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=20210810084816.155203-1-juri.lelli@redhat.com \
    --to=juri.lelli@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --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®