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
| ||
|
Date: Fri, 6 Apr 2012 16:02:37 +0530 From: "Shilimkar, Santosh" <santosh.shilimkar@...com> To: Peter De Schrijver <pdeschrijver@...dia.com> Cc: Kevin Hilman <khilman@...com>, Len Brown <len.brown@...el.com>, Trinabh Gupta <g.trinabh@...il.com>, Russell King <linux@....linux.org.uk>, Stephen Warren <swarren@...dotorg.org>, Daniel Lezcano <daniel.lezcano@...aro.org>, linux-kernel@...r.kernel.org, Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>, linux-tegra@...r.kernel.org, Colin Cross <ccross@...roid.com>, Olof Johansson <olof@...om.net>, linux-arm-kernel@...ts.infradead.org, Arjan van de Ven <arjan@...ux.intel.com> Subject: Re: [RFC PATCH] cpuidle: allow per cpu latencies Peter, On Thu, Apr 5, 2012 at 7:07 PM, Arjan van de Ven <arjan@...ux.intel.com> wrote: > On 4/5/2012 2:53 AM, Peter De Schrijver wrote: >> This patch doesn't update all cpuidle device registrations. I will do that > > question is if you want to do per cpu latencies, or if you want to have > both types of C state in one big table, and have each of the tegra cpyu > types pick half of them... > > Indeed !! That should work. I thought the C-states are always per CPU based and during the cpuidle registration you can register C-state accordingly based on the specific CPU types with different latencies if needed. Am I missing something ? Regards Santosh -- 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