From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: gregkh@linuxfoundation.org, linuc.decode@gmail.com,
torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] srcu: Allow use of Classic SRCU from both process and" failed to apply to 4.9-stable tree
Date: Mon, 12 Jun 2017 10:21:30 -0700 [thread overview]
Message-ID: <20170612172130.GY3721@linux.vnet.ibm.com> (raw)
In-Reply-To: <af48b0f7-cbb9-1b92-0ffd-4bce1ed79b35@redhat.com>
On Mon, Jun 12, 2017 at 06:35:18PM +0200, Paolo Bonzini wrote:
>
>
> On 12/06/2017 18:31, Paul E. McKenney wrote:
> > Indeed, this won't apply cleanly to 4.9 and earlier because of some
> > changes to the way SRCU works. And if you try to make the obvious
> > adjustments to make the patch apply, you will break SRCU.
> >
> > So, question for Paolo... How important is it to push this back to
> > v4.9 and earlier? To make this happen, some non-trivial SRCU changes
> > would also need to be backported.
>
> Indeed I had noticed commit f2c4689640e9 ("srcu: Implement
> more-efficient reader counts", 2017-01-25). It's not very important.
OK, good to know. I haven't given up on it, so it might get done in
any case, but no promises. Not yet, anyway. ;-)
Thanx, Paul
next prev parent reply other threads:[~2017-06-12 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 12:17 FAILED: patch "[PATCH] srcu: Allow use of Classic SRCU from both process and" failed to apply to 4.9-stable tree gregkh
2017-06-12 16:31 ` Paul E. McKenney
2017-06-12 16:35 ` Paolo Bonzini
2017-06-12 17:21 ` Paul E. McKenney [this message]
2017-06-12 19:17 ` Greg KH
2017-06-12 20:15 ` 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=20170612172130.GY3721@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linuc.decode@gmail.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.