Repository navigation
Add kernel-next and supporting packages - #621
Conversation
43d1142 to
764f99f
Compare
kernel-next and supporting packages
31efe97 to
cace382
Compare
|
You'll need to carry the patch added in #623 for |
|
|
||
| [Service] | ||
| Type=oneshot | ||
| ExecStart=/usr/bin/driverdog --modules-set nvidia-lts-open-gpu load-modules |
There was a problem hiding this comment.
Do we need ExecCondition=/usr/bin/ghostdog match-nvidia-driver open-gpu here similar to how we have it in the 580 nvidia packages?
There was a problem hiding this comment.
There's only open-gpu in r620 so we don't need to match the driver to the hardware.
|
|
||
| # Disable DAMON subsystem. We currently do not have a good use-case for DAMON. | ||
| # CONFIG_DAMON is not set | ||
|
|
There was a problem hiding this comment.
Do we need to set a maximum for CMA_AREAS similar to how we have it here?
There was a problem hiding this comment.
This is now the default upstream configuration. The config-full- files have CONFIG_CMA_AREAS=20
| ABORT_CUDA_JOBS_ON_FM_EXIT=1 | ||
|
|
||
| # Path to topology and database files. | ||
| TOPOLOGY_FILE_PATH=/usr/share/nvidia/nvswitch |
There was a problem hiding this comment.
Other files have this set to TOPOLOGY_FILE_PATH=/usr/share/nvidia/tesla/nvswitch, looking to make sure this is what were expecting
There was a problem hiding this comment.
Yeah. /usr/share/nvidia/nvswitch is the default installation path. I chose to keep it that way for the new 620 driver.
Use "LicenseRef-", not "LicenceRef-".
Use the same fabric manager and IMEX URLs as Cargo.toml, and the same IMEX file names.
Find the config-full file names from the files in the kernel package. Find the SRPM spec name from the kernel version, and stop if the SRPM does not have that spec. Give the aarch64 base config to the merge functions as an argument.
cace382 to
099f12d
Compare
|
Update to enable CI and add missing patch |
099f12d to
316b034
Compare
There was a problem hiding this comment.
this and the {-aarch64, -x86_64} custom configurations are identical to the 6.18 kernel's custom configurations that are now in the kernel-6.18-shared-configs pkg
Not a blocking comment for this PR but maybe a follow up to rearchitect that shared pkg and reuse it for the -next kernels, too. If we anticipate that 7.x kernel configs will diverge from the base 6.18 configs, then may not be necessary.
There was a problem hiding this comment.
Yeah. I debated doing this. I didn't mostly to leave the door open for 7.x custom configurations once we have a stable kernel. We'll have to do a full evaluation of newer features and see if there are any that Bottlerocket would benefit from
There was a problem hiding this comment.
I don't think we should merge 6.18 with 7.x configs. We should just keep shared configs along the same kernel family - not across.
7.x and newer kernels will introduce configurations that don't exist on other kernels that we might want to enable. Or we might want to try something new in 7.x that in 6.18 we can't because might impact existing users.
| Summary: NVIDIA %{tesla_major} GRID driver | ||
| Version: %{tesla_ver} | ||
| License: MIT AND GPL-2.0-only AND LicenceRef-NVIDIA-GRID-AWS-EULA | ||
| License: MIT AND GPL-2.0-only AND LicenseRef-NVIDIA-GRID-AWS-EULA |
8a89cc2 to
250dc28
Compare
|
Push to address comments |
2c17d75 to
005216a
Compare
This kernel follows the Amazon Linux minor updates. The build uses the Amazon Linux 2027 kernel7.2 SRPM. On aarch64, the kernel uses 64K pages. tools/latest-kernel-full-config.sh uses config-aarch64-64k and config-microcode-6-18 for kernel-next.
Build the EFA driver for kernel-next from the EFA installer, as kmod-6.18-efa does. kernel-next requires this package.
Add the NVIDIA R620 driver for kernel-next as the lts branch. This package builds only the open GPU kernel modules. The units load them on every boot, with no ghostdog check.
005216a to
9644a9e
Compare
Issue:
Related: #624
Description of changes:
This PR adds
kernel-next, a kernel that follows the Amazon Linux minor updates, twokmodpackages for it, and a change to the full-config tool. It also includes two small fixes to the existing NVIDIA drivers.kernel-nextis not an LTS kernel. The package name stays the same when the kernel moves to a new minor version, for example from 7.2 to 7.3. The build uses the Amazon Linux 2027kernel-7.2.13-17.148for now.What's new in
kernel-next:config-aarch64-64kfrom the SRPM. On x86_64, the kernel uses 4K pages.aws_fwflashdriver, so this kernel cannot mount FSx for Lustre file systems.fipsimage feature.What's new in
kmod-next-nvidia-r620:-directpackages. The fabric manager binaries are in the-teslasubpackage, and the topologies are in/usr/share/nvidia/nvswitch.Testing done:
make full-configgenerated the four kernel-next config-full files, two on an x86_64 host and two on an aarch64 host, with SDK v0.82.0.kernel-nextand the kmods in a custom AMI. Verified on actual hardware that:Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.