Skip to content

Conversation

MartinPavella
Copy link
Collaborator

@MartinPavella MartinPavella commented Sep 25, 2025

Summary

This PR resolves format related issues by inferring the format (NCHW/NHWC) for all nodes before partitioning. These formats are then used by the NeutronPartitioner to accurately determine which nodes are supported on Neutron.

Test plan

Unit tests provided, and correct function is tested by nearly every test in the nxp backend.

cc @kimishpatel

Copy link

pytorch-bot bot commented Sep 25, 2025

🔗 Helpful Links

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

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

❌ 2 New Failures, 1 Unrelated Failure

As of commit 974c05d with merge base f0e8ea8 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following job failed but was likely due to flakiness present 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 Sep 25, 2025
@MartinPavella
Copy link
Collaborator Author

@pytorchbot label "module: nxp" "release notes: nxp"

deps = [
":neutron_sdk",
":aten_passes",
":_passes",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add neutron_backend build to this https://github.com/pytorch/executorch/blob/main/.ci/scripts/unittest-buck2.sh. Thats the one that was failing last time. This way we get signal on the pr itself

@facebook-github-bot
Copy link
Contributor

@kimishpatel has imported this pull request. If you are a Meta employee, you can view this in D83311730.

@kimishpatel
Copy link
Contributor

i have imported it internally. There is an nxp test failing as well

Copy link
Contributor

@digantdesai digantdesai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review automatically exported from Phabricator review in Meta.

@MartinPavella MartinPavella force-pushed the upstream/main-nxp/EIEX-392-resolve-limitations-of-uncertain-tensor-formats branch 2 times, most recently from bb48aad to e1893f5 Compare October 1, 2025 07:41
@MartinPavella MartinPavella marked this pull request as draft October 1, 2025 12:22
@MartinPavella
Copy link
Collaborator Author

MartinPavella commented Oct 1, 2025

@kimishpatel I have fixed the failing nxp test, and added the nxp backend build to the unittest-buck.sh. The build is now failing with:

1: From load at backends/nxp/TARGETS:4
2: File not found: shim_et//arvr/tools/build_defs/oxx_python.bzl

These lines were in the file already before my changes. Do you know what is causing the issue/how to fix it?

@kimishpatel
Copy link
Contributor

@kimishpatel I have fixed the failing nxp test, and added the nxp backend build to the unittest-buck.sh. The build is now failing with:

1: From load at backends/nxp/TARGETS:4 2: File not found: shim_et//arvr/tools/build_defs/oxx_python.bzl

These lines were in the file already before my changes. Do you know what is causing the issue/how to fix it?

I guess it is triggering your build in oss and we have never really had this test in oss so its trying to pull in internal files. I would say roll back that change for now just to be able to land.

@MartinPavella MartinPavella force-pushed the upstream/main-nxp/EIEX-392-resolve-limitations-of-uncertain-tensor-formats branch 2 times, most recently from 2672277 to 1ecfe36 Compare October 3, 2025 07:15
@MartinPavella MartinPavella marked this pull request as ready for review October 3, 2025 08:34
@MartinPavella
Copy link
Collaborator Author

@kimishpatel I have fixed the failing nxp test, and added the nxp backend build to the unittest-buck.sh. The build is now failing with:
1: From load at backends/nxp/TARGETS:4 2: File not found: shim_et//arvr/tools/build_defs/oxx_python.bzl
These lines were in the file already before my changes. Do you know what is causing the issue/how to fix it?

I guess it is triggering your build in oss and we have never really had this test in oss so its trying to pull in internal files. I would say roll back that change for now just to be able to land.

@kimishpatel thanks for the response. I have removed the build as you said. Can you please now verify that your internal build passes?

@kimishpatel
Copy link
Contributor

doing

@MartinPavella
Copy link
Collaborator Author

doing

@kimishpatel any updates? Is the build passing?

@MartinPavella
Copy link
Collaborator Author

doing

@kimishpatel any updates? Is the build passing?

@kimishpatel pinging in case you missed this.

Copy link
Collaborator

@StrycekSimon StrycekSimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the numMacs related comment. Did the remove_geititem_pass.py just pass the linter with such long lines?

@MartinPavella
Copy link
Collaborator Author

Please update the numMacs related comment. Did the remove_geititem_pass.py just pass the linter with such long lines?

Yes, the linter passed. I have shortened the lines now anyway.

@MartinPavella MartinPavella force-pushed the upstream/main-nxp/EIEX-392-resolve-limitations-of-uncertain-tensor-formats branch from 1ecfe36 to 27444cf Compare October 14, 2025 08:26
@MartinPavella MartinPavella force-pushed the upstream/main-nxp/EIEX-392-resolve-limitations-of-uncertain-tensor-formats branch from 27444cf to fa43ac2 Compare October 14, 2025 08:27
… node format.

The pass `RemoveGetItemPass` replaces a `max_pool2d_with_indices` node with a `max_pool2d` node, that doesn't require a GetItem afterward. The new operator must, however, preserve the original node format. Therefore, a copy of the pass was created in `backends/nxp/_passes`, where it was modified. The new directory was created, because the pass doesn't follow the `NeutronEdgePass` interface.
Before, the format inference was done during conversion to NeutronIR (after partitioning), so the partitioner didn't yet know the formats. Now, the partitioner has the format data, which can be used to accurately select nodes for delegation.
@MartinPavella MartinPavella force-pushed the upstream/main-nxp/EIEX-392-resolve-limitations-of-uncertain-tensor-formats branch from fa43ac2 to 974c05d Compare October 15, 2025 12:55
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. module: nxp Issues related to NXP Neutron NPU delegation and code under backends/nxp/ release notes: nxp Changes to the NXP Neutron backend delegate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants