Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix unset version in structs #139

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Conversation

elezar
Copy link
Member

@elezar elezar commented Jan 9, 2025

This change ensures that the Version field is set in structs that require them.

This addresses the following calls:

  • DeviceGetRunningProcessDetailList
  • DeviceGetPciInfoExt
  • DeviceGetVgpuHeterogeneousMode
  • DeviceGetSupportedPlacements
  • DeviceGetCreatablePlacements
  • DeviceGetVgpuProcessesUtilizationInfo
  • DeviceGetSramEccErrorStatus
  • SystemGetConfComputeKeyRotationThresholdInfo
  • SystemGetConfComputeSettings

This replaces replace #130

fixes #138

This change ensures that the Version field is set in structs that require
them.

This addresses the following calls:
* DeviceGetRunningProcessDetailList
* DeviceGetPciInfoExt
* DeviceGetVgpuHeterogeneousMode
* DeviceGetSupportedPlacements
* DeviceGetCreatablePlacements
* DeviceGetVgpuProcessesUtilizationInfo
* DeviceGetSramEccErrorStatus
* SystemGetConfComputeKeyRotationThresholdInfo
* SystemGetConfComputeSettings

Signed-off-by: Evan Lezar <[email protected]>
@elezar elezar self-assigned this Jan 9, 2025
@klueska
Copy link
Contributor

klueska commented Jan 9, 2025

How did you evaluate which functions needed this to ensure we didn't miss any?

@elezar
Copy link
Member Author

elezar commented Jan 9, 2025

How did you evaluate which functions needed this to ensure we didn't miss any?

I searched the generated types for Version fields and searched for declarations of the variable types. I think we could automate this to ensure that we don't miss any in future. Do we think it's worth the overhead?

@klueska
Copy link
Contributor

klueska commented Jan 9, 2025

Not worth the overhead yet, I'd say, but need to watch out for this as new functions / types get added from release to release

@elezar elezar merged commit 8a7f6b7 into NVIDIA:main Jan 9, 2025
4 checks passed
@elezar elezar deleted the fix-get-sram-ecc-status branch January 9, 2025 13:12
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.

GetSramEccErrorStatus() returned an error status of 'Argument version mismatch'
2 participants