0 Fork 0

Files

T

5e4b9f8c6e [Misc] Align CODEOWNERS with module/feature design docs (#5958 )

Signed-off-by: hsliu_ustc <hsliu_ustc@noreply.gitcode.com>
Signed-off-by: Hongsheng Liu <liuhongsheng4@huawei.com>
Co-authored-by: hsliu_ustc <hsliu_ustc@noreply.gitcode.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

2026-08-10 19:25:03 +08:00

1.4 KiB

Raw Blame History

title, kind, status, owners, primary_code_paths, primary_code_path_owners, related_code_paths, depends_on, validation_paths, upstream_refs, last_reviewed

title

kind

status

owners

primary_code_paths

primary_code_path_owners

related_code_paths

depends_on

validation_paths

upstream_refs

last_reviewed

Execution Platforms

module

draft

@gcanlin

@tjtanaa

@xuechendi

vllm_omni/platforms/**

vllm_omni/attention/**

paths

owners

vllm_omni/attention/**

@david6666666

@lishunyang12

ar_runtime.md

diffusion/index.md

tests/platforms/**

vllm.platforms

2026-07-16

Execution platforms

Execution platforms isolate hardware-specific capability detection, worker selection, patches, kernels, and configuration adjustments.

Candidate invariants

PLATFORM-INV-001: Capabilities are explicit

Rule: Hardware-dependent behavior MUST be guarded by platform selection or capability detection and MUST fail clearly when unsupported.

PLATFORM-INV-002: Portable code remains portable

Rule: Platform-neutral modules MUST NOT import a vendor implementation directly when a common selection interface exists.

PLATFORM-INV-003: Overrides are minimal

Rule: A platform implementation SHOULD override only behavior that differs from the common or upstream implementation.

Safe-change guide

Validate common import paths without the target accelerator and run focused tests in a fresh uv environment on every affected device platform.

1.4 KiB Raw Blame History