Skip to content

Prototype AMD XDNA bfp16ebs8 as a backend-local vendor tier #148

Description

@aravishankar-mp

Part of #110. Blocked by #146.

Goal

Prototype the proven AMD XDNA bfp16ebs8 block-8 contract as a backend-local vendor experiment so
the native hardware path can be exercised before TOSA standardization settles.

This is deliberately not called block FP16, BFP16, BF16, TOSA MX, or EXT-MX-*. It must not be
accepted under the stable TOSA 1.0 artifact format or advertised through
TosaCapabilityProvider.

Boundaries

  • Use a backend-local/precompiled experimental artifact with an explicit version and target
    identity that cannot collide with released TOSA.
  • Keep the numerical label guest-visible and immutable; a host knob may disable the experiment but
    cannot substitute it under another tier.
  • Reuse the characterization ticket's reference model and fixtures exactly.
  • Bind caller-owned buffers directly and perform no submission-time repacking or scale synthesis.
  • Compilation remains offline/load-time and pinned to the measured toolchain identity.

Acceptance criteria

  • The experimental artifact encodes every scale/value plane and block-layout parameter needed to
    reproduce the characterized contract without hidden defaults.
  • Exact or explicitly tolerance-bounded oracles cover edge classes and representative block
    exponent disagreement.
  • The full lifecycle runs on the reference NPU with direct-binding diagnostics and no hidden
    staging.
  • Unsupported or mismatched artifacts are rejected before native resource creation.
  • Documentation labels the surface “AMD bfp16ebs8 vendor experiment (block-8)” and explains why
    it is not a TOSA capability.
  • The prototype creates no protocol 1.0 wire change and no claim about future MX compatibility.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area: backendAccelerator traits, mock backend, and provider conformancearea: verificationSecurity, fuzzing, model tests, and performance evidenceenhancementNew feature or requestkind: implementationProduction implementation workwayfinder:taskWayfinder task ticket

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions