lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50C98413.5050707@linaro.org>
Date:	Thu, 13 Dec 2012 08:30:27 +0100
From:	Daniel Lezcano <daniel.lezcano@...aro.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Julius Werner <jwerner@...omium.org>,
	Francesco Lavra <francescolavra.fl@...il.com>,
	linux-pm@...r.kernel.org,
	Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>,
	Trinabh Gupta <g.trinabh@...il.com>,
	Lists Linaro-dev <linaro-dev@...ts.linaro.org>,
	len.brown@...el.com, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Sameer Nanda <snanda@...omium.org>
Subject: Re: [PATCH] cpuidle - remove the power_specified field in the driver

On 12/12/2012 11:42 PM, Rafael J. Wysocki wrote:
> On Wednesday, December 12, 2012 09:00:53 PM Daniel Lezcano wrote:
>> On 12/12/2012 07:50 PM, Julius Werner wrote:
>>> Thanks again for making this happen, Daniel. I like this version,
>>> except for the small nitpick that I still think it would make sense to
>>> also turn the loop in menu.c around. How about something like this:
>>>
>>>        for (i = drv->state_count - 1; i >= CPUIDLE_DRIVER_STATE_START; i++) {
>>>                 struct cpuidle_state *s = &drv->states[i];
>>>                 if (!s->disable && s->exit_latency <= latency_req &&
>>>                     s->target_residency <= data->predicted_us &&
>>>                     s->exit_latency * multiplier <= data->predicted_us) {
>>>                         data->last_state_idx = i;
>>>                         data->exit_us = s->exit_latency;
>>>                         break;
>>>                 }
>>>         }
>>
>> Actually I was planning to do that in a separate patch.
> 
> Can you submit that second patch too, please, so that people don't have to
> wonder?

Sure.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ