| 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: <20131230184053.F1939546@viggo.jf.intel.com> Date: Mon, 30 Dec 2013 10:40:53 -0800 From: Dave Hansen <dave@...1.net> To: linux-kernel@...r.kernel.org Cc: x86@...nel.org, Dave Hansen <dave@...1.net> Subject: [PATCH 05/12] x86 Kconfig: processor drivers From: Dave Hansen <dave.hansen@...ux.intel.com> These are both drivers to access very cpu and architecture-specific features. However, they are probably not very commonly changed in the configuration. Give them their own menu. Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com> --- linux.git-davehans/arch/x86/Kconfig | 169 ++++++++++++++++++------------------ 1 file changed, 86 insertions(+), 83 deletions(-) diff -puN arch/x86/Kconfig~processor-drivers arch/x86/Kconfig --- linux.git/arch/x86/Kconfig~processor-drivers 2013-12-30 10:37:44.825215930 -0800 +++ linux.git-davehans/arch/x86/Kconfig 2013-12-30 10:37:44.830216154 -0800 @@ -396,6 +396,92 @@ config X86_SMAP If unsure, say Y. +comment "Processor Feature Drivers" + +config MICROCODE + tristate "CPU microcode loading support" + depends on CPU_SUP_AMD || CPU_SUP_INTEL + select FW_LOADER + ---help--- + + If you say Y here, you will be able to update the microcode on + certain Intel and AMD processors. The Intel support is for the + IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, + Xeon etc. The AMD support is for families 0x10 and later. You will + obviously need the actual microcode binary data itself which is not + shipped with the Linux kernel. + + This option selects the general module only, you need to select + at least one vendor specific module as well. + + To compile this driver as a module, choose M here: the module + will be called microcode. + +config MICROCODE_INTEL + bool "Intel microcode loading support" + depends on MICROCODE + default MICROCODE + select FW_LOADER + ---help--- + This options enables microcode patch loading support for Intel + processors. + + For latest news and information on obtaining all the required + Intel ingredients for this driver, check: + <http://www.urbanmyth.org/microcode/>. + +config MICROCODE_AMD + bool "AMD microcode loading support" + depends on MICROCODE + select FW_LOADER + ---help--- + If you select this option, microcode patch loading support for AMD + processors will be enabled. + +config MICROCODE_OLD_INTERFACE + def_bool y + depends on MICROCODE + +config MICROCODE_INTEL_LIB + def_bool y + depends on MICROCODE_INTEL + +config MICROCODE_INTEL_EARLY + def_bool n + +config MICROCODE_AMD_EARLY + def_bool n + +config MICROCODE_EARLY + bool "Early load microcode" + depends on MICROCODE=y && BLK_DEV_INITRD + select MICROCODE_INTEL_EARLY if MICROCODE_INTEL + select MICROCODE_AMD_EARLY if MICROCODE_AMD + default y + help + This option provides functionality to read additional microcode data + at the beginning of initrd image. The data tells kernel to load + microcode to CPU's as early as possible. No functional change if no + microcode data is glued to the initrd, therefore it's safe to say Y. + +config X86_MSR + tristate "/dev/cpu/*/msr - Model-specific register support" + ---help--- + This device gives privileged processes access to the x86 + Model-Specific Registers (MSRs). It is a character device with + major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. + MSR accesses are directed to a specific CPU on multi-processor + systems. + +config X86_CPUID + tristate "/dev/cpu/*/cpuid - CPU information support" + ---help--- + This device gives processes access to the x86 CPUID instruction to + be executed on a specific processor. It is a character device + with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to + /dev/cpu/31/cpuid. + + endmenu # Processor Options config X86_X2APIC @@ -1434,89 +1520,6 @@ config X86_REBOOTFIXUPS enable this option even if you don't need it. Say N otherwise. -config MICROCODE - tristate "CPU microcode loading support" - depends on CPU_SUP_AMD || CPU_SUP_INTEL - select FW_LOADER - ---help--- - - If you say Y here, you will be able to update the microcode on - certain Intel and AMD processors. The Intel support is for the - IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, - Xeon etc. The AMD support is for families 0x10 and later. You will - obviously need the actual microcode binary data itself which is not - shipped with the Linux kernel. - - This option selects the general module only, you need to select - at least one vendor specific module as well. - - To compile this driver as a module, choose M here: the module - will be called microcode. - -config MICROCODE_INTEL - bool "Intel microcode loading support" - depends on MICROCODE - default MICROCODE - select FW_LOADER - ---help--- - This options enables microcode patch loading support for Intel - processors. - - For latest news and information on obtaining all the required - Intel ingredients for this driver, check: - <http://www.urbanmyth.org/microcode/>. - -config MICROCODE_AMD - bool "AMD microcode loading support" - depends on MICROCODE - select FW_LOADER - ---help--- - If you select this option, microcode patch loading support for AMD - processors will be enabled. - -config MICROCODE_OLD_INTERFACE - def_bool y - depends on MICROCODE - -config MICROCODE_INTEL_LIB - def_bool y - depends on MICROCODE_INTEL - -config MICROCODE_INTEL_EARLY - def_bool n - -config MICROCODE_AMD_EARLY - def_bool n - -config MICROCODE_EARLY - bool "Early load microcode" - depends on MICROCODE=y && BLK_DEV_INITRD - select MICROCODE_INTEL_EARLY if MICROCODE_INTEL - select MICROCODE_AMD_EARLY if MICROCODE_AMD - default y - help - This option provides functionality to read additional microcode data - at the beginning of initrd image. The data tells kernel to load - microcode to CPU's as early as possible. No functional change if no - microcode data is glued to the initrd, therefore it's safe to say Y. - -config X86_MSR - tristate "/dev/cpu/*/msr - Model-specific register support" - ---help--- - This device gives privileged processes access to the x86 - Model-Specific Registers (MSRs). It is a character device with - major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. - MSR accesses are directed to a specific CPU on multi-processor - systems. - -config X86_CPUID - tristate "/dev/cpu/*/cpuid - CPU information support" - ---help--- - This device gives processes access to the x86 CPUID instruction to - be executed on a specific processor. It is a character device - with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to - /dev/cpu/31/cpuid. - config MATH_EMULATION bool prompt "Math emulation" if X86_32 _ -- 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