executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
s-tir-tuningGuides TVM S-TIR scheduling, transformations, dlight rules, meta-schedule tuning, builders, runners, and CPU/GPU tuning decisions.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this route when a task involves tvm.s_tir.Schedule, schedule primitives,
transform passes, dlight/default schedules, meta-schedule, tune_tir, or
bounded tuning of TIR generated from Relax or TIRx.
../install-build/SKILL.md for package/build
failures.references/schedule-workflows.md.tune_tir, builder/runner/database/cost-model decisions, or bounded
tuning runs, read references/meta-schedule.md.scripts/meta_schedule_import_probe.py
before a tuning run to verify the API and optional dependencies.references/troubleshooting.md for
ScheduleError, invalid traces, no-candidate tuning, database, XGBoost,
runner/RPC, and backend issues.from tvm.s_tir import Schedule
from tvm.s_tir import meta_schedule as ms
sch = Schedule(mod, seed=None, debug_mask="none", error_render_level="detail", enable_check=True)
ms.tune_tir(mod, target, work_dir, max_trials_global, runner="local", database="json")
tune_tir returns a meta-schedule Database. Use tiny max_trials_global
values for smoke checks, a disposable work_dir, and a CPU target unless the
user has explicitly prepared a GPU/RPC backend.
../relax-compile/SKILL.md.../tirx-kernels/SKILL.md.../rpc-deployment/SKILL.md.../install-build/SKILL.md.