Ethos Driver Backwards Compatibility (#19116)

[gkrulce]

Summary:

The version of ethos driver that supports multiple devices / multiple
NPUs has a few breaking API changes. Installing backwards compatibility hooks
so that Executorch continues to work with both old and new driver code.

It adds the new APIs as weak definitions and redirects to old driver code. If
new driver code is available, those definitions override the weak definitions.

Driver code ref:
https://gitlab.arm.com/artificial-intelligence/ethos-u/ethos-u-core-driver/-/blob/experimental/multidevice/README.md?ref_type=heads#experimental---multi-device

Reviewed By: digantdesai

Differential Revision: D102359186

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Rolling out OSDC (ARC) runners on pull & trunk workflows in PyTorch main

❌ 4 New Failures, 4 Unrelated Failures

As of commit a92a6b8 with merge base e4ab34d ():

NEW FAILURES - The following jobs have failed:

• pull / test-qnn-delegate-linux / linux-job (gh)
  backends/qualcomm/tests/test_qnn_delegate.py::TestQNNFloatingPointOperator::test_qnn_backend_argmin
• trunk / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  RuntimeError: Command docker exec -t 0e59ab6d577024a1ee641506e6cd5986455d7674d246f3c7331ad4126da5cd2f /exec failed with exit code 92
• trunk / test-qnn-model (fp32, ic3) / linux-job (gh)
  RuntimeError: Command docker exec -t bc9605600f9af935c7ac1d37e08a14b07a8cec20b4e2e1559968d0d4413bdbdf /exec failed with exit code 92
• trunk / test-qnn-optimum-model (fp32, focalnet) / linux-job (gh)
  RuntimeError: Command docker exec -t 7ba0a04c1cc632ce839b32ab0ffefced21b9f1b045b852088418dfdc137c50c5 /exec failed with exit code 92

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-qnn-testsuite-linux / test-backend-linux (qnn, models) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / unittest / macos / macos-job (gh) (similar failure)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• trunk / unittest-release / macos / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[meta-codesync]

@gkrulce has exported this pull request. If you are a Meta employee, you can view the originating Diff in D102359186.

[pytorch-bot]

Workflows were awaiting approval. CI has now been triggered for the ciflow labels on this PR.

[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.

[digantdesai]

Review automatically exported from Phabricator review in Meta.

[digantdesai]

cc: @zingo as FYI, should be harmless.

[perheld]

cc: @zingo as FYI, should be harmless.

FYI. Funny thing, it broke our internal cppcheck test. So that highlights the need for cppcheck to make it into lintrunner-adapters so it can run upstream as well. WIP: justinchuby/lintrunner-adapters#137 :)