Skip to content

Add XPU guidance for register-spill-aware autotune pruning to the `xp… - #690

Merged
sayakpaul merged 2 commits into
huggingface:mainfrom
sywangyi:register-spill-aware
Jul 15, 2026
Merged

sayakpaul merged 2 commits into
huggingface:mainfrom
sywangyi:register-spill-aware

Conversation

@sywangyi

@sywangyi sywangyi commented Jul 6, 2026 •

Copy link
Copy Markdown
Contributor

…u-kernels` skill.

This PR extends the XPU kernel optimization skill with a new pattern for pruning Triton autotune configurations that are likely to spill registers on Intel XPU. The existing Xe-Forge workflow already detects register spills through profiling and recommends GRF/liveness mitigations; this change adds a proactive pruning strategy that can reduce wasted compile and benchmark time for obviously spill-prone configs.

Important: Read before submitting

New contributors: Please open or comment on an issue before submitting a
PR to discuss the change you'd like to make. This helps us align on approach and
avoids wasted effort on changes we may not be able to merge. Please only create
a PR once one of the project maintainers agrees on your outlined approach.

PRs of contributors who are not vouched for are automatically closed. Regular
contributors are added to the vouch list.

For, LLM-generated changes, we prefer that you write your prompt in an issue
over a PR with LLM-generated changes.

Related issue

Closes #

What does this PR do?

Motivation

Changes

Testing

Checklist

  • This PR is linked to an issue that was discussed and approved
  • I have tested these changes locally
  • New/changed functionality has test coverage
  • LLM disclosure:
    • I did not use an LLM to create this PR.
    • I used and LLM for assistance while creating this PR.
    • This PR was mostly or completely generated by an LLM.

…u-kernels` skill.

This PR extends the XPU kernel optimization skill with a new pattern for pruning Triton autotune configurations that are likely to spill registers on Intel XPU. The existing Xe-Forge workflow already detects register spills through profiling and recommends GRF/liveness mitigations; this change adds a proactive pruning strategy that can reduce wasted compile and benchmark time for obviously spill-prone configs.

Signed-off-by: Wang, Yi A <yi.a.wang@intel.com>
@sywangyi

sywangyi commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

@IlyasMoutawwakil please help review

@drbh drbh left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me, but happy to take another look if this is updated/edited

@sayakpaul
sayakpaul merged commit 690cd70 into huggingface:main Jul 15, 2026
36 of 39 checks passed
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.

4 participants