[PATCH] Clarify VMID consideration for SBI HFENCE VVMA calls


Anup Patel
 

The SBI HFENCE VVMA calls use current VMID (in HGATP CSR) of calling
HART for flushing TLB enteries. This fact is not clearly evident in
current documentatation of HFENCE VVMA calls hence this patch improves
documentation accordingly.

Signed-off-by: Anup Patel <anup.patel@...>
---
riscv-sbi.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/riscv-sbi.adoc b/riscv-sbi.adoc
index 8137686..dae489c 100644
--- a/riscv-sbi.adoc
+++ b/riscv-sbi.adoc
@@ -466,8 +466,8 @@ struct sbiret sbi_remote_hfence_vvma_asid(unsigned long hart_mask,
----
Instruct the remote harts to execute one or more HFENCE.VVMA instructions,
covering the range of guest virtual addresses between start and size for the
-given guest ASID. This function call is only valid for harts implementing
-hypervisor extension.
+given ASID and current VMID (in HGATP CSR) of calling hart. This function call
+is only valid for harts implementing hypervisor extension.

*Returns* following possible values via sbiret.
[cols="<,>",options="header,compact"]
@@ -486,9 +486,9 @@ struct sbiret sbi_remote_hfence_vvma(unsigned long hart_mask,
unsigned long start_addr, unsigned long size)
----
Instruct the remote harts to execute one or more HFENCE.VVMA instructions,
-covering the range of guest virtual addresses between start and size for any
-process belonging to the current guest. This function call is only valid for
-harts implementing hypervisor extension.
+covering the range of guest virtual addresses between start and size for
+current VMID (in HGATP CSR) of calling hart. This function call is only valid
+for harts implementing hypervisor extension.

*Returns* following possible values via sbiret.
[cols="<,>",options="header,compact"]
--
2.25.1

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