Add PrivateUse1 Tutotial on integrating a new backend to pytorch via PrivateUse1

[FFFrog]

Includes a tutorial on how to integrate a new backend to pytorch via PrivateUse1.

It should be added that the tutorial uses Ascend NPU as an example, this is because we think that using npu instead of foo might be clearer for users or developers. Of course, we can change it back to foo if there's any argument or concern

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/2526

• 📄 Preview Python docs built from this PR

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

⏳ No Failures, 15 Pending

As of commit 4da9c18 with merge base 420399d ():
💚 Looks good so far! There are no failures yet. 💚

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

[facebook-github-bot]

Hi @FFFrog!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[FFFrog]

@albanD, please have a look at this, thank you.

[albanD]

Content sounds good. Not sure why the CI is not working and would need to double check the rendered version.

[svekars]

Thanks so much! I added a few editorial suggestions. Let me know if you have any questions.

[FFFrog]

@svekars, thank you very much for your review, the new commit is ready, please take a look at it again :D

[svekars]

A couple more super tiny nits and we should be good to go. Also, make sure the generated HTML looks good here.

[FFFrog]

@svekars, the generated HTML looks fine to me, please help to check it, thanks.

[FFFrog]

@svekars Sorry to bother you.

The deadline for August 25th is coming soon. If there is anything else that needs to be modified, please contact me, and I will modify it immediately.

Thank you.

[svekars]

The tutorial looks good to me. We typically merge tutorials in support of a release feature on the day of the release, which is scheduled for October 4.

[FFFrog]

The tutorial looks good to me. We typically merge tutorials in support of a release feature on the day of the release, which is scheduled for October 4.

Thank you for your comments.

[FFFrog]

Sorry to bother @svekars, I made a new commit to fix a tiny nits and rebase at the same time, please help to start the workflow.