All of lore.kernel.org
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] ARM: cpuidle: make arm_cpuidle_suspend() a bit more efficient
Date: Fri, 8 Jul 2016 14:17:29 +0800	[thread overview]
Message-ID: <20160708141729.3fa61c10@xhacker> (raw)
In-Reply-To: <20160707134628.GB20553@linaro.org>

Dear Daniel,

On Thu, 7 Jul 2016 15:46:28 +0200 Daniel Lezcano wrote:

> On Wed, Jul 06, 2016 at 02:15:55PM +0800, Jisheng Zhang wrote:
> > Currently, we check cpuidle_ops.suspend every time when entering a
> > low-power idle state. But this check could be avoided in this hot path
> > by moving it into arm_cpuidle_read_ops() to reduce arm_cpuidle_suspend
> > overhead a bit.
> > 
> > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> > ---  
> 
> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>

I'm not sure the upstream merging path this patch should follow, Per my
understanding, I need to put it into Russell's PATCH system.

Thanks in advance,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: <lorenzo.pieralisi@arm.com>, <lina.iyer@linaro.org>,
	<linux@armlinux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] ARM: cpuidle: make arm_cpuidle_suspend() a bit more efficient
Date: Fri, 8 Jul 2016 14:17:29 +0800	[thread overview]
Message-ID: <20160708141729.3fa61c10@xhacker> (raw)
In-Reply-To: <20160707134628.GB20553@linaro.org>

Dear Daniel,

On Thu, 7 Jul 2016 15:46:28 +0200 Daniel Lezcano wrote:

> On Wed, Jul 06, 2016 at 02:15:55PM +0800, Jisheng Zhang wrote:
> > Currently, we check cpuidle_ops.suspend every time when entering a
> > low-power idle state. But this check could be avoided in this hot path
> > by moving it into arm_cpuidle_read_ops() to reduce arm_cpuidle_suspend
> > overhead a bit.
> > 
> > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> > ---  
> 
> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>

I'm not sure the upstream merging path this patch should follow, Per my
understanding, I need to put it into Russell's PATCH system.

Thanks in advance,
Jisheng

  reply	other threads:[~2016-07-08  6:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  6:15 [PATCH v4 0/2] make arm_cpuidle_suspend() a bit more efficient Jisheng Zhang
2016-07-06  6:15 ` Jisheng Zhang
2016-07-06  6:15 ` [PATCH v4 1/2] ARM: cpuidle: fix !cpuidle_ops[cpu].init case during init Jisheng Zhang
2016-07-06  6:15   ` Jisheng Zhang
2016-07-07 13:45   ` Daniel Lezcano
2016-07-07 13:45     ` Daniel Lezcano
2016-07-06  6:15 ` [PATCH v4 2/2] ARM: cpuidle: make arm_cpuidle_suspend() a bit more efficient Jisheng Zhang
2016-07-06  6:15   ` Jisheng Zhang
2016-07-07 13:46   ` Daniel Lezcano
2016-07-07 13:46     ` Daniel Lezcano
2016-07-08  6:17     ` Jisheng Zhang [this message]
2016-07-08  6:17       ` Jisheng Zhang
2016-07-08 10:50       ` Daniel Lezcano
2016-07-08 10:50         ` Daniel Lezcano
2016-07-08 10:58         ` Jisheng Zhang
2016-07-08 10:58           ` Jisheng Zhang
2016-07-14 15:31           ` Russell King - ARM Linux
2016-07-14 15:31             ` Russell King - ARM Linux
2016-07-15  7:38             ` Jisheng Zhang
2016-07-15  7:38               ` 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=20160708141729.3fa61c10@xhacker \
    --to=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.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.