[XPU] log clean up for XPU platform

[yma11]

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Summary of Changes

Hello @yma11, I'm Gemini Code Assist¹! 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 primarily focuses on improving and refining the integration of the XPU platform within the vllm codebase. My changes address specific platform-dependent behaviors, such as conditionally loading custom operations and cleaning up logging practices. Most notably, I've enabled pin memory support for XPU, which can have a positive impact on performance.

Highlights

• XPU Platform Compatibility: I've updated vllm/_custom_ops.py to prevent the import of vllm._C (custom C++ operations) when running on an XPU platform. This aligns XPU with TPU and HPU, where these custom operations are also not loaded.
• Refined XPU Logging: In vllm/platforms/xpu.py, I've refined a logging condition within the get_attn_backend_cls method. The log message about backend incompatibility will now only be printed if selected_backend is not None, preventing unnecessary log noise.
• XPU Pin Memory Support: A significant change in vllm/platforms/xpu.py is the update to is_pin_memory_available. It now returns True, indicating that pin memory is supported on XPU, and the previous warning message stating it was not supported has been removed. This is a functional improvement for XPU.
• Code Formatting: A minor formatting fix was applied to vllm/platforms/xpu.py by adding a missing newline character at the end of the file.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request adds XPU platform support, including log clean up and enabling pinned memory. Review comments address code style, potential errors, and outdated information.

[gemini-code-assist]

Consider using parentheses for line continuation instead of a backslash for better readability and adherence to Python's style guidelines (PEP 8).

if not (current_platform.is_tpu() or
        current_platform.is_hpu() or
        current_platform.is_xpu()):

[gemini-code-assist]

Consider checking if selected_backend is None before accessing it to avoid a potential AttributeError if it's unexpectedly None.

if selected_backend is not None and selected_backend != _Backend.IPEX:

[gemini-code-assist]

The warning message stating that pin memory is not supported on XPU is no longer accurate, as this change enables pin memory. Consider removing the warning to avoid confusion.

return True