Skip to content

Conversation

@SS-JIA
Copy link
Contributor

@SS-JIA SS-JIA commented Dec 27, 2025

Stack from ghstack (oldest at bottom):

The qdq8ta_conv2d_activations correctness tests were failing because the GPU timing collection function was filtering out quantize_and_pack_4w4c and unpack_4w4c_and_dequantize shaders from timing measurements. For these tests, these shaders ARE the operations being tested, not overhead.

This change refactors shader filtering to be configurable per test case:

  • Added shader_filter member to TestCase class with getter/setter methods
  • Created kDefaultShaderFilter (filters layout conversions + quantization) for backward compatibility
  • Created kLayoutOnlyShaderFilter (filters only layout conversions) for tests where quantization is the primary operation
  • Updated collect_gpu_timing_us() to accept shader_filter parameter
  • Updated qdq8ta_conv2d_activations to use kLayoutOnlyShaderFilter

This allows tests to control what shaders are excluded from timing measurements based on what they're actually testing, while maintaining backward compatibility for all existing tests.

Differential Revision: D89832383

…igurable shader filtering

The qdq8ta_conv2d_activations correctness tests were failing because the GPU timing collection function was filtering out quantize_and_pack_4w4c and unpack_4w4c_and_dequantize shaders from timing measurements. For these tests, these shaders ARE the operations being tested, not overhead.

This change refactors shader filtering to be configurable per test case:
- Added shader_filter member to TestCase class with getter/setter methods
- Created kDefaultShaderFilter (filters layout conversions + quantization) for backward compatibility
- Created kLayoutOnlyShaderFilter (filters only layout conversions) for tests where quantization is the primary operation
- Updated collect_gpu_timing_us() to accept shader_filter parameter
- Updated qdq8ta_conv2d_activations to use kLayoutOnlyShaderFilter

This allows tests to control what shaders are excluded from timing measurements based on what they're actually testing, while maintaining backward compatibility for all existing tests.

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

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 27, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Cancelled Job, 1 Unrelated Failure

As of commit 753411a with merge base 9a30bd3 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

@meta-cla meta-cla 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 Dec 27, 2025
@github-actions
Copy link

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.

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 meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants