Revision as of 00:34, 17 July 2024

ROCm 6.2

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

The latest ROCm release in sync with AMD's latest upstream release. Builds on the math libraries released in F40 to also include packages to run AI workloads. Has been integrated with Fedora's PyTorch.

Owner

Name: Tom Rix
Email: trix@redhat.com

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-07-17
[<will be assigned by the Wrangler> 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

ROCm 6.2 is the latest iteration of AMD's compute libraries that work with the linux kernel to allow users to run compute workloads on their GPU's. As many GPU's as possible are enabled so open acceleration is available and easy for to as wide an audience as possible.

Feedback

Benefit to Fedora

By providing system level acceleration, the challenges for developers to sync out of tree kernel drivers with complicated software stacks is removed. Developers can focus on solving their problems, not the problems of the getting hardware acceleration working.

Scope

Proposal owners: ROCm Packagers Sig has to update the current set from 6.1.2 to 6.2.0

Other developers: Fedora tools has to release compat packages for llvm18 because ROCm 6.2 is not compatible with llvm19 which is slated for inclusion with F41 (this is already planned and on their schedule). The ROCm upstreams need to finalize the 6.2 release which is expected prior to F41's release

Release engineering: N/A (not needed for this Change)

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

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

Alignment with the Fedora Strategy: "Innovation & Leadership in Technology: We integrate programming language stack ecosystems" by including the latest release of the ROCm ecosystem, Fedora is better enabling heterogeneous computation and supporting the latest hardware for ROCm.

Upgrade/compatibility impact

There should be no backwards incompatible changes for this upgrade, it is a minor release.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

How To Test

AMD GPU hardware is needed. Most of the ROCm packages have option test subpackages which need to be built locally for a single specific AMD shader family (e.g gfx1100). These will be built and run.

User Experience

Dependencies

Contingency Plan

The current ROCm set 6.1.2 has all of the current packages expected in 6.2 llvm17 will be maintained by the ROCm packagers sig (Tom Rix)

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+= ROCm 6.2 =
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name <!-- The name of your change proposal --> = ROCm 6.2
 {{Change_Proposal_Banner}}
@@ Line 26: / Line 18: @@
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 -->
 == Current status ==
 [[Category:ChangePageIncomplete]]
@@ Line 47: / Line 37: @@
 ON_QA -> change is fully code complete
 -->
-* [Announced]
 * [<will be assigned by the Wrangler> Discussion thread]
 * FESCo issue: <will be assigned by the Wrangler>
@@ Line 91: / Line 80: @@
 == Scope ==
-* Proposal owners:
+* Proposal owners: ROCm Packagers Sig has to update the current set from 6.1.2 to 6.2.0
-Fedora tools has to release compat llvm18 has to be available because ROCm 6.2 uses this compiler
-AMD has to finalize the release of 6.2
-ROCm Packagers Sig has to update the current set from 6.1.2 to 6.2.0
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> Fedora tools has to release compat packages for llvm18 because ROCm 6.2 is not compatible with llvm19 which is slated for inclusion with F41 (this is already planned and on their schedule). The ROCm upstreams need to finalize the 6.2 release which is expected prior to F41's release
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 111: / Line 97: @@
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with the Fedora Strategy:
+* Alignment with the Fedora Strategy: "Innovation & Leadership in Technology: We integrate programming language stack ecosystems" by including the latest release of the ROCm ecosystem, Fedora is better enabling heterogeneous computation and supporting the latest hardware for ROCm.
 <!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider -->
@@ Line 118: / Line 104: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+There should be no backwards incompatible changes for this upgrade, it is a minor release.
 == Early Testing (Optional) ==
 <!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. -->
-Do you require 'QA Blueprint' support? Y/N <!-- Optional Step for System-Wide Changes only -->
+Do you require 'QA Blueprint' support? N <!-- Optional Step for System-Wide Changes only -->
 == How To Test ==
 AMD GPU hardware is needed.
-Most of the ROCm packages have option test subpackages, these will be built and run.
+Most of the ROCm packages have option test subpackages which need to be built locally for a single specific AMD shader family (e.g `gfx1100`). These will be built and run.
 <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  This can be based off of the above section if early testing has been completed. If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.

Search

Changes/ROCm6.2: Difference between revisions