From: Thomas Gleixner <tglx@linutronix.de>
To: Zhaoyang Huang <zhaoyang.huang@linaro.org>
Cc: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Geng Ren" <geng.ren@spreadtrum.com>,
"Alex Wang" <alex.wang@spreadtrum.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org,
"Zhaoyang Huang (黄朝阳)" <zhaoyang.huang@spreadtrum.com>
Subject: Re: [RESEND PATCH v2 2/2] power/idle: enhance the precision of sleep_length
Date: Thu, 23 Jun 2016 10:18:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1606231016290.5839@nanos> (raw)
In-Reply-To: <CAN2waFuLRG1AsebmWey6N16v8AM7HDK6q=tV1su-gNWNjbC6hw@mail.gmail.com>
On Thu, 23 Jun 2016, Zhaoyang Huang wrote:
> On 23 June 2016 at 15:01, Thomas Gleixner <tglx@linutronix.de> wrote:
> Thomas, I agree with you, I have discussed the modification with the
> call back owner. However, I wonder if we can make the idle's framework
> to be more precised without the assumption of short CPU_PM_ENTER
> callbacks. Thank you!
What's the point? To help people who put insanities into the idle code path?
Thanks,
tglx
next prev parent reply other threads:[~2016-06-23 8:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 9:13 [RESEND PATCH v2 1/2] power/cpuidle: enhance the precision of state select Zhaoyang Huang
2016-06-17 9:13 ` [RESEND PATCH v2 2/2] power/idle: enhance the precision of sleep_length Zhaoyang Huang
2016-06-17 9:27 ` Thomas Gleixner
2016-06-17 11:18 ` Zhaoyang Huang
2016-06-17 11:50 ` Thomas Gleixner
2016-06-20 1:14 ` Zhaoyang Huang
2016-06-22 3:01 ` Zhaoyang Huang
2016-06-23 7:01 ` Thomas Gleixner
2016-06-23 7:26 ` Zhaoyang Huang
2016-06-23 8:18 ` Thomas Gleixner [this message]
2016-06-23 8:34 ` Zhaoyang Huang
2016-06-23 8:35 ` Thomas Gleixner
2016-06-23 8:45 ` Zhaoyang Huang
2016-06-23 10:16 ` Thomas Gleixner
2016-06-25 1:09 ` [RESEND PATCH v2 1/2] power/cpuidle: enhance the precision of state select Rafael J. Wysocki
2016-06-27 1:13 ` Zhaoyang Huang
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=alpine.DEB.2.11.1606231016290.5839@nanos \
--to=tglx@linutronix.de \
--cc=alex.wang@spreadtrum.com \
--cc=daniel.lezcano@linaro.org \
--cc=geng.ren@spreadtrum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=zhaoyang.huang@linaro.org \
--cc=zhaoyang.huang@spreadtrum.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 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.