Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

2020.09.24: Working Group Meeting

Jump to bottom
Al Stone edited this page Oct 22, 2020 · 1 revision

Platform Spec Task Group Agenda: 24 Sep 2020

  • tech-unixplatformspec group is on google groups
  • Meeting info: [0]

Join with Google Meet

Old Business

  1. Rename to OSPS
    • Deferred pending further discussions on "platform" vs "profile"
    • Recommendation to drop the "OS" part to be more inclusive, i.e., just "Platform Spec"
  2. Proposed scope/charter
    • Get Linux for 64-bit written down first
    • Document where we are first, then improve over time
    • General agreement on the priorities as listed above, need clarification on a lot of the terminology being used first
    • Deferred pending rename and clarifications

Today's Topics

  1. Meeting cadence: weekly?
    • Agreed, do some polling to determine which day
  2. github master -> main (riscv/riscv-platform-specs)
    • Just housekeeping, now done
  3. SBI PMU extension
  4. SBI Reset extension
    • discussion: https://lists.riscv.org/g/tech-unixplatformspec/message/212
    • discussion: https://lists.riscv.org/g/tech-unixplatformspec/message/226
    • proposed for SBI to have one standard mechanism; e.g., UefiReset() would call the SBI reset
    • there was debate on whether or not this was a RISC-V specific concept, with the preference being to keep only RISC-V specific features in SBI
    • could we re-use an existing standard, such as ARM PSCI, or similar, to avoid inventing yet another standard? Perhaps; there is significant concern that such features may always be architecture-specific and do not translate well
    • discussion to be continued on the mailing list
  5. PR#3: Housekeeping
    • this was an attempt to see what happens when github PRs are used
    • this PR was a general overhaul of the document structure
    • given the discussion on the next item, this will be re-done and can be set aside for now
    • offers of similar content were shared; the more perspectives, the better
  6. PR vs mailing list vs both
    • we appear to have consensus on a basic process for submitting changes
      • Make a proposal on the mailing list, discuss as needed
      • Once an agreement on content has been reached, document it properly as a patch to the spec
      • Once approved, the patch is merged to become part of the next draft of the spec
      • On general agreement, the latest draft is submitted to the TSC for approval

Open Floor

  1. Notes from MarkH:
    • Software groups are still forming; churn and change is to be expected for a while.

References

[0] Recording: please see https://lists.riscv.org/g/tech-unixplatformspec/files/

[1] https://github.com/riscv/riscv-platform-specs/wiki/Draft-Charter

Clone this wiki locally