Make kv cache update op support transposed cache

[kimishpatel]

Stack from ghstack (oldest at bottom):

• temp changes to enable benchmarking on device via adb #18719
• Add xplat cxx_binary target for bench_transposed_cache benchmark #18718
• Add non-flash SDPA path gated by ET_USE_UNFUSED_SDPA #18717
• Add ONNX Runtime GQA-style SDPA benchmark #18716
• Add GEMM-based standard SDPA benchmark and fix custom_sdpa_out signature #18715
• Support separate K/V seq dim in custom_sdpa op #18714
• Add --no_transposed_cache CLI flag for export pipeline #18713
• Plumb transposed cache config through export pipeline #18712
• Add benchmarks for transposed vs standard KV cache layout #18711
• temp hack #18710
• Add support for transposed kv cache in all variants of custom kv cache #18709
• Add contig requirement to aot binding for llm custom ops #18708
• Add support for seq at dim=2 #18707
• -> Make kv cache update op support transposed cache #18706
• Add xplat cxx_binary target for bench_sdpa #18705
• Use unfused SDPA for short sequences (q_len <= 128 or kv_len <= 128) #18651
• Limit softmax to causally-valid elements in cpu_sdpa #18650
• Add quantized input support to cpu_sdpa #18649
• [Executorch] Add non-flash SDPA for decode #18648
• Add ONNX Runtime GQA-style SDPA benchmark #18647
• Add GEMM-based standard SDPA benchmark #18646
• Fix SLEEF preprocessor macro name to match ATen vec headers #18645

Differential Revision: D93870392

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 3 Cancelled Jobs

As of commit c0e8395 with merge base fb1618e ():

NEW FAILURES - The following jobs have failed:

• pull / test-lora-linux / linux-job (gh)
  RuntimeError: Command docker exec -t ae4d1fdb6638585badecb7928c72f4b9c1dce12879e92de631e362f531d8354a /exec failed with exit code 1
• pull / test-lora-multimethod-linux / linux-job (gh)
  RuntimeError: Command docker exec -t f9a162587e21b9fcff3bf1d009c26e7e23a04d29d606efae171c7964e13685cd /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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

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

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

[kimishpatel]

submitted by accident, not meant to land immedidately

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[meta-cla]

Hi @kimishpatel!

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 cla@meta.com. Thanks!