All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: stern@rowland.harvard.edu, scottt@scottt.tw,
	gpiccoli@linux.vnet.ibm.com, neeraju@codeaurora.org,
	bigeasy@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL rcu/next] RCU commits for 4.15
Date: Mon, 23 Oct 2017 13:45:02 -0700	[thread overview]
Message-ID: <20171023204502.GA2776@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171023182045.GA1291@linux.vnet.ibm.com>

Hello, Ingo,

[ Resend, this time remembering to CC LKML. ]

This pull request contains the following changes:

1.	Documentation updates.

	lkml.kernel.org/r/20171004212051.GA8411@linux.vnet.ibm.com

	(But note that a number of these commits were redirected to
	v4.14 on the request of Randy Dunlap and Jon Corbet.)

2.	Miscellaneous fixes.

	lkml.kernel.org/r/20171004212915.GA10089@linux.vnet.ibm.com

3.	RCU CPU stall-warning updates.

	lkml.kernel.org/r/20171004215006.GA12792@linux.vnet.ibm.com

4.	Torture-test updates.

	lkml.kernel.org/r/20171004215609.GA14782@linux.vnet.ibm.com

All of these commits have been exposed to 0day Test Robot and -next
testing, and are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo

for you to fetch changes up to ad4e25a3a1a5a95b334242d908e26f1249db83e0:

  Merge branches 'doc.2017.10.20a', 'fixes.2017.10.19a', 'stall.2017.10.09a' and 'torture.2017.10.09a' into HEAD (2017-10-20 11:11:15 -0700)

----------------------------------------------------------------
Alan Stern (1):
      memory-barriers: Rework multicopy-atomicity section

Guilherme G. Piccoli (1):
      doc: Rewrite confusing statement about memory barriers

Neeraj Upadhyay (1):
      rcu: Fix up pending cbs check in rcu_prepare_for_idle

Paul E. McKenney (19):
      documentation: RCU grace-period memory ordering guarantees
      documentation: Long-running irq handlers can stall RCU grace periods
      documentation: Slow systems can stall RCU grace periods
      documentation: Update RCU CPU stall warning messages
      memory-barriers: Replace uses of "transitive"
      rcu: Create call_rcu_tasks() kthread at boot time
      irq_work: Map irq_work_on_queue() to irq_work_on() in !SMP
      sched: Make resched_cpu() unconditional
      sched,rcu: Make cond_resched() provide RCU quiescent state
      rcu: Make RCU CPU stall warnings check for irq-disabled CPUs
      rcu: Turn off tracing before dumping trace
      rcu: Suppress RCU CPU stall warnings while dumping trace
      rcutorture: Add interrupt-disable capability to stall-warning tests
      rcutorture: Dump writer stack if stalled
      torture: Provide TMPDIR environment variable to specify tmpdir
      rcu: Suppress lockdep false-positive ->boost_mtx complaints
      rcu: Add extended-quiescent-state testing advice
      srcu: Add parameters to SRCU docbook comments
      Merge branches 'doc.2017.10.20a', 'fixes.2017.10.19a', 'stall.2017.10.09a' and 'torture.2017.10.09a' into HEAD

Scott Tsai (1):
      memory-barriers.txt: Fix typo in pairing example

Sebastian Andrzej Siewior (2):
      rcu: Do not include rtmutex_common.h unconditionally
      rcu/segcblist: Include rcupdate.h

 .../Design/Memory-Ordering/Tree-RCU-Diagram.html   |    9 +
 .../Memory-Ordering/Tree-RCU-Memory-Ordering.html  |  707 +++
 .../TreeRCU-callback-invocation.svg                |  486 ++
 .../Memory-Ordering/TreeRCU-callback-registry.svg  |  655 +++
 .../RCU/Design/Memory-Ordering/TreeRCU-dyntick.svg |  700 +++
 .../Design/Memory-Ordering/TreeRCU-gp-cleanup.svg  | 1126 +++++
 .../RCU/Design/Memory-Ordering/TreeRCU-gp-fqs.svg  | 1309 +++++
 .../Design/Memory-Ordering/TreeRCU-gp-init-1.svg   |  656 +++
 .../Design/Memory-Ordering/TreeRCU-gp-init-2.svg   |  656 +++
 .../Design/Memory-Ordering/TreeRCU-gp-init-3.svg   |  632 +++
 .../RCU/Design/Memory-Ordering/TreeRCU-gp.svg      | 5135 ++++++++++++++++++++
 .../RCU/Design/Memory-Ordering/TreeRCU-hotplug.svg |  775 +++
 .../RCU/Design/Memory-Ordering/TreeRCU-qs.svg      | 1095 +++++
 .../RCU/Design/Memory-Ordering/rcu_node-lock.svg   |  229 +
 Documentation/RCU/stallwarn.txt                    |  200 +-
 Documentation/admin-guide/kernel-parameters.txt    |    3 +
 Documentation/memory-barriers.txt                  |  197 +-
 include/linux/irq_work.h                           |    3 -
 include/linux/srcu.h                               |    1 +
 kernel/irq_work.c                                  |    9 +-
 kernel/rcu/rcu.h                                   |   21 +-
 kernel/rcu/rcu_segcblist.c                         |    1 +
 kernel/rcu/rcutorture.c                            |   24 +-
 kernel/rcu/srcutree.c                              |    2 +-
 kernel/rcu/tree.c                                  |  159 +-
 kernel/rcu/tree.h                                  |    5 +
 kernel/rcu/tree_plugin.h                           |   14 +-
 kernel/rcu/update.c                                |   25 +-
 kernel/sched/core.c                                |    5 +-
 .../selftests/rcutorture/bin/config_override.sh    |    2 +-
 .../selftests/rcutorture/bin/configcheck.sh        |    2 +-
 .../testing/selftests/rcutorture/bin/configinit.sh |    2 +-
 .../testing/selftests/rcutorture/bin/kvm-build.sh  |    2 +-
 .../selftests/rcutorture/bin/kvm-test-1-run.sh     |    2 +-
 tools/testing/selftests/rcutorture/bin/kvm.sh      |    4 +-
 .../selftests/rcutorture/bin/parse-build.sh        |    2 +-
 .../selftests/rcutorture/bin/parse-torture.sh      |    2 +-
 37 files changed, 14600 insertions(+), 257 deletions(-)
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Diagram.html
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-invocation.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-registry.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-dyntick.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-cleanup.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-fqs.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-1.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-2.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-3.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-hotplug.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg
 create mode 100644 Documentation/RCU/Design/Memory-Ordering/rcu_node-lock.svg

       reply	other threads:[~2017-10-23 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171023182045.GA1291@linux.vnet.ibm.com>
2017-10-23 20:45 ` Paul E. McKenney [this message]
2017-10-24  8:51   ` [GIT PULL rcu/next] RCU commits for 4.15 Ingo Molnar
2018-01-02 19:10 Paul E. McKenney
2018-01-03 13:17 ` Ingo Molnar
2018-01-03 17:38   ` 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=20171023204502.GA2776@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=gpiccoli@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=neeraju@codeaurora.org \
    --cc=scottt@scottt.tw \
    --cc=stern@rowland.harvard.edu \
    /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.