Changes/IntelCompute2025

Intel Compute Runtime - Upgrade with HW cut-off

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Intel Compute Runtime parts are currently stuck at a legacy branch that isn't undergoing an active development. Newer branches did significantly cut hardware support (for GPU Generations prior to the 12th), and the aim of this change is to do the leap of faith, and rebase intel-compute-runtime and intel-igc to the latest upstream releases.

This Change doesn't affect the intel-media-driver included in the default package set, which continues to have support for old generations of hardware in the main development branches for now.

Owner

• Name: Frantisek Zatloukal, Ali Erdinc Koroglu
• Email: fzatlouk@redhat.com, aekoroglu@linux.intel.com

Current status

• Targeted release: Fedora Linux 42
• Last updated: 2024-12-16
• Announced
• Discussion thread
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Intel Compute Runtime, consisting of intel-compute-runtime, intel-igc, oneapi-level-zero, removed support for GPU Generations prior to the 12th Gen GPUs. This effectively means that any hardware released before 2020 is no longer supported for OpenCL and oneAPI workloads. The cut-off occurred first in compute-runtime with branch 24.39, released as stable on October 21st, 2024, and followed in rest of the components.

The removed architectures are listed at LEGACY_PLATFORMS:

• Broadwell
• Skylake
• Kaby Lake
• Coffee Lake
• Apollo Lake
• Gemini Lake
• Ice Lake
• Elkhart Lake

The now supported GPU generations would be:

• DG1
• Alchemist
• Tiger Lake
• Rocket Lake
• Alder Lake
• Meteor Lake
• Raptor Lake
• Lunar Lake
• Arrow Lake
• more to come...

Fedora packages thus stayed on the older branches that support older hardware generations up to Broadwell (released around 2015). These snapshots do miss support for newer Hardware generations, most notably Intel Battlemage GPUs, will miss support for upcoming graphics based on Xe3+, and lack fixes and improvements for integrated Xe2 architecture products.

Apart from HW Support plane, it'll, over time, become problematic to keep the pieces working, as new kernels, headers, and compilers do break the suite on occasion, and older branches aren't getting fixes in these areas.

This change is to propose a rebase of the entire suite to the latest upstream branches, undergoing an active development and adding support for new products.

Benefit to Fedora

This change brings in a new hardware support, and will allow to keep supporting future hardware generations. The change would also allow Fedora to come with the latest fixes and improvements (including in the performance area) to the Intel Compute Runtime. And finally, it'll allow the suite to continue to work with other parts of the components forming the stack (drivers in kernel, OpenCL, etc.) as they evolve.

This will also enable to move the suite from depending on LLVM 15 to a newer releases, bringing batch of improvements and changes done over the years in LLVM.

Scope

• Proposal owners: Prepare, and build rebased parts of the stack in a testing COPR, rebase the components in Fedora.

• Other developers: If any volunteers want/need, they can package legacy branches of the suite to keep it in the repositories.

• Release engineering: N/A

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with the Fedora Strategy:

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

How To Test

(expected in Jan/Feb 2025 timeframe)

1. Own any intel GPU from the supported generation (12th Gen onwards)
2. Enable testing COPR: TBD
3. Update to the packages in the testing COPR
4. Install intel-compute-runtime, darktable, any other software which leverages OpenCL or oneAPI
5. Run various compute tests, eg. clinfo, clpeak, rm -rf ~/.cache/darktable/ && darktable-cltest, zello_world
6. Observe the results

Contingency Plan

• Contingency mechanism: Not doing the change, reverting packages that may have been affected
• Contingency deadline: Final Freeze
• Blocks release? N/A (not a System Wide Change)

Documentation

N/A (not a System Wide Change)