Driver branch adds region-specific performance profiles and 'regulatory configuration' telemetry field
The compliance perimeter moves from the border to the runtime
A driver and firmware release published to NVIDIA's developer download portal adds region-specific performance profiles selectable at install time and documents a telemetry field labeled 'regulatory configuration' that reports which profile is active. The release notes state profiles are 'validated per jurisdiction' and that migrating a workload between profiles requires a restart of the serving stack; no performance deltas between profiles are published. Two community trackers noted the profile count differs by driver branch and that one profile present in the previous branch is absent from the current release, replaced in the migration table by a differently named identifier. The notes reference a compatibility matrix that lists five suffixes for the same part number. A footnote states that telemetry is exposed to 'authorized support channels,' without defining the term. The portal page carries a revision timestamp two days after the release itself.
Region-specific profiles and a regulatory configuration telemetry field are compliance-by-design reaching the runtime layer. One profile disappearing between branches, and five suffixes for a part number, describe a market matrix managed in firmware.
The audit trail is now shipping in the runtime. Nobody builds compliance telemetry before the conversation with the regulator, and nobody quietly removes a profile between branches unless a market moved.
- Region-specific performance profiles selectable at install, 'validated per jurisdiction'
- New telemetry field reports the active 'regulatory configuration'
- Profile set differs by branch; one profile absent from the current release
- Compatibility matrix lists five suffixes for the same part number; telemetry scope undefined