Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove fault for other fields of mttp csr #95

Merged
merged 1 commit into from
Oct 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions chapter3.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ an illegal instruction exception.
supervisor domains beyond the physical memory protection scheme described in
Section 3.7 of the RISC-V privileged architecture specification cite:[ISA]. In
this case, the remaining fields (`SDID`, `PPN`) in `mttp` must be set to
zeros, else generate a fault. When `XLEN=32`, the other valid setting for
zeros. When `XLEN=32`, the other valid setting for
`MODE` is `Smmtt34` to support read-write-execute
access permissions for 34-bit system physical addresses.

Expand Down Expand Up @@ -188,7 +188,7 @@ respective sections in this specification.
The `MFENCE.SPA` fence instruction is used to synchronize updates to supervisor
domain access-permissions with current execution.
`MFENCE.SPA` is only valid in M-mode. If operand rs1≠x0, it
specifies a single physical address, and if rs2≠x0, it specifies a single SDID.
specifies a single physical address, and if rs2≠x0, it specifies a single SDID.

If rs1 corresponds to an `MTT_L1_DIR` mapping, the fence applies to
a 4 KiB page. If rs1 corresponds to a `2M_PAGES` or `4M_PAGES` mapping,
Expand All @@ -197,15 +197,15 @@ of the 1G_* mappings, the fence applies to a 1 GiB range.

The behavior of `MFENCE.SPA` depends on rs1 and rs2 as follows:

* If rs1=x0 and rs2=x0, the fence orders all reads and writes to the MTT for
* If rs1=x0 and rs2=x0, the fence orders all reads and writes to the MTT for
all supervisor domain address spaces.
* If rs1=x0 and rs2≠x0, the fence orders all reads and writes to the MTT for
the supervisor domain address space identified by the SDID in rs2.
* If rs1≠x0 and rs2=x0, the fence orders all reads and writes made to the MTT
that correspond to the physical address in rs1, for all supervisor domain
address spaces.
* If rs1≠x0 and rs2≠x0, the fence orders all reads and writes made to the MTT
that correspond to the physical address in rs1, for the supervisor domain
that correspond to the physical address in rs1, for the supervisor domain
address space identified by the SDID in rs2.

Executing a `MFENCE.SPA` guarantees that any previous stores
Expand Down
Loading