From: Will Deacon <will.deacon@arm.com>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: catalin.marinas@arm.com, lorenzo.pieralisi@arm.com,
daniel.lezcano@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: cpuidle: make arm_cpuidle_suspend() more efficient
Date: Thu, 24 Mar 2016 11:15:07 +0000 [thread overview]
Message-ID: <20160324111507.GB9323@arm.com> (raw)
In-Reply-To: <1458796130-6109-1-git-send-email-jszhang@marvell.com>
On Thu, Mar 24, 2016 at 01:08:48PM +0800, Jisheng Zhang wrote:
> This series is to improve the arm_cpuidle_suspend() a bit by removing/moving
> out checks from this hot path.
>
> Jisheng Zhang (2):
> arm64: cpuidle: remove cpu_ops check from arm_cpuidle_suspend()
> arm64: cpuidle: make arm_cpuidle_suspend() a bit more efficient
>
> arch/arm64/kernel/cpuidle.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
These look fine to me, but do you have any rough numbers showing what
sort of improvement we get from this change?
Will
next prev parent reply other threads:[~2016-03-24 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 5:08 [PATCH 0/2] arm64: cpuidle: make arm_cpuidle_suspend() more efficient Jisheng Zhang
2016-03-24 5:08 ` [PATCH 1/2] arm64: cpuidle: remove cpu_ops check from arm_cpuidle_suspend() Jisheng Zhang
2016-03-24 5:08 ` [PATCH 2/2] arm64: cpuidle: make arm_cpuidle_suspend() a bit more efficient Jisheng Zhang
2016-03-24 11:15 ` Will Deacon [this message]
2016-03-24 13:18 ` [PATCH 0/2] arm64: cpuidle: make arm_cpuidle_suspend() " Jisheng Zhang
2016-03-24 16:44 ` Lorenzo Pieralisi
2016-03-25 2:40 ` Jisheng Zhang
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=20160324111507.GB9323@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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