All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.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,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/3] CPU hotplug changes for 4.9
Date: Mon, 22 Aug 2016 08:38:25 -0700	[thread overview]
Message-ID: <20160822153825.GA9242@linux.vnet.ibm.com> (raw)

Hello!

This series contains a few CPU-hotplug updates:

1.	Provide exact tracking of incoming CPUs, which means that there
	is now a definite point in the CPU-hotplug code at which RCU
	starts paying attention to incoming CPUs.

2.	Get rid of obsolete CPU_STARTING reference, courtesy of Sebastian
	Andrzej Siewior.

3.	Convert rcutorture's CPU-hotplug handling to use the shiny new
	state machine, courtesy of Sebastian Andrzej Siewior.

							Thanx, Paul

------------------------------------------------------------------------

 include/linux/rcupdate.h |    1 
 kernel/cpu.c             |    3 +-
 kernel/rcu/rcutorture.c  |   52 ++++++++++++-----------------------------------
 kernel/rcu/tree.c        |   32 ++++++++++++++++++++++++++--
 4 files changed, 46 insertions(+), 42 deletions(-)

             reply	other threads:[~2016-08-22 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 15:38 Paul E. McKenney [this message]
2016-08-22 15:38 ` [PATCH tip/core/rcu 1/3] rcu: Exact CPU-online tracking for RCU Paul E. McKenney
2016-08-22 15:38 ` [PATCH tip/core/rcu 2/3] cpu/hotplug: Get rid of CPU_STARTING reference Paul E. McKenney
2016-08-22 15:38 ` [PATCH tip/core/rcu 3/3] rcutorture: Convert to hotplug state machine 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=20160822153825.GA9242@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.