Proposal: RISC-V Hypervisor Sync-up Call
Hi All,
Quite a few organizations are working on implementing RISC-V
H-extension.
I suggest to have a regular RISC-V Hypervisor Sync-up Call to:
1) Coordinate RISC-V hypervisor software efforts so that two
different organization/individuals don't end-up doing same
work.
2) Decide priorities and future directions for RISC-V hypervisor
software efforts.
3) Distro expectations from RISC-V hypervisor (particularly KVM RISC-V)
4) General discussion around validating RISC-V hypervisor software
in RTL simulation or FPGA or real SOC
5) Anything else ???
Regards,
Anup
Quite a few organizations are working on implementing RISC-V
H-extension.
I suggest to have a regular RISC-V Hypervisor Sync-up Call to:
1) Coordinate RISC-V hypervisor software efforts so that two
different organization/individuals don't end-up doing same
work.
2) Decide priorities and future directions for RISC-V hypervisor
software efforts.
3) Distro expectations from RISC-V hypervisor (particularly KVM RISC-V)
4) General discussion around validating RISC-V hypervisor software
in RTL simulation or FPGA or real SOC
5) Anything else ???
Regards,
Anup