mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, linuc.decode@gmail.com,
	kvm@vger.kernel.org, pbonzini@redhat.com
Subject: [GIT PULL rcu/urgent] Allow SRCU readers in irq handlers for KVM
Date: Thu, 8 Jun 2017 18:45:51 -0700	[thread overview]
Message-ID: <20170609014551.GA22701@linux.vnet.ibm.com> (raw)

Hello, Ingo,

This series enables srcu_read_lock() and srcu_read_unlock to be used from
interrupt handlers, which fixes a bug in KVM's use of SRCU in delivery
of interrupts to guest OSes.  These patches have been exposed to 0day
Test Robot and to -next testing, have been tested by the KVM folks,
and were posted to LKML:

http://lkml.kernel.org/r/20170605220919.GA27820@linux.vnet.ibm.com

These changes, based on v4.2-rc4, are available in the git repository at:

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

for you to fetch changes up to 1123a6041654e8f889014659593bad4168e542c2:

  srcu: Allow use of Classic SRCU from both process and interrupt context (2017-06-08 08:25:19 -0700)

----------------------------------------------------------------
Paolo Bonzini (2):
      srcu: Allow use of Tiny/Tree SRCU from both process and interrupt context
      srcu: Allow use of Classic SRCU from both process and interrupt context

 include/linux/srcu.h  | 2 --
 kernel/rcu/srcu.c     | 5 ++---
 kernel/rcu/srcutiny.c | 7 ++++---
 kernel/rcu/srcutree.c | 5 ++---
 4 files changed, 8 insertions(+), 11 deletions(-)

             reply	other threads:[~2017-06-09  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  1:45 Paul E. McKenney [this message]
2017-06-09  6:18 ` 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=20170609014551.GA22701@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linuc.decode@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pbonzini@redhat.com \
    /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

Powered by JetHome