From: "Paul E. McKenney" <paulmck@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86 <x86@kernel.org>
Subject: Re: [tip: core/rcu] rcu: Enable tick for nohz_full CPUs slow to provide expedited QS
Date: Sat, 25 Jan 2020 12:08:54 -0800 [thread overview]
Message-ID: <20200125200854.GA8673@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200125194846.GF2935@paulmck-ThinkPad-P72>
On Sat, Jan 25, 2020 at 11:48:46AM -0800, Paul E. McKenney wrote:
> On Sat, Jan 25, 2020 at 06:54:42PM +0100, Borislav Petkov wrote:
> > On Sat, Jan 25, 2020 at 08:10:50AM -0800, Paul E. McKenney wrote:
[ . . . ]
> > > If that works, I will re-introduce the warning with proper protection
> > > for the merge window following this coming one.
> >
> > My big box is at your service if you need stuff tested later.
>
> Thank you in advance! I just might take you up on that!
And I do have an alleged fix on branch dev of the -rcu tree:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
I am just now starting testing, so the probability of failure is
decidedly non-zero. ;-)
Thanx, Paul
next prev parent reply other threads:[~2020-01-25 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 10:42 tip-bot2 for Paul E. McKenney
2020-01-25 13:14 ` Borislav Petkov
2020-01-25 16:10 ` Paul E. McKenney
2020-01-25 17:54 ` Borislav Petkov
2020-01-25 19:48 ` Paul E. McKenney
2020-01-25 20:08 ` Paul E. McKenney [this message]
2020-01-25 20:23 ` Borislav Petkov
2020-01-25 20:19 ` Borislav Petkov
2020-01-26 1:43 ` Paul E. McKenney
2020-01-26 11:25 ` Borislav Petkov
2020-01-26 15:28 ` Paul E. McKenney
2020-01-26 17:19 ` Borislav Petkov
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=20200125200854.GA8673@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®