linux-kernel - Re: [RFC V1] cpuidle: add idle routine registration and cleanup pm

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Oct 2010 01:33:21 +0530
From:	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
To:	Venkatesh Pallipadi <venki@...gle.com>
Cc:	Arjan van de Ven <arjan@...ux.intel.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Trinabh Gupta <trinabh@...ux.vnet.ibm.com>,
	peterz@...radead.org, lenb@...nel.org, suresh.b.siddha@...el.com,
	benh@...nel.crashing.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC V1] cpuidle: add idle routine registration and cleanup
 pm_idle pointer

* Venkatesh Pallipadi <venki@...gle.com> [2010-10-20 12:47:22]:

> >> Ok, you are suggesting that for x86 lets move cpuidle in kernel
> >> always, while it can be an optional module for other archs as it
> >> stands today.  We can slim down the cpuidle from current 7K or atleast
> >> split some parts like governors as modules if needed.
> >
> > governors as modules is a total pain. modules don't solve the problem.
> > really. it's still code you need.
> > we have two governors today, menu and ladder
> > menu is best on anything that is tickless
> > ladder is useless on any tickless kernel, and likely not better than menu on
> > non-tickless.
> > that's it.
> > It will be good to have other archs also follow the same cpuidle
> 
> I don't think they have to be modules. There can be a CPUIDLE_LITE
> which deCONFIG entire governor.c and individual governors (and
> probably sysfs stuff as well) for archs that can only use one state at
> any time, but still want to do config or runtime detection of one
> state and register that state.

hmm, CPUIDLE_LITE should resemble this patch, where there is only
simple single idle routine registration.  If the full CPUIDLE is
picked at compile time (default for x86), we could have all the
features.

Sounds like a good option to try.

--Vaidy

--
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/