MCFG table was not referenced earlier. UC is not present in abbreviation section. Moreover, PMA + PBMT seems bit ambiguous to me. It wouldn't hurt to be more verbose here. same comment as

Looks good.Reviewed-by: Abner Chang <abner.chang@...> Mayuresh Chitale <mchitale@...> 於 2021年7月2日 週五 上午12:50寫道：

I think it will be good to provide additional clarification in the beginning about the number of interrupts/contexts. Something along the lines: The PLIC specification supports up-to 1024 interrupts

Reviewed-by: Atish Patra <atish.patra@...> -- Regards, Atish

This patch adds requirements for PCIe support for the server extension Signed-off-by: Mayuresh Chitale <mchitale@...> --- riscv-platform-spec.adoc | 174

V2: - Fixed abbreviation for root complex integrated endpoint - Added section for PCIe device firmware requirement. V1: - Initial patch. Mayuresh Chitale (1): server extension: PCIe requirements

Updated v2 of the cache coherency patch Changes from v1 Brought in all cache coherency changes after feedback Removed ASID requirements diff --git a/riscv-platform-spec.adoc

Sure. Yes, I will fix in the next revision. Yes, looks like I missed it. I will include it in the next revision.

Mayuresh Chitale <mchitale@...> 於 2021年6月30日 週三 上午12:27寫道： Suggest using RCiEP (lower case of "I") which is aligned with PCIE spec. Should this be RCiEP? If yes, then the same

We have the initial draft of an official RISC-V Glossary: https://github.com/riscv/riscv-glossary Anyone can can create an issue for the Glossary. We could append the Glossary to each and every

This patch adds requirements for PCIe support for the server extension Signed-off-by: Mayuresh Chitale <mchitale@...> --- riscv-platform-spec.adoc | 166

This is an initial patch for PCIe requirements for the server extension. The goal is to specify requirements for those PCIe elements which interact with the system such as PCIe config space, memory

do we have a glossary (with links if apropos) for the acronyms in use in the docs (like IMSIC)? more than just what the acronym is for but like what the item is for and either a standards definition

Hi Team, As we discussed in the Platform HSC meeting yesterday, I am attaching the snapshot of the slides presented. Please also go through the

Jonathan Behrens <behrensj@...> 於 2021年6月29日 週二 上午2:32寫道： I don't think that is necessary to mention how to program the RTC in platform spec. We just need the RTC to keep

Keep in mind the distinction between RVM ISA profile specs and M platform specs. I would expect that the M platform spec would require the RVM ISA profile spec. But all the individual FP and C

Forwarding to tech mailing list. Regards Kumar

What does "implementation specific" mean in this context? Could the platform spec require implementations to program the RTC with UTC times? If not, could it recommend/encourage them to? Jonathan

https://github.com/riscv/riscv-platform-specs/blob/main/riscv-platform-spec.adoc Yes, it includes all planned extensions. Regards Kumar

where are the current platform specifications that are under development being stored? does it include extensions? Thanks Mark