| 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
| ||
|
Message-ID: <20150527080831.GJ19282@twins.programming.kicks-ass.net> Date: Wed, 27 May 2015 10:08:31 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Pavel Machek <pavel@....cz> Cc: mingo@...hat.com, linux-kernel@...r.kernel.org, cooloney@...il.com, rpurdie@...ys.net, j.anaszewski@...sung.com, linux-leds@...r.kernel.org Subject: Re: CPU LED trigger: add hooks to generic code so that it works on x86 On Wed, May 27, 2015 at 09:47:57AM +0200, Pavel Machek wrote: > On Wed 2015-05-27 09:43:43, Peter Zijlstra wrote: > > On Wed, May 27, 2015 at 08:57:12AM +0200, Pavel Machek wrote: > > > > > > CPU LED trigger hooks are currently hidden in arm-specific code, which > > > means that this trigger only works on arm. Add it to the generic > > > code, so that it works on x86, too. > > > > And why do we want to go and slow down the idle loop for everyone? > > If the trigger is not configured, this is not slowing down anyone. > > If the trigger is configured, well, then the user requested the > functionality. So we are not slowing down _everyone_, just the people > that want the blinking. What kind of x86 hardware will support this? If its _everything_ distros will have to enable this and it suddenly becomes a lot of people. -- 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