Currently, kernel launcher searches for wisdom files based on the exact name of the GPU in the system. This is strict and poses a problem when dealing with GPUs that share similar architectures but have slightly different names (e.g., RTX 4000 vs RTX 4500).
A potential solution would be to allow users to specify a 'virtual' GPU model. This could be implemented through an environment variable, such as KERNEL_LAUNCHER_GPU_NAME="RTX 4500". By setting this variable, users can inform kernel launcher to act like it contains a GPU of a different name.
Currently, kernel launcher searches for wisdom files based on the exact name of the GPU in the system. This is strict and poses a problem when dealing with GPUs that share similar architectures but have slightly different names (e.g., RTX 4000 vs RTX 4500).
A potential solution would be to allow users to specify a 'virtual' GPU model. This could be implemented through an environment variable, such as KERNEL_LAUNCHER_GPU_NAME="RTX 4500". By setting this variable, users can inform kernel launcher to act like it contains a GPU of a different name.