-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
add code for intel qlora #3370
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
Merged
danielhanchen
merged 2 commits into
unslothai:main
from
leizhenyuan:zhenyuan_intel_enable_qlora
Oct 27, 2025
Merged
add code for intel qlora #3370
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Small nit. In this case both HAS_CUDA_STREAM and HAS_XPU_STREAM could be True. For clarity it would be good to make sure it's one or the other.
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.
I think it's OK since it's really just talking about the API and not the device availability. Maybe the naming doesn't explain that well enough. But in this case, the bitsandbytes C API requires stream arguments on some functions for both CUDA/XPU.
But to be honest, separate from this PR, I would suggest bumping the minimum bitsandbytes version for CUDA to at least
>=0.45.0. Ideally>=0.46.0to ensuretorch.compilecompatibility. If that's done thenHAS_CUDA_STREAMandHAS_XPU_STREAMparts can be completely removed. (It's always true for>=0.44.0).For Blackwell, the minimum bitsandbytes needed would be
>=0.45.3.For Intel, the minimum bitsandbytes should be
>=0.48.0.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.
Actually, since I see in pyproject.toml that Unsloth already pins to
bitsandbytes>=0.45.5, the checks aroundHAS_CUDA_STREAMcan be removed already.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.
Shall we create a new pr for removing HAS_CUDA_STREAM instead of this pr?