Skip to content

[ET-VK][ez] Store physical device identity metadata #10353

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
merged 2 commits into from
Apr 22, 2025

Conversation

SS-JIA
Copy link
Contributor

@SS-JIA SS-JIA commented Apr 22, 2025

Stack from ghstack (oldest at bottom):

Context

Lay the groundwork for storing device identity metadata. This will allow operator implementations to select and/or configure compute shaders based on the GPU that is being used.

Differential Revision: D73438723

## Context

Lay the groundwork for storing device identity metadata. This will allow operator implementations to select and/or configure compute shaders based on the GPU that is being used.

Differential Revision: [D73438723](https://our.internmc.facebook.com/intern/diff/D73438723/)

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Apr 22, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/10353

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit 809fee4 with merge base 95c663e (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

SS-JIA added a commit that referenced this pull request Apr 22, 2025
## Context

Lay the groundwork for storing device identity metadata. This will allow operator implementations to select and/or configure compute shaders based on the GPU that is being used.

Differential Revision: [D73438723](https://our.internmc.facebook.com/intern/diff/D73438723/)

ghstack-source-id: 279540367
Pull Request resolved: #10353
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 22, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D73438723

## Context

Lay the groundwork for storing device identity metadata. This will allow operator implementations to select and/or configure compute shaders based on the GPU that is being used.

Differential Revision: [D73438723](https://our.internmc.facebook.com/intern/diff/D73438723/)

[ghstack-poisoned]
SS-JIA added a commit that referenced this pull request Apr 22, 2025
Pull Request resolved: #10353

## Context

Lay the groundwork for storing device identity metadata. This will allow operator implementations to select and/or configure compute shaders based on the GPU that is being used.

Differential Revision: [D73438723](https://our.internmc.facebook.com/intern/diff/D73438723/)
ghstack-source-id: 279563504
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D73438723

@SS-JIA SS-JIA added the release notes: vulkan Changes to the Vulkan backend delegate label Apr 22, 2025
@facebook-github-bot facebook-github-bot merged commit b48452a into gh/SS-JIA/218/base Apr 22, 2025
83 of 88 checks passed
@facebook-github-bot facebook-github-bot deleted the gh/SS-JIA/218/head branch April 22, 2025 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported release notes: vulkan Changes to the Vulkan backend delegate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants