| 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: <1233310639-27916-1-git-send-email-andi@firstfloor.org> Date: Fri, 30 Jan 2009 11:17:06 +0100 From: Andi Kleen <andi@...stfloor.org> To: mingo@...e.hu Cc: linux-kernel@...r.kernel.org, lnxninja@...ux.vnet.ibm.com Subject: Genapic cleanup & NUMAQ/es7000 removal Just to demonstrate the clean up possibilities by removing es7000 and numaq here's a sample patch series. It doesn't actually remove the es7000/numaq code, but just marks them broken and then removes all the hooks only used by them. I'm not actually sure I caught all the now unused hooks, there are probably now more. Also I think there's still some other NUMAQ only code in smpboot.c that could be exercised. This removes 6 hooks and 2 fields out of struct genapic (out of 26 hooks, a reduction of ~23%!) The first three patches are independent cleanups that should be applied anyways. This gives a nice generic cleanup: Kconfig | 4 +- include/asm/bigsmp/apic.h | 4 -- include/asm/genapic.h | 17 ++---------- include/asm/setup.h | 3 -- include/asm/smpboot_hooks.h | 10 +++---- kernel/apic.c | 2 - kernel/bigsmp_32.c | 12 -------- kernel/es7000_32.c | 32 ---------------------- kernel/genapic_flat_64.c | 16 ----------- kernel/genx2apic_cluster.c | 8 ----- kernel/genx2apic_phys.c | 8 ----- kernel/genx2apic_uv_x.c | 8 ----- kernel/io_apic.c | 11 ------- kernel/numaq_32.c | 62 -------------------------------------------- kernel/probe_32.c | 8 ----- kernel/setup.c | 11 ------- kernel/smpboot.c | 54 ++------------------------------------ kernel/summit_32.c | 12 -------- 18 files changed, 13 insertions(+), 269 deletions(-) -Andi -- 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