From: Borislav Petkov <b...@suse.de> As recently experienced, using static_cpu_has too early (before alternatives have run) causes some obscure bugs and decyphering those doesn't simply point to such premature usage.
Therefore, let's add a static_cpu_has_safe variant which always works and can be used in early code. Also, 2/5 adds a debugging option, the idea behind it being to enable all sensible debugging code which we want to enable on x86 in order to catch build and runtime issues. The idea is to save a bunch of time of wading through "Kernel hacking" and staring at options. We'll see how that actually pans out though. Borislav Petkov (5): x86, cpu: Add a synthetic cpu feature x86, debug: Add a collect-all misc debug checks option x86: Sanity-check static_cpu_has usage x86: Add a static_cpu_has_safe variant x86, FPU: Use static_cpu_has_safe before alternatives arch/x86/Kconfig.debug | 12 ++++ arch/x86/include/asm/cpufeature.h | 118 ++++++++++++++++++++++++++++++++++-- arch/x86/include/asm/fpu-internal.h | 2 +- arch/x86/kernel/cpu/common.c | 16 +++++ 4 files changed, 143 insertions(+), 5 deletions(-) -- 1.8.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
