[KleidiAI] turn on SME2 by default

[mcr229]

No description provided.

[mcr229]

Stack from ghstack (oldest at bottom):

• -> [KleidiAI] turn on SME2 by default #13233
• [KleidiAI] Always attempt activation packing #13232
• [Profiling] Add python scripts to generate per-op profiling from etdumps #13302
• Add csv and etdump files to gitignore #13301

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures

As of commit cfdebbe with merge base a84b3c9 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• Lint / lintrunner / linux-job (gh)
  >>> Lint for backends/xnnpack/cmake/Dependencies.cmake:
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh)
  backends/arm/test/models/stable_diffusion/test_vae_AutoencoderKL.py::TestAutoencoderKL::test_AutoencoderKL_tosa_INT

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

[digantdesai]

Move around the comment?

[digantdesai]

What's the test plan? Assuming Kleidi folks have tested the kernel and the XNNPACK path to the kernel is ~shared?

[mcr229]

What's the test plan? Assuming Kleidi folks have tested the kernel and the XNNPACK path to the kernel is ~shared?

cc. @mergennachin for the test plan around SME2 kernels.

[meta-cla]

Hi @mcr229!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!