linux-kernel - Re: KS/Plumbers: c-state governor BOF

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Sep 2012 11:34:48 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Youquan Song <youquan.song@...ux.intel.com>
CC:	Linux kernel Mailing List <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Boris Ostrovsky <boris.ostrovsky@....com>,
	Len Brown <len.brown@...el.com>,
	Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>,
	ShuoX Liu <shuox.liu@...el.com>, youquan.song@...el.com
Subject: Re: KS/Plumbers: c-state governor BOF

On 09/11/2012 10:43 PM, Youquan Song wrote:
>> After talking about my RFC patches to the c-state governor with
>> Matthew and Arjan, it is clear that the whole concept of how
>> things are done could use some more discussion.
>>
>> Since a good number of us will be in San Diego next week, at
>> Kernel Summit / Plumbers / etc, I will organize a c-state
>> governor BOF for those who are interested.
>>
>> Things to think about:
>> - what should the c-state governor do?
>> - how to best predict the future?
>> - what kinds of odd workloads do we need to accomodate?
>
> Hi Rik,
>
> Just notice there is a topic to discuss menu governor at Kernel Summit.
> Acutally, I have posted a patchset to at May 11 2012 to bring up the
> topic, at that time, I only have a convinced and proved application
> turbostat v1 to prove that my patch are useful. I try to find other
> workloads to prove that the patchset are also solidated useful. But I
> stucked in other high priority tasks, so I move slow on it.
>  From you bring up the issue I guess that you already has real workload
> to show this issue.
> My patchset is not only improve repeat mode failure but also improve
> general prediction failure. Let's have a discuss and talk about it.
>
> Here is the patchset posted at May 11 2012.
>
> http://lwn.net/Articles/496919/ "x86,idle: Enhance cpuidle prediction to
> handle its failure"
> http://lkml.indiana.edu/hypermail/linux/kernel/1205.1/02267.html
> "[PATCH 1/3] x86,idle: Quickly notice prediction failure for repeat mode"
> http://lkml.indiana.edu/hypermail/linux/kernel/1205.1/02268.html
> "[PATCH 2/3] x86,idle: Quickly notice prediction failure in general case"
> http://lkml.indiana.edu/hypermail/linux/kernel/1205.1/02269.html
> "[PATCH 3/3] x86,idle: Set residency to 0 if target Cstate not really
> enter"

Your patches could make a lot of sense when integrated with my
patches:

http://people.redhat.com/riel/cstate/

However, we should probably get the tracepoint upstream first,
so we can know for sure :)

-- 
All rights reversed
--
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/