Quant doc updates

[metascroy]

Initial draft of quantization doc updates (#10603)

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 15 Pending

As of commit dd47664 with merge base 9d599c9 ():

NEW FAILURES - The following jobs have failed:

• Build Presets / zephyr (zephyr) / build (gh)
  RuntimeError: Command docker exec -t c0de2dbf6d0e713d48749f2bf5491bc618056281c2db4d2e7f83b0bc1d9fa4ff /exec failed with exit code 1
• pull / unittest / linux / linux-job (gh)
  backends/xnnpack/test/ops/test_gelu.py::TestGelu::test_fp16_gelu
• pull / unittest-editable / linux / linux-job (gh)
  backends/xnnpack/test/ops/test_gelu.py::TestGelu::test_fp16_gelu

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[GregoryComer]

Looks great. Thanks for updating this.

[metascroy]

@jerryzh168 can you give the changes a look over too?

[jerryzh168]

nit: I think Configure would be more accurate

[jerryzh168]

nit: link to docs as well?

[jerryzh168]

makes sense, wondering if we want to connect with transformer (or optimum-executorch?) as well, like what we did in https://docs.pytorch.org/ao/main/serving.html

[metascroy]

makes sense, wondering if we want to connect with transformer (or optimum-executorch?) as well, like what we did in https://docs.pytorch.org/ao/main/serving.html

The LLM doc overhaul is separate

[metascroy]

@pytorchbot cherry-pick --onto release/0.7 -c docs

[pytorchbot]

Cherry picking #12240

The cherry pick PR is at #12260 The following tracker issues are updated:

• [v0.7.0] Release Tracker #11075 (comment)

Details for Dev Infra team

Raised by workflow job

[metascroy]

@pytorchbot cherry-pick --onto release/0.7 -c “docs”

[pytorch-bot]

❌ 🤖 pytorchbot command failed:

@pytorchbot cherry-pick: error: argument -c/--classification: invalid choice: '“docs”' (choose from 'regression', 'critical', 'fixnewfeature', 'docs', 'release')

usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c
                               {regression,critical,fixnewfeature,docs,release}

Try @pytorchbot --help for more info.