NVIDIA: VR: SAUCE: Introduce full.config and full-64k.config

[jamieNguyenNVIDIA]

Introduce full.config and full-64k.config files:

• full.config: Full config (nvidia-6.17 + generic-6.18 new options, env excluded). Deduplicated so options already in nvidia.config are omitted. Merge with nvidia.config to build.

• full-64k.config: 64K page size variant of full.config. Same dedup rule. 64K-related options taken from nvidia-6.17-64k reference (page size, PGTABLE_LEVELS, VA/PA bits, ARCH_MMAP_RND, etc.).

[jamieNguyenNVIDIA]

The full configs were generated using the following formula:

• config-6.17.0-1008-nvidia from noble + config-6.18.0-9-generic from resolute
• stripped out environment-based configs
• deduplicated configs that were already in nvidia.config
• set a few additional ones to keep ensure the compilation was prompt-less

[arighi]

LGTM.

To verify this I tried to re-generate the configs using noble:linux-nvidia-6.17 as a baseline + the configs from the latest resolute:linux kernel from Ubuntu for the new options and I produced similar results.

A general comment (not specific to this PR): it would be nice to have a reference (nvbug / LP bug / generic URL) for each NVIDIA option defined in arch/arm64/configs/nvidia.config. Some configs already include an LP bug (which is great), while others only have a brief comment. Sometimes having a proper reference makes much easier to understand the full context and rationale behind enabling (or disabling) a particular option. Maybe something to keep in mind for the future configs.

[nvmochs]

@jamieNguyenNVIDIA

Previously (with just nvidia.confg) we were saying to merge defconfig + nvidia.confg. Because of that, I think we concluded that we did not need to add "CONFIG_NVIDIA_TEGRA410_CMEM_LATENCY_PMU=m" to nvidia.config. However since we'd now be recommending to merge the full*.config + nvidia.config, I think we need to sure that any defconfig items that we want are captured in either full*.config or nvidia.config. i.e. we need to add CONFIG_NVIDIA_TEGRA410_CMEM_LATENCY_PMU=m to nvidia.config. I looked at others but this was the one that stood out.

I assume we'd need to potentially refresh full*.config when stable updates are applied? We might want to capture that methodology in the commit message.

[jamieNguyenNVIDIA]

@jamieNguyenNVIDIA

Previously (with just nvidia.confg) we were saying to merge defconfig + nvidia.confg. Because of that, I think we concluded that we did not need to add "CONFIG_NVIDIA_TEGRA410_CMEM_LATENCY_PMU=m" to nvidia.config. However since we'd now be recommending to merge the full*.config + nvidia.config, I think we need to sure that any defconfig items that we want are captured in either full*.config or nvidia.config. i.e. we need to add CONFIG_NVIDIA_TEGRA410_CMEM_LATENCY_PMU=m to nvidia.config. I looked at others but this was the one that stood out.

I assume we'd need to potentially refresh full*.config when stable updates are applied? We might want to capture that methodology in the commit message.

Good points.

I'll add CONFIG_NVIDIA_TEGRA410_CMEM_LATENCY_PMU to nvidia.config. I believe this is the only one missing.

And instead of hand-crafting the full.config/full-64k.config, I'll check in a script that can regenerate these files when given the right configs (i.e. config-6.17.0-1008-nvidia + config-6.18.0-9-generic or config-6.17.0-1008-nvidia-64k + config-6.18.0-9-generic-64k)

[nvmochs]

Thanks Jamie for the script - that will help with future updates!

I confirmed that using the script and example provided in the commit message generates the full configs that are added by this commit.

Acked-by: Matthew R. Ochs <mochs@nvidia.com>