fix jamba slow foward for multi-gpu #30418
Merged
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do ?
This PR makes the slow forward of Jamba model compatible with multi-gpu setup with use_cache=True. The issue is that the cache is not initialized on the right device. Not sure we want to refactor the cache since the
key_cache
and andvalue_cache
are handled correctly. This is just specific tossm_states
. Moving the tensor manually should only impact the first forward also. After the first forward, the cache will be correctly initialized.Fixes #30367
Code: