Skip to content

Add additional checks for operator support. #8367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

Erik-Lundell
Copy link
Collaborator

@Erik-Lundell Erik-Lundell commented Feb 11, 2025

This can be used to avoid partitioning parts
of a model when debugging.

Though any OperatorSupportBase can be used, we add three OperatorSupport as utilities:

  • DontPartition: Don't partition based on node target
  • DontPartitionName: Don't partition based on node name
  • DontPartitionModule: Don't partition based on which module the op comes from.

All these checks can match parts of the target name, and save a list of the nodes they reject for debugging.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

This seems to match the intention of OperatorSupportBase
and increases the flexibility of our support flow.
New checks if different kinds are simply added
to `tosa_support_factory`

Signed-off-by: Erik Lundell <[email protected]>
Change-Id: I4f5f1669959f35c5e2770da396a352e1730cb3e0
This can be used to avoid partitioning parts
of a model when debugging.

Though any OperatorSupportBase can be used,
we add three OperatorSupport as utilities:
DontPartition: Don't partition based on node target
DontPartitionName: Don't partition based on node name
DontPartitionModule: Don't partition based on which module
the op comes from.

All these checks can match parts of the target name,
and save a list of the nodes they reject for debugging.

Signed-off-by: Erik Lundell <[email protected]>
Change-Id: I0b2537370da4aadcffbb87c52cb98e82d78cf27f
@Erik-Lundell Erik-Lundell added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk topic: not user facing labels Feb 11, 2025
Copy link

pytorch-bot bot commented Feb 11, 2025

🔗 Helpful Links

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

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

❌ 1 Cancelled Job, 1 Pending

As of commit 2584dc4 with merge base 8d96d74 (image):

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

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

@facebook-github-bot facebook-github-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 Feb 11, 2025
@zingo
Copy link
Collaborator

zingo commented Feb 11, 2025

MacOs fails unrelated

@zingo zingo merged commit 6d49702 into pytorch:main Feb 11, 2025
106 of 110 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants