Intel PECI CPU and DIMM thermal monitoring
Hardware monitoring support for Intel's Platform Environment Control Interface (PECI), a sideband bus that baseboard management controllers and the OS use to read CPU package and DIMM temperatures on Intel Xeon server platforms. The peci-cputemp and peci-dimmtemp modules expose those readings to userspace through the standard hwmon interface.
recommendation
It should stay because PECI remains the standard thermal and manageability interface on current Intel Xeon server platforms, including the 2025 Eagle Stream generation, and the in-tree drivers are actively maintained with around 20 substantive commits over the last five years from roughly ten contributors. There is no successor driver and no sign of an upstream removal effort, so this is straightforwardly kept.
repository signals
sources
- git.kernel.org
Upstream directory history is recent and ongoing rather than abandoned; this matches the provided metadata showing substantive touches through 2026-03-24.
- docs.kernel.org
The in-tree hwmon documentation describes `peci-cputemp` as the generic Intel PECI CPU temperature monitor for Xeon server processors.
- docs.kernel.org
The companion `peci-dimmtemp` driver exposes DIMM temperature readings over the same Intel PECI path on supported server CPUs.
- edc.intel.com
Intel's 2025 Eagle Stream platform documentation still documents PECI as an active thermal/manageability interface on current server platforms.
codex reasoning notes (technical)
Real driver directory: contains hwmon PECI modules (`peci-cputemp`, `peci-dimmtemp`) with module driver entry points. `docs.kernel.org` URLs were obtained via web search (`turn0search0`/`turn0search1`). The Intel Eagle Stream PECI URL was obtained via web search (`turn0search3`). The `git.kernel.org` log URL is canonical recall; it was used together with the provided static history (20 substantive commits in 5y, last touch 2026-03-24, 10 authors) and local Kconfig/source inspection via shell to judge maintenance state. I found no evidence of an active removal push; given recent upstream churn, current Intel platform PECI documentation, and lack of a successor driver for the same use case, this should be kept rather than deprecated.