This document lists the current 2H23 priorities as of 8/23/2023.
Contents:
| Table of Contents |
|---|
...
- RVI CoVE: for EDK2_00_02 - StandaloneMmPkg
- RVI CoVE-IO: for EDK2_00_02 - StandaloneMmPkg
- UEFI PI: EDK2_00_02 - StandaloneMmPkg
- RVI SBI Debug Trigger Extension: LK_01_005 - Native/hosted debug support (aka HW breakpoint)
- RVI RISC-V Cryptography Extensions: SL_00_003 - OpenSSL
- RVI psABI vector ABI: CT_03_001 - Binary Toolchain Packages
- RVI psABI: CT_01_003 - Shadow Stacks (LLVM)
- RVI psABI: CT_00_009 - Large Code Model (GCC) (https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/388)
- RVI Unified Discovery: Profile- and Extension- Optimized Distros
Observations
Prioritization Activities
Current prioritization efforts were "bottom up". This meant the WGs were largely left to their own devices in terms of identifying priorities. Such an approach enabled the TSC to identify trends to help shape further (1H24, 2H24) priorities.
Overall, three trends (market directions) are evident:
- General-purpose compute (aka "server")
- HPC (differentiated from "server" by a different software stack)
- Consumer / Mobile (Android, Tizen, possible bridges to existing AArch64 software)
These are all dependent on:
- Base developer / SW ecosystem enablement, seen with toolchain/runtime and emulator work.
It's reasonable to work across a couple of directions that are different enough from each other to have the maximum impact from enablement activities. Such two directions could be server and consumer.
Prioritized Projects
...