c483e7ea10
A recent suggested change to the IFS code has shown that the userspace API needs a bit more work, see: https://lore.kernel.org/platform-driver-x86/20220708151938.986530-1-jithu.joseph@intel.com/ Mark it as BROKEN before 5.19 ships, to give ourselves one more kernel-devel cycle to get the userspace API right. Link: https://lore.kernel.org/platform-driver-x86/20220708151938.986530-1-jithu.joseph@intel.com/ Cc: Jithu Joseph <jithu.joseph@intel.com> Cc: Ashok Raj <ashok.raj@intel.com> Cc: Tony Luck <tony.luck@intel.com> Suggested-by: Greg KH <gregkh@linuxfoundation.org> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Link: https://lore.kernel.org/r/20220710140736.6492-1-hdegoede@redhat.com
16 lines
609 B
Text
16 lines
609 B
Text
config INTEL_IFS
|
|
tristate "Intel In Field Scan"
|
|
depends on X86 && CPU_SUP_INTEL && 64BIT && SMP
|
|
# Discussion on the list has shown that the sysfs API needs a bit
|
|
# more work, mark this as broken for now
|
|
depends on BROKEN
|
|
select INTEL_IFS_DEVICE
|
|
help
|
|
Enable support for the In Field Scan capability in select
|
|
CPUs. The capability allows for running low level tests via
|
|
a scan image distributed by Intel via Github to validate CPU
|
|
operation beyond baseline RAS capabilities. To compile this
|
|
support as a module, choose M here. The module will be called
|
|
intel_ifs.
|
|
|
|
If unsure, say N.
|