** Summary changed:

- Backport Intel Compute Runtime to enable LNL and BMG on Noble
+ [SRU] Backport Intel Compute Runtime to enable LNL and BMG on Noble

** Description changed:

+ SRU exception definition available here:
+ https://documentation.ubuntu.com/project/SRU/reference/exception-Intel-
+ Graphics-Updates/
+ 
  [ Impact ]
  
  Without backporting these versions, the graphics stack in Ubuntu would not
  run on Lunar Lake (LNL) and Battlemage (BMG). This is not backporting a 
single fix, nor an MRE, but backporting a later version of each package for 
platform enablement.
  
  See the Intel Graphics SRU exception here for more details:
  
https://documentation.ubuntu.com/sru/en/latest/reference/package-specific/#defined-exceptions
  
  As this is the first time following a newly established Intel Graphics
  SRU exception, we have decided to submit a partial-stack SRU to update
  the Compute stack. We have chosen this stack because it is already
  broken in Noble, according to Intel’s assessments.
  
  Specifically in this SRU, Intel reports that our Noble compute runtime
  package is significantly broken, but this update would fix the issue.
  
  [ Test Plan ]
  
  In order to track intentional hardware retiring, we will compare these lists 
in the current stable and proposed versions:
  * 
https://github.com/intel/compute-runtime?tab=readme-ov-file#supported-platforms
  * 
https://github.com/intel/intel-graphics-compiler?tab=readme-ov-file#supported-platforms
  * 
https://github.com/intel/vc-intrinsics?tab=readme-ov-file#supported-platforms
  * https://github.com/intel/gmmlib?tab=readme-ov-file#supported-platforms
  
  Compute Runtime
  * Base
  
https://github.com/intel/compute-runtime/tree/23.43.27642.40?tab=readme-ov-file#supported-platforms
  * Legacy
  
https://github.com/intel/compute-runtime/tree/23.43.27642.40?tab=readme-ov-file#supported-platforms
  * Non-Legacy
  
https://github.com/intel/compute-runtime/tree/25.31.34666.3?tab=readme-ov-file#supported-platforms
  Assuming co-installation of the legacy and non legacy package (default on 
upgrade), there are no intentional hardware regressions and 8 new generations 
enabled.
  
  IGC
  * 
https://github.com/intel/intel-graphics-compiler?tab=readme-ov-file#supported-platforms
  * Base
  
https://github.com/intel/intel-graphics-compiler/tree/releases/igc-1.0.15468?tab=readme-ov-file#supported-platforms
  * IGC1 (legacy)
  
https://github.com/intel/intel-graphics-compiler/tree/releases/igc-1.0.17791?tab=readme-ov-file#supported-platforms
  * IGC2
  
https://github.com/intel/intel-graphics-compiler/tree/v2.16.0?tab=readme-ov-file#supported-platforms
  IGC1 shows an intentional regression, dropping support on gen8 for our legacy 
IGC package. IGC2 also drops gen8 support. However, this is a 
documentation-only change ahead of a future support drop. Intel has confirmed 
that we would not lose gen 8 functionality in this update.
  
  vc-intrinsics
  * 
https://github.com/intel/vc-intrinsics?tab=readme-ov-file#supported-platforms
  vc-intrinsics only added supported platforms recently at our request, so 
neither the new or old version has a supported list.
  
  gmmlib
  * Base
  
https://github.com/intel/gmmlib/tree/intel-gmmlib-22.3.17?tab=readme-ov-file#supported-platforms
  * New
  
https://github.com/intel/gmmlib/tree/intel-gmmlib-22.8.1?tab=readme-ov-file#supported-platforms
  Comparing the two lists, there are no hardware regressions, and there are 5 
generations being enabled
  
  Since we are only updating the compute stack, the following lists do not need 
to be compared:
  * https://github.com/intel/media-driver?tab=readme-ov-file#supported-platforms
  * 
https://github.com/intel/level-zero-raytracing-support?tab=readme-ov-file#supported-platforms
  * 
https://github.com/uxlfoundation/oneTBB/blob/master/SYSTEM_REQUIREMENTS.md#supported-hardware
  * 
https://github.com/intel/libvpl?tab=readme-ov-file#dispatcher-behavior-when-targeting-intel-gpus
  
  To mitigate unintentional hardware regressions, Intel's and Canonical's
  validation teams will install all proposed packages and test that the
  graphics stack is working as expected. Partner Engineering will run tests
  developed to confirm successful integration of each component and its
  dependencies. Since this SRU will focus on Compute Runtime, which provides 
OpenCL functionality, we will focus testing on OpenCL.
  
  The following tests intended for an SRU of the entire graphics stack will be 
omitted since this is only a partial graphics stack bump (compute):
  * Vulkan and OpenGL conformance testing
  * Level Zero unit testing
  * Level Zero Raytracing unit testing
  * Libvpl unit tests
  * Crucible
  * Gstreamer testing
  * FFmpeg testing
  * Firefox testing
  * GuC and HuC testing
  * Totem (default video player) testing
  
  To run OpenCL tests, use the following commands:
  sudo snap install --classic snapcraft
  sudo snap install checkbox24
  lxd init --auto
  git clone https://github.com/canonical/checkbox
  cd checkbox/contrib/checkbox-gfx
  snapcraft
  sudo snap install --dangerous --classic ./checkbox-gfx_1.0_<arch>.snap
  
  checkbox-gfx.install-opencl
  checkbox-gfx.test-opencl
  
  # Remove all installed test materials
  checkbox-gfx.remove
  
  We will then compare the initial test output (before the HWE update) with
  the new stack to ensure that there have been no regressions.
  
  The following describes which generations we will test to mitigate 
unintentional hardware regressions:
  
https://documentation.ubuntu.com/sru/en/latest/reference/exception-Intel-Graphics-Updates/#hardware-support
  
  [ Where problems could occur ]
  
  An HWE update contains a lot of new changes. On an LTS, it is
  likely that the version will not change between HWE updates, which means
  there will be substantial diffs, especially on projects as active as the
  media driver and compute runtime. With the bugfixes, refactors, and new
  features introduced in the meantime, we may be trading known issues for
  new issues. When dealing with packages like these, we could see serious
  bugs, but we have to balance that knowledge with the knowledge that
  we will only promote well-tested configurations.
  
  In this SRU specifically, we must accommodate a packaging compatibility 
solution for Compute Runtime and Intel Graphics Compiler (IGC). Intel dropped 
support for several generations starting in 24.35, so later releases now have 
two co-installable compute stacks depending on the user’s hardware:
  intel-compute-runtime-legacy —> intel-graphics-compiler
  intel-compute-runtime —> intel-graphics-compiler2
  Noble currently has the following configuration:
  intel-compute-runtime —> intel-graphics-compiler
  
  In order to transition Noble to newer versions of Compute Runtime,
  intel-compute-runtime will upgrade to the latest version which does not
  have legacy platform support. However, each intel-compute-runtime
  package recommends its intel-compute-runtime-legacy counterpart, which
  should automatically co-install legacy support on upgrade.
  
  Note that intel-compute-runtime currently depends on intel-graphics-
  compiler, but on upgrade, it will depend on intel-graphics-compiler2,
  while intel-compute-runtime-legacy will depend on intel-graphics-
  compiler. This is because IGC’s semantic versioning allows for the
  intel-graphics-compilerX format, unlike Compute Runtime’s date-based
  versioning.
  
  This upgrade path should be fine, but it is still possible that
  something unexpected happens while transitioning between the old and new
  dependency structure or in the coinstallation of the new and legacy
  packages.
  
  [ Other Info ]
  
  Packages to update:
  
  intel-compute-runtime version 23.43.27642.40-1ubuntu3.1 to
  25.31.34666.3-1ubuntu1 (Questing current)
  
  Intel-compute-runtime-legacy “Not in Noble” to 24.35.30872.32-2
  (Questing current)
  
  intel-graphics-compiler version 1.0.15468.25-2ubuntu0.1 to
  1.0.17791.18-1 (Questing current)
  
  Intel-graphics-compiler2 “Not in Noble” to 2.16.0-2ubuntu1  (Questing
  current)
  
  intel-vc-intrinsics version 0.13.0-1build1 to 0.23.1-1 (Questing
  current)
  
  intel-gmmlib version 22.3.17+ds1-1 to 22.8.1+ds1-1  (Questing current)
  
  Level-zero support in Noble appears to be sufficient for this SRU:
  
https://github.com/intel/compute-runtime/tree/25.31.34666.3?tab=readme-ov-file#supported-platforms
  
  Any known test regressions should be listed below:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2138272

Title:
  [SRU] Backport Intel Compute Runtime to enable LNL and BMG on Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/2138272/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to