-
-
Notifications
You must be signed in to change notification settings - Fork 10k
[xpu]feat: support multi-lora on xpu #20616
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
Conversation
Signed-off-by: yan <yan.ma@intel.com>
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.
Summary of Changes
Hello @yma11, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces comprehensive support for multi-LoRA functionality on the XPU platform. It involves adapting core LoRA operations for platform-specific dispatch, refining tensor handling for multiple LoRA weights, and enabling XPU-aware model deserialization. The changes also include XPU-specific configurations and a temporary workaround to ensure stability with torch.compile
.
Highlights
- XPU LoRA Operations Dispatching: Modified
lora_expand_op.py
andlora_shrink_op.py
to usecurrent_platform.dispatch_key
when registering custom operations. This enables platform-specific implementations for LoRA expand and shrink operations, crucial for XPU compatibility. - Multi-LoRA Pointer Handling Improvement: Updated
utils.py
to explicitly cast tensor pointers and slice offsets totorch.uint64
when creating tensors for multiple LoRA weights. This change enhances robustness and precision, particularly important for memory addressing on XPU. - XPU Model Deserialization Support: Adjusted
tensorizer.py
to dynamically select the appropriate device (xpu
orcuda
) during model deserialization. This ensures that models are loaded onto the correct hardware platform based oncurrent_platform.is_xpu()
. - XPU Platform Configuration and Workarounds: Added a
get_punica_wrapper
method toxpu.py
to specify the Punica wrapper path for XPU. Additionally, a temporary measure was introduced to disabletorch.compile
(forcing eager mode) for XPU under specific conditions, addressing current stability considerations with compilation on the platform.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request introduces multi-LoRA support for the XPU platform. My feedback focuses on improving code style and readability for better maintainability.
device=f'xpu:{torch.xpu.current_device()}' | ||
if current_platform.is_xpu() else | ||
f'cuda:{torch.cuda.current_device()}', |
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.
vllm/platforms/xpu.py
Outdated
if envs.VLLM_USE_V1 and vllm_config.model_config is not None and \ | ||
not vllm_config.model_config.enforce_eager: |
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.
Use parentheses for grouping expressions over multiple lines to improve readability and avoid potential issues with trailing whitespace.
if envs.VLLM_USE_V1 and vllm_config.model_config is not None and \ | |
not vllm_config.model_config.enforce_eager: | |
if (envs.VLLM_USE_V1 and vllm_config.model_config is not None and | |
not vllm_config.model_config.enforce_eager): |
vllm/platforms/xpu.py
Outdated
vllm_config.compilation_config.level = \ | ||
CompilationLevel.NO_COMPILATION |
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.
Signed-off-by: yan <yan.ma@intel.com>
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
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.
Considering that these changes are mostly only related to XPU, we can merge after the CI is all green
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com> Signed-off-by: Patrick von Platen <patrick.v.platen@gmail.com>
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com> Signed-off-by: avigny <47987522+avigny@users.noreply.github.com>
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com> Signed-off-by: Jinzhen Lin <linjinzhen@hotmail.com>
Signed-off-by: yan <yan.ma@intel.com>
Signed-off-by: yan <yan.ma@intel.com>
This PR enables multi-lora support on xpu platform, passing UT like
pytest -s -v tests/lora/test_quant_model.py