Skip to content

fix(qwen-asr): select Intel XPU devices - #11539

Open
localai-org-maint-bot wants to merge 1 commit into
masterfrom
cron/fix-8934-qwen-asr-xpu-20260815
Open

fix(qwen-asr): select Intel XPU devices#11539
localai-org-maint-bot wants to merge 1 commit into
masterfrom
cron/fix-8934-qwen-asr-xpu-20260815

Conversation

@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator

Description

This PR fixes #8934.

The Intel qwen-asr image already installs PyTorch XPU wheels, but the backend only selected CUDA, MPS, or CPU. It now detects an available XPU, uses BF16, and places the model on xpu:0. CUDA, MPS, and CPU selection remain unchanged.

Notes for Reviewers

The regression suite uses a small torch availability stub, so it verifies device selection and placement without a model download or GPU runner.

Verification:

  • python3 -m unittest discover -s backend/python/qwen-asr -p "*_test.py"
  • python3 -m py_compile backend/python/qwen-asr/backend.py backend/python/qwen-asr/device_utils.py backend/python/qwen-asr/device_utils_test.py
  • git diff --check

Signed commits

  • Yes, I signed my commits.
  • Documentation updated (docs/content/) for user-facing changes, or not applicable

Documentation is not applicable because this restores the existing Intel backend behavior and adds no API, CLI, or configuration surface.

The Intel backend installs PyTorch XPU wheels, but Qwen ASR only
checked CUDA and MPS. Every Intel model therefore loaded on the CPU.

Select XPU when available and place the model on xpu:0. Keep the
existing CUDA, MPS, and CPU placement behavior.

Assisted-by: Codex:GPT-5 [apply_patch] [gh]
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.

Intel GPU is not utilized by intel-qwen-asr

1 participant