Skip to content

[TIRx][CUDA] Allow newer CUTLASS packages for IKET - #20164

Open
jinhongyii wants to merge 1 commit into
apache:mainfrom
jinhongyii:fix/iket-cutlass-minimum-version
Open

[TIRx][CUDA] Allow newer CUTLASS packages for IKET#20164
jinhongyii wants to merge 1 commit into
apache:mainfrom
jinhongyii:fix/iket-cutlass-minimum-version

Conversation

@jinhongyii

Copy link
Copy Markdown
Contributor

The official IKET profile currently requires the CUTLASS packages to be exactly version 4.6.0 and locks their runtime files by hash. This rejects newer package releases such as 4.6.2 even when they retain the supported run-iket interface.

This change represents CUTLASS requirements as minimum versions and accepts releases at or above 4.6.0. It preserves the existing exact nvidia-cuda-nvrtc and nvidia-cuda-nvdisasm package requirements and the NVRTC runtime check. Binary hash pinning is removed, while the run-iket entry point and injected environment structure continue to be validated.

Testing:

  • pre-commit run --files python/tvm/backend/cuda/iket.py tests/python/tirx/iket/test_iket_profiler.py
  • python -m pytest tests/python/tirx/iket/test_iket_profiler.py tests/python/tirx/iket/test_iket_orchestration.py -q (71 passed, 2 skipped)
  • Local installation validation with CUTLASS 4.6.2, NVDisasm 13.3.73, and NVRTC 13.2.78/runtime 13.2

The official IKET profile currently pins CUTLASS 4.6.0 package versions and binary hashes, which rejects newer CUTLASS installations even when they retain the supported interface.\n\nTreat the four CUTLASS packages as requiring version 4.6.0 or newer while preserving the existing exact NVRTC and NVDisasm requirements. Remove binary hash pinning, and cover the minimum-version boundary in the installation validation tests.
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.

1 participant