1. Messages
  2. Status of v1.12 privileged specification

Re: Status of v1.12 privileged specification

Allen Baum
 

So " In general every new extension will be a separate new chapter."
But of course, but.... will they always be added to the end of the spec, or could they be inserted into the middle?
The latter will, cause renumbering of chapters, and many, many references to those sections to become obsolete
in docs all over the ecosystem. 

I'm reviewing the RISC-V certification test questions, and authors must point to references for their answers.
If sections change numbers, then a lot of those test questions will need to be rewritten. 
 I'm sure that won't be the only place, and tracking them all down will be a pain.

On Tue, Jul 26, 2022 at 9:51 AM Greg Favor <gfavor@...> wrote:
On Tue, Jul 26, 2022 at 8:05 AM Greg Chadwick <gac@...> wrote:
I appreciate no guarantees are possible but is it anticipated that the final v1.12 of the RISC-V privileged specification will be the  v. 20211203 currently listed on the RISC-V website (https://riscv.org/technical/specifications/) along with copy edits and the relevant already ratified extensions integrated (Smepmp, Smstateen, Sstc) as new chapters as the Svinval, Svnapot, Svpbmt extensions already are?

From that version onwards the ratified chapters are frozen other than "typo" corrections and clarifications.  The plan is for all Priv-related ratified extensions to be integrated into the Priv document (i.e. to have them all in one document), and for the Priv (and Unpriv) documents to be converted to adoc and to the new RVI adoc format.  These are active works in progress.  In general every new extension will be a separate new chapter.
 
Am I right in my understanding that support of new extensions for a particular implementation is determined via the (as yet to be defined) structure pointed to by the mconfigptr CSR

Yes.
 
and that any instructions introduced by one of those extensions should cause an illegal instruction exception where that extension isn't supported?

The current ISA arch specs do not require that unimplemented instructions result in an Illegal Instruction trap.  That is left for an ISA Profile or a Platform to recommend or mandate.

Greg
Join tech-privileged@lists.riscv.org to automatically receive all group messages.