linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: enable generic idle loop
Date: Tue, 15 Sep 2015 19:20:08 +0800	[thread overview]
Message-ID: <20150915112008.GA30920@leoy-linaro> (raw)
In-Reply-To: <20150821155425.GC16410@e104818-lin.cambridge.arm.com>

Hi Will,

On Fri, Aug 21, 2015 at 04:54:25PM +0100, Catalin Marinas wrote:
> On Fri, Aug 21, 2015 at 05:14:46PM +0800, Leo Yan wrote:
> > On Fri, Aug 21, 2015 at 10:00:43AM +0100, Catalin Marinas wrote:
> > > On Fri, Aug 21, 2015 at 11:40:22AM +0800, Leo Yan wrote:
> > > > Enable generic idle loop for ARM64, so can support for hlt/nohlt
> > > > command line options to override default idle loop behavior.
> > > 
> > > Just curious, what do you need this for?
> > 
> > With this config, usually we can add "nohlt" in command line to force
> > the cpu will never be powered off; so can quickly narrow down if some
> > issues are related with cpuidle or not.
> > 
> > And if CPU is powered off, then its debug logic also will be powered off.
> > So we can simply use this method to let debugger always hot connect with
> > the target CPU.
> 
> OK.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Suppose you have missed this patch at previous merge window,
so just for reminding.

Thanks,
Leo Yan

  reply	other threads:[~2015-09-15 11:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  3:40 [PATCH] arm64: enable generic idle loop Leo Yan
2015-08-21  9:00 ` Catalin Marinas
2015-08-21  9:14   ` Leo Yan
2015-08-21 15:54     ` Catalin Marinas
2015-09-15 11:20       ` Leo Yan [this message]
2015-09-15 14:31         ` Catalin Marinas
2015-09-15 14:44           ` Will Deacon
2015-09-15 14:51             ` Leo Yan

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=20150915112008.GA30920@leoy-linaro \
    --to=leo.yan@linaro.org \
    --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 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).