[ET-VK][profiling] Add additional profiling blocks

[SS-JIA]

Stack from ghstack (oldest at bottom):

• -> [ET-VK][profiling] Add additional profiling blocks #17394
• [ET-VK][qconv2d][ez] Don't use im2col path for general convs #17393
• [ET-VK] Add nchw_to_int8x4_buffer shader for prepacking int8 staging data #17392
• [ET-VK] Layout-flexible impl of quantized binary #17391
• [ET-VK][ez] Make q8ta_conv2d use 4C1W layout #17390
• [ET-VK][ez] Add AOT support for PackedInt8_4C1W dtype #17389
• [ET-VK] Migrate to use new q8ta_conv2d ops #17388
• [ET-VK][qconv] Dynamically select between im2col path and general path #17387
• [ET-VK][qconv][ez] Make q8ta_im2col shader support stride_w != 1 #17386
• Back out "[Diff Train][pytorch/executorch] Apply fixup patch to fbsource" #17399

This adds fine-grained ET_EVENT_TRACER profiling blocks to the Vulkan backend's execute() method in VulkanBackend.cpp. Previously, only GPU shader timestamps were logged. Now the following phases are individually traced: ETVK_COPY_INPUTS (host-to-GPU input transfer), ETVK_RESIZE (graph resize propagation), ETVK_COMPUTE_GRAPH_EXECUTE (GPU compute dispatch), ETVK_COPY_OUTPUTS (GPU-to-host output transfer), and ETVK_EXECUTE (overall delegate execution). The GPU shader timestamp extraction is also moved to occur right after execute() completes rather than at the end of the function, so it falls within the ETVK_EXECUTE span.

Differential Revision: D93000163

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 2 Unrelated Failures

As of commit d1be431 with merge base 964c565 ():

NEW FAILURE - The following job has failed:

• pull / test-vulkan-operators-linux / linux-job (gh)
  RuntimeError: Command docker exec -t ec18f20965775af3d59e54e11129489484fd59b81b19d9ec7c38cb33e9eff467 /exec failed with exit code 1

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-selective-build-linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following job failed but was present on the merge base:

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

• pull / test-samsung-models-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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.