From: Will Deacon <will.deacon@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Yang Shi <yang.shi@linaro.org>,
linaro-kernel@lists.linaro.org, linux-rt-users@vger.kernel.org,
catalin.marinas@arm.com, bigeasy@linutronix.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: replace read_lock to rcu lock in call_step_hook
Date: Tue, 9 Feb 2016 16:04:42 +0000 [thread overview]
Message-ID: <20160209160442.GS22874@arm.com> (raw)
In-Reply-To: <20160209100758.69d9006f@gandalf.local.home>
On Tue, Feb 09, 2016 at 10:07:58AM -0500, Steven Rostedt wrote:
> On Tue, 9 Feb 2016 14:54:26 +0000
> Will Deacon <will.deacon@arm.com> wrote:
>
>
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Will,
Hi Steve,
> The patch looks good to me. Do you want to take it through your tree?
>
> It benefits mainline too as a rcu_read_lock() is more efficient than
> rwlocks. Although I will say this is a slow path anyway.
I was thinking that Catalin would queue it for 4.6 in the arm64 tree,
since that's probably easiest in case any unlikely conflicts crop up.
Will
next prev parent reply other threads:[~2016-02-09 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:49 [PATCH] arm64: replace read_lock to rcu lock in call_step_hook Yang Shi
2016-02-09 9:02 ` Sebastian Andrzej Siewior
2016-02-09 14:54 ` Will Deacon
2016-02-09 15:07 ` Steven Rostedt
2016-02-09 16:04 ` Will Deacon [this message]
2016-02-09 16:08 ` Steven Rostedt
2016-02-09 16:24 ` Catalin Marinas
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=20160209160442.GS22874@arm.com \
--to=will.deacon@arm.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=yang.shi@linaro.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;
as well as URLs for NNTP newsgroup(s).