Skip to content

index.md

Latest commit

 

History

History
32 lines (22 loc) · 1.04 KB

index.md

File metadata and controls

32 lines (22 loc) · 1.04 KB

Execution Engine

日本語

AIKernel.Control is the execution-engine layer for AIKernel.

Responsibilities

  • Schedule semantic execution graphs onto CPU, GPU, or emulator backends.
  • Preserve deterministic replay and step-by-step execution.
  • Expose diagnostics for node timing, CPU/GPU load, breakpoints, watches, and traces.
  • Keep physical execution separate from AIKernel.Core contracts and AIKernel.Demo samples.

Runtime Analogy

AIKernel.Core is the semantic graph producer. AIKernel.Control is the runtime that binds the graph to execution providers, similar to how ONNX Runtime binds ONNX graphs to CPU/GPU execution providers.

Bonsai Execution

The initial standard model path is Bonsai-1.7B:

  • BonsaiBuiltInProvider owns ROM loading, lifecycle observation, and provider capability metadata.
  • Bonsai1BitCpuKernel owns Q1_0 CPU execution.
  • IBonsaiGpuExecutionDelegate defines the GPU delegation surface for CUDA, WebGPU, ROCm, Vulkan, or other backends.

See Q1_0 CPU Execution Kernel.