-
Notifications
You must be signed in to change notification settings - Fork 345
Add --disable-hook flag to cdi generate command #1077
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new CLI flag (--skip-hooks) to allow users to opt out of specific hooks when generating the CDI specification.
- Updated tests to include a skip-hook option.
- Modified the command initialization and spec generation logic to support disabling hooks based on the provided flag.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
File | Description |
---|---|
cmd/nvidia-ctk/cdi/generate/generate_test.go | Added a test case to validate the skip-hook functionality and updated expected spec/options accordingly. |
cmd/nvidia-ctk/cdi/generate/generate.go | Introduced a new CLI flag and added logic to disable hooks based on user input. |
Comments suppressed due to low confidence (1)
cmd/nvidia-ctk/cdi/generate/generate_test.go:40
- [nitpick] The variable name 'skipdHook' may be a typo and could be renamed to 'skipHook' for consistency and clarity.
skipdHook := cli.NewStringSlice("enable-cuda-compat")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds support for a new flag (--skip-hooks) to the nvidia-ctk cdi generate command so that users can opt out of specific hooks when creating the CDI spec.
- In generate.go, a new skipHook option and corresponding CLI flag are introduced and processed when creating CDI library options.
- In generate_test.go, a new test case verifies the behavior when a non-default hook is skipped.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
cmd/nvidia-ctk/cdi/generate/generate_test.go | Added test case for --skip-hooks flag and its effect. |
cmd/nvidia-ctk/cdi/generate/generate.go | Introduced skipHook flag and integrated it into initialization options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new flag --skip-hooks to the cdi generate command to allow users to disable specific hooks while generating the CDI specification.
- Introduces a new CLI flag in generate.go to capture the hooks to skip
- Updates the options struct and test cases in generate_test.go to include and validate the new skipHook functionality
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
cmd/nvidia-ctk/cdi/generate/generate_test.go | Adds a test case for skipHook using a new CLI string slice |
cmd/nvidia-ctk/cdi/generate/generate.go | Registers the new --skip-hook flag and passes the provided hooks to disable options during CDI spec generation |
Comments suppressed due to low confidence (1)
cmd/nvidia-ctk/cdi/generate/generate_test.go:40
- [nitpick] Consider adding a test case to verify that when a hook name is provided via skipHook, the generated CDI specification omits or disables that hook, ensuring the new flag's functionality is fully verified.
skipHook := cli.NewStringSlice("enable-cuda-compat")
@@ -176,6 +177,12 @@ func (m command) build() *cli.Command { | |||
Usage: "Specify a pattern the CSV mount specifications.", | |||
Destination: &opts.csv.ignorePatterns, | |||
}, | |||
&cli.StringSliceFlag{ | |||
Name: "skip-hook", | |||
Usage: "Comma-separated list of hooks to skip when generating the CDI specification.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically the flag can also be specified multiple times.
@@ -57,6 +57,7 @@ type options struct { | |||
|
|||
configSearchPaths cli.StringSlice | |||
librarySearchPaths cli.StringSlice | |||
skipHook cli.StringSlice |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be:
skipHook cli.StringSlice | |
skipHooks cli.StringSlice |
Since it contains 0 or more entries.
if len(opts.skipHook.Value()) > 0 { | ||
for _, hook := range opts.skipHook.Value() { | ||
initOpts = append(initOpts, nvcdi.WithDisabledHook(nvcdi.HookName(hook))) | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we want to check for validity of the names, or do we want to add that as a follow-up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's hold this PR until:
- Ensure that libcuda.so is in the ldcache #947
- Disable device node creation in CDI mode #927
get in, then I will think on how to add a name check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's hold this PR until:
Should this PR not just work automatically with those PRs -- assuming those hooks can be opted out of using the same option?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It now allows for disabling all hooks
@@ -176,6 +177,12 @@ func (m command) build() *cli.Command { | |||
Usage: "Specify a pattern the CSV mount specifications.", | |||
Destination: &opts.csv.ignorePatterns, | |||
}, | |||
&cli.StringSliceFlag{ | |||
Name: "skip-hook", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about disable-hook
(we could even add an alias as disable-hooks
) instead? Thinking ahead, it may be useful to allow users to do something like:
nvidia-ctk cdi generate \
--disable-hook=update-ldcache \
--disable-hook=enable-cuda-compat \
--mode=nvml
Even further forward, more conservative users may want to consider:
nvidia-ctk cdi generate --disable-hooks=all
although that is out of scope of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds support for a new flag that allows users to disable specific hooks during the CDI spec generation. Key changes include:
- Adding conditional logic to check for supported hooks in the NVML driver library.
- Introducing the new CLI flag (and corresponding option) to allow disabling hooks.
- Updating tests to reflect the new --disable-hook(s) functionality.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
File | Description |
---|---|
pkg/nvcdi/driver-nvml.go | Wraps hook-based discoverer creation in conditionals based on hook support. |
cmd/nvidia-ctk/cdi/generate/generate_test.go | Adds test cases and sample disable-hook values in accordance with the new functionality. |
cmd/nvidia-ctk/cdi/generate/generate.go | Introduces a new flag and integrates hook disabling into the initialization options. |
Comments suppressed due to low confidence (1)
cmd/nvidia-ctk/cdi/generate/generate.go:181
- [nitpick] Consider renaming the flag from "disable-hook" to "disable-hooks" to match the PR title and description for consistency.
Name: "disable-hook",
When running the nvidia-ctk cdi generate command, a user should be able to opt out of specific hooks. We propose to add a flag --disable-hook that will take a comma-separated list of hooks that will be skipped when creating the CDI spec. Signed-off-by: Carlos Eduardo Arango Gutierrez <[email protected]>
Signed-off-by: Carlos Eduardo Arango Gutierrez <[email protected]>
Signed-off-by: Carlos Eduardo Arango Gutierrez <[email protected]>
When running the
nvidia-ctk cdi generate
command, a user should be able to opt out of specific hooks. We propose to add a flag --disable-hooks that will take a comma-separated list of hooks that will be skipped when creating the CDI spec.Fixes: #1074