kernelci / kernelci/kernelci-project

RISC-V pull-lab: qemu-riscv64 kselftest profile

Open
#585 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
14
Forks
32
Avg merge
1d 1h
Merged PRs (30d)
3

Description

## Context

KUBUDS Tech intern working on the RISC-V Development Partners SOW:
https://github.com/riscv-admin/dev-partners/issues/49

Repo: https://github.com/Hao-Chen2337/kernelci-riscv

Tracking the upstream integration of a RISC-V QEMU pull-lab test profile
(Vector + Hypervisor coverage) for kernelci-pipeline.
(Separate from #579 — that's another KUBUDS team member's project.)

## Current state

- Local pipeline (tuxrun/QEMU) via one-command `./run.sh`; validate_yaml green.
- Vector: 10 tests, 9 pass / 1 fail. Hypervisor: 6 pass / 2 skip, job pass.
- Config drift + trend tooling working.
- PR submitted: https://github.com/kernelci/kernelci-pipeline/pull/1599

Known environment limits (not kernel regressions): pointer_masking
(PMLEN=16), irqfd_test / sbi_pmu_test skip under TCG; perf/stress and
kvm_page_table_test excluded (hang/time out under TCG).

## Status

- [x] Phase 1: local pipeline + validation
- [x] Phase 2: Vector/Hypervisor pass-rates + drift + trend
- [x] Phase 3: PR submitted (#1599)
- [ ] Phase 4: blog / demo / badges (runbook done)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the referenced kernelci-pipeline PR #1599 and the one-command ./run.sh pipeline; validate the YAML with validate_yaml and review the Vector and Hypervisor results. The remaining Phase 4 work is a blog, demo, and badges deliverable, while the runbook is already done.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
operating-systems, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.