Intel In-Field Scan (IFS) for Xeon server CPUs
A self-test facility built into recent Intel server processors (4th Gen Xeon Sapphire Rapids, 5th Gen Emerald Rapids, and Xeon 6) that runs vendor-supplied test patterns against each core to detect silent silicon faults. Data-center operators trigger scans on running fleets to flag failing cores before they corrupt workloads.
recommendation
It should stay because the underlying hardware feature ships in Intel's current Xeon line and the code is under active upstream maintenance. Maintainership was handed from Jithu Joseph to Tony Luck in mid-2025, support for the upcoming Clearwater Forest Xeons was added in late 2024, and updates continue to flow through the platform-drivers-x86 tree. No other driver exposes this CPU self-test capability.
repository signals
sources
- intel.com
Intel documents In-field Scan as a current Xeon feature on 4th Gen, 5th Gen, and Xeon 6 CPUs, and explicitly describes a Linux device driver as part of the solution.
- intel.com
Intel Xeon 6 processors were an actively marketed product family in 2025, showing the supported hardware class is still sold new.
- spinics.net
In July 2025 the IFS driver was not slated for removal; maintainership was handed from Jithu Joseph to Tony Luck, indicating continued upstream ownership.
- spinics.net
A December 2024 patch added Clearwater Forest support to intel/ifs, showing ongoing enablement for new Intel server CPU generations.
- spinics.net
The v6.15-1 platform-drivers-x86 pull for March 2025 included an intel/ifs documentation update, showing recent upstream touch rather than abandonment.
codex reasoning notes (technical)
Real driver, confirmed by local exec_command inspection of core.c and Kconfig: module_init/module_exit, x86 CPU ID table, and misc devices for Intel In Field Scan. URLs were obtained via web search_query: turn0search1 (Intel support article), turn0search0 (Intel Xeon 6 product brief), turn3search2 (MAINTAINERS handoff), turn3search0 (new CPU support patch), turn4search2 (2025 pull request including intel/ifs change). Evidence points to active maintenance and shipping hardware, with a niche but real deployment footprint in data-center/server fleets. No natural replacement driver exists for the same CPU self-test function.