From 5f3e4b74474d4f2ad3e17334364a86d298ae2382 Mon Sep 17 00:00:00 2001 From: Woosuk Kwon Date: Fri, 11 Sep 2026 20:15:02 -0700 Subject: [PATCH] Revert "[Agents] Link Triton skill to JIT kernel warmup guide" (#56546) --- .agents/skills/triton-kernel-writing/SKILL.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.agents/skills/triton-kernel-writing/SKILL.md b/.agents/skills/triton-kernel-writing/SKILL.md index 5a524c8a71..6dd6a8520b 100644 --- a/.agents/skills/triton-kernel-writing/SKILL.md +++ b/.agents/skills/triton-kernel-writing/SKILL.md @@ -26,10 +26,6 @@ description: Write or review Triton kernels for vLLM, with practical guidance fo unimportant runtime integer scalars in `do_not_specialize`, especially those that may alternate between values such as 0 and 1, which can produce different specialization keys. -- For new warmable kernels, follow the - [JIT Kernel Warmup guide](../../../docs/contributing/jit_kernel_warmup.md) - to define the warmup wrapper and call its `register_warmup(...)` where the - runtime implementation is selected during runner setup. - The Triton compiler does not guarantee safe ordering when a kernel writes to a pointer and subsequently reads from the same pointer. This pattern must have a `tl.debug_barrier()` between the write and read. The barrier