Skip to content

CI: hi3516cv500 QEMU regression target for ive_neo #114

@widgetii

Description

@widgetii

The QEMU IVE ops regression job in .github/workflows/build.yml runs kernel/ive_neo/test/qemu/test-ive-ops (the vendored 19-op register checksum test) only against the hi3516ev300 machine model in widgetii/qemu-hisilicon. There's no equivalent for cv500.

This means cv500-specific regressions can land without any automated regression catch:

What's needed

  1. Upstream QEMU work: widgetii/qemu-hisilicon needs a hi3516cv500 machine model. Doesn't exist yet — separate project.
  2. OR: A test runner that ssh's into a CI-attached cv500 board (openipc-hi3516av300.dlab.doty.ru already serves this role for manual verification) and runs test_persp_hog. Needs ssh key + secret in CI.

(2) is more pragmatic short-term — the lab board exists and works; just needs CI access.

Definition of done

  • Either:
    • cv500 QEMU machine model exists in qemu-hisilicon AND a QEMU IVE ops regression (cv500) job runs against it; OR
    • A Live cv500 board regression job ssh's to a CI-attached cv500 board (likely behind tailscale / CI runner constraints), loads the freshly built open_ive_neo.ko + libive_neo.so, runs test_persp_hog, asserts Summary: 0 failures.
  • The new job is gated on cv500-affecting paths only (kernel/ive_neo/**, libraries/ive_neo/**).

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions