2021.03.22: Working Group Meeting

Platforms Horizontal Subcommittee (PHSC) Agenda: 22 March 2021

Details: https://sites.google.com/a/riscv.org/risc-v-staff/home/tech-groups-cal
Past meetings: https://github.com/riscv/riscv-platform-specs/wiki
Meetings every alternate Monday
- 7AM PST until Mar 14 2021, 8AM PST after Mar 14 2021
- If the meeting Monday is a scheduled holiday in the US, the meeting will be held on Wed 8AM PST of the same week

Anti-trust statement
Open and collaborative
Org chart:
- TSC -> Software HC -> Platform HSC (you are here)
- TGs and SIGs as needed

Linux/Embedded-2022 Platform specification presentation by Kumar
- Presentation located here https://docs.google.com/presentation/d/10NfguE3C6GQTkKaoVBdneB94i4b_M7akmH1pt4kmqCs/edit#slide=id.g9a913c83e8_0_41
- Platform Policy Discussion - Philipp Tomsich - 15-mins
- RISC-V Linux spinlock implementation - Christoph Mullner - 15-mins
- Platform Specification Update - 15-mins
- Questions/Opens - 8-mins
- Next Steps - 2-mins
Platform schedule and owners tracker Excel located here https://docs.google.com/spreadsheets/d/1J4kqyW9tPxqY1CGcJUQsmtHt3FYlqGi_erWQGrmoQtU/edit#gid=0
Google Drive Shared platform folder with all presentations, schedules and material located here https://drive.google.com/drive/folders/1ooqdnIsYx7XKor5O1XTtM6D1CHp4hc0p?usp=sharing
Platform Specification Document located here https://github.com/riscv/riscv-platform-specs/blob/main/riscv-platform-spec.adoc

Platform Policy should be reviewed and approved first by the platform and software chairs and vice-chairs. It then gets sent out for a final review.
RISC-V Linux spinlock
- Pursue option B (now called option 2)
- There may not be at this time a problematic impediment to getting improved patches accepted upstream (unlike in the past).
- Christoph and Anup are going to sync up about pursuing this.
- Net, the goal is for RISC-V Linux to support qspinlocks (albeit sub-optimal compared to what option C (now being called option 3) can enable).
- OpenSBI will upgrade to using ticket locks - since this is simpler code and OpenSBI has a much simpler situation to deal with that does not warrant the extra complexity of qspinlocks.
For security related updates to the spec, platform group should make a joint decision and escalate to Mark if there is any dependency on other groups.