Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Enable native Kev inference with the Vulkan backend

Aperta
#23,098 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, cmake, cpp, python, pytorch
Ambito
ai-infra-agents, backend, desktop-dev, mobile-dev

Direzione di ricerca

Start with the Kev example in examples/kev/ and the Vulkan export example in examples/vulkan/. Examine the Vulkan backend in backends/vulkan/ to identify missing operator support for GatedDeltaNet and dynamic shapes. Write a small GDN parity test as a first step, then extend the export and CMake linkage to allow kev_runner to use the Vulkan backend. Validate against the PyTorch reference implementation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

good first issue module: examples module: vulkan

Enable the native Kev example on the Vulkan backend, extending the XNNPACK and MLX support added in #23023.

Kev runs prefill followed by pointer-head scoring, with an immutable prefix snapshot reused across question batches. The goal is to support this workflow through the existing C++ API on Vulkan-capable GPUs, without Python at inference.

Start with Kev's model/export code, the Vulkan export example, and the Vulkan backend. Qwen3.5 MoE's GatedDeltaNet implementation provides a reference for GDN math and state layouts; Vulkan will need its own lowering or shader support where coverage is missing.

Work to cover:

  • Identify operator and dynamic-shape gaps in Kev's prefill and score graphs. Add the required Vulkan support, including GDN, with focused backend regression tests. A small GDN parity test is a useful first step.
  • Add a Vulkan export option and CMake linkage so the existing kev_runner and kev_benchmark run the exported model through Module.
  • Preserve system_one, explicit prefill/evaluate, configurable token limits, variable question/option counts, and batching beyond eight questions. Repeated evaluations must leave the prefix unchanged.
  • Start with an unquantized FP32 path, retaining the fitted temperature and checkpoint metadata. Check logits, probabilities, and reused state against upstream Kev's PyTorch implementation and the existing FP32 path, with documented tolerances.
  • Verify the backbone, including GDN, executes on Vulkan and report any CPU fallback. Document a tested GPU, precision requirements, export/build/run commands, and measurements using kev_benchmark.

Keep the integration in the existing example and reuse the runner and benchmark. A Vulkan-capable GPU and the Vulkan SDK are needed for validation.

cc @SS-JIA @manuelcandales @digantdesai @cbilgin @iseeyuan @lucylq @helunwencser @tarun292 @kimishpatel @jackzhxng

Lingua principale
Python
Stelle
5k
Fork
1.2k
Merge medio
2g 13h
PR unite (30g)
595

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pytorch/executorch

Tutte le issue di pytorch/executorch

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.