public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, yongjun_wei@trendmicro.com.cn,
	boqun.feng@gmail.com, mark.rutland@arm.com, bristot@redhat.com,
	peterz@infradead.org, eric@engestrom.ch
Subject: [GIT PULL rcu/next] RCU commits for 4.8
Date: Wed, 29 Jun 2016 11:49:09 -0700	[thread overview]
Message-ID: <20160629184909.GA3425@linux.vnet.ibm.com> (raw)

Hello, Ingo,

This series contains the following changes:

1.	Documentation updates.  Just some simple changes, no design-level
	additions.  I guess that means two for the next merge window...

	http://lkml.kernel.org/g/20160615213847.GA3610@linux.vnet.ibm.com

2.	Miscellaneous fixes.

	http://lkml.kernel.org/g/20160615214550.GA4931@linux.vnet.ibm.com

3.	Torture-test updates.

	http://lkml.kernel.org/g/20160615220924.GA7877@linux.vnet.ibm.com

All of these changes have been subjected 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 4d03754f04247bc4d469b78b61cac942df37445d:

  Merge branches 'doc.2016.06.15a', 'fixes.2016.06.15b' and 'torture.2016.06.14a' into HEAD (2016-06-15 16:58:03 -0700)

----------------------------------------------------------------
Boqun Feng (6):
      torture: Stop onoff task if there is only one cpu
      rcutorture/doc: Create initrd using dracut
      rcutorture: Use vmlinux as the fallback kernel image
      rcutorture: Make -soundhw a x86 specific option
      rcutorture: Don't specify the cpu type of QEMU on PPC
      rcuperf: Don't treat gp_exp mis-setting as a WARN

Daniel Bristot de Oliveira (1):
      rcu: sysctl: Panic on RCU Stall

Eric Engestrom (1):
      Documentation: Fix spelling mistake

Mark Rutland (1):
      rcu: Correctly handle sparse possible cpus

Paul E. McKenney (20):
      documentation: Add reference to 2014 RCU API LWN article
      documentation: Add references to 2010 and 2014 Big API Tables
      documentation: Add RCU_NONIDLE() restrictions to requirements
      rcu: Fix outdated rcu_scheduler_active comment
      rcu: Fix outdated hotplug-exclusion comment in rcu_gp_init()
      rcu: Move expedited code from tree.c to tree_exp.h
      rcu: Move expedited code from tree_plugin.h to tree_exp.h
      rcu: Document RCU_NONIDLE() restrictions in comment header
      torture: Simplify code, eliminate RCU_PERF_TEST_RUNNABLE
      torture: Remove CONFIG_RCU_TORTURE_TEST_RUNNABLE, simplify code
      torture: Forgive lengthy trace dumps and preemption
      torture:  Break online and offline functions out of torture_onoff()
      torture: Add starvation events to error summary
      rcutorture: Drop "-soundhw pcspkr" from x86 boot arguments
      torture: Inflict default jitter
      rcu: No ordering for rcu_assign_pointer() of NULL
      rcu: Disable TASKS_RCU for usermode Linux
      rcu: Make call_rcu_tasks() tolerate first call with irqs disabled
      rcu: Fix a typo in a comment
      Merge branches 'doc.2016.06.15a', 'fixes.2016.06.15b' and 'torture.2016.06.14a' into HEAD

Peter Zijlstra (1):
      rcu: Remove some superfluous lines

Wei Yongjun (1):
      rcutorture: Fix error return code in rcu_perf_init()

 .../RCU/Design/Requirements/Requirements.html      |  35 ++
 Documentation/RCU/stallwarn.txt                    |   2 +-
 Documentation/RCU/whatisRCU.txt                    |   3 +
 Documentation/sysctl/kernel.txt                    |  12 +
 include/linux/kernel.h                             |   1 +
 include/linux/rcupdate.h                           |  23 +-
 include/linux/torture.h                            |   4 +
 init/Kconfig                                       |   1 +
 kernel/rcu/rcuperf.c                               |  25 +-
 kernel/rcu/rcutorture.c                            |   9 +-
 kernel/rcu/tree.c                                  | 586 +-----------------
 kernel/rcu/tree.h                                  |  15 +
 kernel/rcu/tree_exp.h                              | 656 +++++++++++++++++++++
 kernel/rcu/tree_plugin.h                           |  95 +--
 kernel/rcu/update.c                                |   7 +-
 kernel/sysctl.c                                    |  11 +
 kernel/torture.c                                   | 176 ++++--
 lib/Kconfig.debug                                  |  33 --
 .../testing/selftests/rcutorture/bin/functions.sh  |  12 +-
 .../selftests/rcutorture/bin/kvm-test-1-run.sh     |  34 +-
 tools/testing/selftests/rcutorture/bin/kvm.sh      |   2 +-
 .../selftests/rcutorture/bin/parse-console.sh      |   7 +-
 tools/testing/selftests/rcutorture/doc/initrd.txt  |  22 +
 23 files changed, 978 insertions(+), 793 deletions(-)
 create mode 100644 kernel/rcu/tree_exp.h

             reply	other threads:[~2016-06-29 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 18:49 Paul E. McKenney [this message]
2016-06-30  6:29 ` [GIT PULL rcu/next] RCU commits for 4.8 Ingo Molnar

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=20160629184909.GA3425@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=boqun.feng@gmail.com \
    --cc=bristot@redhat.com \
    --cc=eric@engestrom.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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