Jiong Gong c58d0ad85d Propose Out-of-tree Backend Integration (PrivateUse1) as a module and FFFrog as the maintainer (#165958) ... I'd like to propose a new module `Out-of-tree Backend Integration` via `PrivateUse1` device key. The out-of-tree backend integration via `PrivateUse1` device key has been a recommended mechanism of plug-in third-party accelerator devices into PyTorch. There are already quite a few documents/tutorials on the usage with the primary one as https://docs.pytorch.org/docs/main/accelerator/index.html. We also saw more and more HW vendors to leverage the `PrivateUse1` mechanism to support their accelerators. For example: 1. Ascend NPU 2. Microsoft MAIA 3. MooreThreads MUSA 4. Cambricon MLU The scope of `PrivateUse1` based out-of-tree backend integration is composed of two parts: 1. `PrivateUse1` device as an out-of-tree backend that involves: (a) make `PrivateUse1` a function-complete device as other in-tree devices: i.e., device runtime, autograd, autocast, profiling, distributed, quantization etc. (b) a pluggable design to allow out-of-tree integration to extend the functionality of `PrivateUse1` such as a backend registration mechanism that allows user-friendly device naming, runtime extension points with either C++ and Python for third-party to plug-in their runtime implementation, customizable tensor implementation for third-party to add extra info/functionality to the tensor and their serialization. 2. OpenReg: A test suite and documentation effort to guarantee the functional correctness of `PrivateUse1` mechanism and to guide HW vendors with the right implementation. I'm also proposing @FFFrog as the module maintainer for this new module due to his continuous contribution to the design and implementation both parts of the module. Below are the RFCs/Feature Proposals @FFFrog was working on: 1. [An improvement of PrivateUse1 mechanism, facilitating third-party backend integration](https://docs.google.com/document/d/1_2EO5A2Ww3xDwqbhIvs9Nk65-jV0oNYg3XAmNUsHdAY/edit?tab=t.0#heading=h.5vt8c1vo4dc7) 2. [The interoperability Standard of Third-party Backend Integration Mechanism](9bd181e742/RFC-0037-Interoperability-Standard-of-3rd-Backend-Integration-Mechanism.md) 3. [PyTorch Backend Accelerator Integration Verification and Guidance](f6048cbd4f/RFC-0045-PyTorch-Accelerator-Integration-Enhancements.md) @FFFrog contributed 240+ PRs and a majority of them is related to `PrivateUse1`. (https://github.com/pytorch/pytorch/pulls?q=is%3Apr+author%3Afffrog+). He also reviewed 50+ PRs related to this area. He is also the primary author of OpenReg. Pull Request resolved: https://github.com/pytorch/pytorch/pull/165958 Approved by: https://github.com/albanD, https://github.com/malfet, https://github.com/ezyang		2025-10-27 05:00:15 +00:00
..
build_ci_governance.rst	Migrate to new theme (#149331)	2025-04-16 21:35:19 +00:00
contribution_guide.rst	Fix broken URLs (#152237)	2025-04-27 09:56:42 +00:00
design.rst	Migrate to new theme (#149331)	2025-04-16 21:35:19 +00:00
governance.rst	Migrate to new theme (#149331)	2025-04-16 21:35:19 +00:00
index.rst	Clean up right nav (#153090)	2025-05-12 21:00:45 +00:00
persons_of_interest.rst	Propose Out-of-tree Backend Integration (PrivateUse1) as a module and FFFrog as the maintainer (#165958)	2025-10-27 05:00:15 +00:00