Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Commit

Permalink
clarify explicit store behavior for D bit
Browse files Browse the repository at this point in the history
  • Loading branch information
ved-rivos committed Sep 10, 2023
1 parent 83e695e commit f0603a4
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions svadu.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ A/D bits. The A and D bits are managed by these extensions as follows:
must atomically check that the PTE is valid and grants sufficient permissions
as part of conditionally making the update. Updates of the A bit may be
performed as a result of speculation, even if the associated memory access
ultimately is not performed architecturally. However, updates to the D bit
by an explicit store must be exact (i.e., non-speculative), and observed in
program order by the local hart. When two-stage address translation is active,
updates of the D bit in G-stage PTEs may be performed as a result of
speculative updates of the A bit in VS-stage PTEs. +
ultimately is not performed architecturally. However, updates to the D bit,
resulting from an explicit store, must be exact (i.e., non-speculative), and
observed in program order by the local hart. When two-stage address
translation is active, updates of the D bit in G-stage PTEs may be performed
as a result of speculative updates of the A bit in VS-stage PTEs. +
+
The PTE update must appear in the global memory order before the memory access
that caused the PTE update and before any subsequent explicit memory access to
Expand Down

0 comments on commit f0603a4

Please sign in to comment.