Skip to content

[POC] Add DOCA OFED 3.3.0#16293

Draft
joejoew wants to merge 1 commit intotomls/base/mainfrom
zwan/tomls/doca
Draft

[POC] Add DOCA OFED 3.3.0#16293
joejoew wants to merge 1 commit intotomls/base/mainfrom
zwan/tomls/doca

Conversation

@joejoew
Copy link
Copy Markdown
Contributor

@joejoew joejoew commented Mar 25, 2026

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

POC spec to add DOCA OFED 3.3.0 (corresponding mlnx-ofa_kernel 26.01) for 4.0

Change Log
  • Add spec for DOCA OFED 3.3.0
  • Add toml to specify download link for DOCA's SRPM
Does this affect the toolchain?

YES/NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

[components.mlnx-ofa_kernel.build]
# Kernel version must match the kernel on the target VM.
# target_kernel_dist carries the full dist suffix including any pre-release tag.
defines = { target_kernel_version = "6.18.5.1", target_kernel_release = "3", target_kernel_dist = ".azl4" }
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw offline discussion regarding how to keep this in sync with the kernel version via macros and such. Are you planning to hold this draft until that solution can be implemented?

#
#

%global target_kernel_version 6.18.5.1
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are these also defined here?

#
# Copyright (c) 2012 Mellanox Technologies. All rights reserved.
#
# This Software is licensed under one of the following licenses:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the license for the spec or for the sources covered by it? Where did the spec come from, and how do we plan to ingest updates to it -- or have we hard-forked it?

# MarinerOS 1.0 sets -fPIE in the hardening cflags
# (in the gcc specs file).
# This seems to break only this package and not other kernel packages.
%if "%{_vendor}" == "azl" || (0%{?rhel} >= 10) || (0%{?amzn} == 2023)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we certain this vendor macro lines up? This also won't work correctly for "stage1" (a.k.a. bootstrap) builds.

%global IS_RHEL_VENDOR "%{_vendor}" == "redhat" || ("%{_vendor}" == "bclinux") || ("%{_vendor}" == "openEuler")
%global KMOD_PREAMBLE "%{_vendor}" != "openEuler"

# MarinerOS 1.0 sets -fPIE in the hardening cflags
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why references to Mariner 1?

%global non_kmp_pname %{_name}-modules

Summary: Infiniband HCA Driver
Name: mlnx-ofa_kernel
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this still be the name of the package (i.e., with mlnx as a prefix)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants