| 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: <AANLkTinxgurYfHosAgEETggCAirjMDEaG3YSE4dKdOad@mail.gmail.com> Date: Tue, 12 Oct 2010 12:24:45 -0700 From: Blaise Gassend <blaise@...lowgarage.com> To: linux-kernel@...r.kernel.org Subject: Kconfig.preempt advertises no longer existing hardirq-preempt option and related proc entries. Seems like the documentation for PREEMPT_HARDIRQS has fallen behind the code. I would like to submit the following patch to fix that situation. Anybody happen to know why the option and proc entry were removed? I would have loved to have used them... Signed-off-by: Blaise Gassend <blaise@...lowgarage.com> diff -ru linux-2.6.33.7-rt29/kernel/Kconfig.preempt linux-2.6.33.7-rt29-modified/kernel/Kconfig.preempt --- linux-2.6.33.7-rt29/kernel/Kconfig.preempt 2010-10-12 09:59:18.335119093 -0700 +++ linux-2.6.33.7-rt29-modified/kernel/Kconfig.preempt 2010-10-12 10:01:17.185554319 -0700 @@ -113,10 +113,4 @@ in their own kernel thread context. While this helps latency, this feature can also reduce performance. - The threading of hardirqs can also be controlled via the - /proc/sys/kernel/hardirq_preemption runtime flag and the - hardirq-preempt=0/1 boot-time option. Per-irq threading can - be enabled/disable via the /proc/irq/<IRQ>/<handler>/threaded - runtime flags. - Say N if you are unsure. -- 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