Re: Proposal for Custom Values in satp


Bill Huffman
 

Looks appropriate to me.     Bill

On 7/31/20 4:22 PM, Andrew Waterman wrote:

EXTERNAL MAIL

I've written the idea up so it doesn't get lost, but others should still feel free to comment.  In the meantime, can you sanity-check my patch?  https://github.com/riscv/riscv-isa-manual/commit/f7710a02da497a721095a0252041122a6d0e0a6c

On Thu, Jul 30, 2020 at 10:26 AM Allen Baum <allen.baum@...> wrote:
That sounds like a no brainer good idea.

-Allen

On Jul 29, 2020, at 2:41 PM, Andrew Waterman <andrew@...> wrote:

I support this proposal.

On Wed, Jul 29, 2020 at 12:42 PM Bill Huffman <huffman@...> wrote:

The satp register has reserved values.  Some implementers will, no doubt, want to define non-standard behavior based on satp.  I would like to propose that we define some of the reserved values in satp as Custom now so that those who do so won't head in diverging directions.

For RV64, there are 11 reserved values of the Mode field.  I propose that the encodings 14 and 15 be defined as Custom.

For RV32, values with satp[31] clear and satp[30:0] non-zero are reserved.  I propose that values with satp[31] clear and satp[30:29]=0x3 be defined as Custom.

The RV32 encoding is not perfect.  To have the largest contiguous space free, we need to pick bits at the top or bottom.  Top bits encroach on what's now ASID space while bottom bits encroach on what's now PPN space.  The former seemed a bit better.

       Bill


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