[quant][improvement] Check the fixedqparam op qconfig based on backend_config

[jerryzh168]

Stack from ghstack (oldest at bottom):

• -> [quant][improvement] Check the fixedqparam op qconfig based on backend_config #87425

Summary:
Previously we hardcoded the supported observers for fixedqparam ops, this PR changes that to take the information from BackendConfig,
this allows users to customize the support for fixed qparam ops

Test Plan:
python test/test_quantization.py TestQuantizeFx.test_change_backend_config_for_fixed_qparam_ops

Reviewers:

Subscribers:

Tasks:

Tags:

unlinked from diff since it's too hard to land

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

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

❌ 1 Failures

As of commit 617f19f:

The following jobs have failed:

• linux-bionic-py3.7-clang9 / test (dynamo, 2, 2, linux.2xlarge)

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

[jerryzh168]

@jerryzh168 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[andrewor14]

I guess what's happening in this test is more like "ensure we skip validation for fixed qparams ops since backend config doesn't support anything"?

[jerryzh168]

Yes, I can change the comment for the test

[jerryzh168]

@pytorchbot merge -g

[pytorchmergebot]

Merge failed

Reason: This PR has internal changes and must be landed via Phabricator

Details for Dev Infra team

Raised by workflow job

[jerryzh168]

@jerryzh168 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[jerryzh168]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot successfully started a rebase job. Check the current status here

[pytorchmergebot]

Tried to rebase and push PR #87425, but it was already up to date

[jerryzh168]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot successfully started a rebase job. Check the current status here

[pytorchmergebot]

Successfully rebased gh/jerryzh168/807/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/87425)

[jerryzh168]

@pytorchbot merge

[pytorchmergebot]

Merge failed

Reason: This PR has internal changes and must be landed via Phabricator

Details for Dev Infra team

Raised by workflow job

[jerryzh168]

@pytorchbot merge -f "not sure why this can't land"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: This PR has internal changes and must be landed via Phabricator

Details for Dev Infra team

Raised by workflow job

[jerryzh168]

@jerryzh168 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[jerryzh168]

@pytorch merge -f "failing test doesn't seem related"

[jerryzh168]

@pytorchbot merge -f "failing test doesn't seem related"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: The following mandatory check(s) are pending/not yet run (Rule superuser):

• EasyCLA

Dig deeper by viewing the pending checks on hud

Details for Dev Infra team

Raised by workflow job

[jerryzh168]

@pytorchbot merge -f "failing test doesn't seem related"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: The following mandatory check(s) are pending/not yet run (Rule superuser):

• EasyCLA

Dig deeper by viewing the pending checks on hud

Details for Dev Infra team

Raised by workflow job

[bigfootjon]

/easycla

[jerryzh168]

@pytorchbot merge -f "failing test doesn't seem related"

[seemethere]

@pytorchbot merge -f "failing test doesn't seem related"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @jerryzh168.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.