Groups > linux.kernel > #1552073

Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep

From	Arjan van de Ven <arjan@linux.intel.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep
Date	2017-01-05 17:00 +0100
Message-ID	<sWiCl-50p-1@gated-at.bofh.it> (permalink)
References	<sWij0-4TE-7@gated-at.bofh.it> <sWij0-4TE-5@gated-at.bofh.it> <sWisF-4WY-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 1/5/2017 7:43 AM, Rik van Riel wrote:
> On Thu, 2017-01-05 at 23:29 +0800, Alex Shi wrote:
>> The obsolete commit 71abbbf85 want to introduce a dynamic cstates,
>> but it was removed for long time. Just left the nonsense deeper
>> cstate
>> checking.
>>
>> Since all target_residency and exit_latency are going longer in
>> deeper
>> idle state, no needs to waste some cpu cycle on useless seeking.
>
> Makes me wonder if it would be worth documenting the
> requirement that c-states be listed in increasing
> order?

or better, a boot time quick check...

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current state is too deep Alex Shi <alex.shi@linaro.org> - 2017-01-05 16:40 +0100
  Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current  state is too deep Rik van Riel <riel@redhat.com> - 2017-01-05 16:50 +0100
    Re: [PATCH 1/3] cpuidle/menu: stop seeking deeper idle if current  state is too deep Arjan van de Ven <arjan@linux.intel.com> - 2017-01-05 17:00 +0100

csiph-web