[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PULL 2/6] riscv: Don't use stage-2 PTE lookup protection flags

From: Palmer Dabbelt
Subject: [PULL 2/6] riscv: Don't use stage-2 PTE lookup protection flags
Date: Tue, 21 Apr 2020 12:09:57 -0700

From: Alistair Francis <address@hidden>

When doing the fist of a two stage lookup (Hypervisor extensions) don't
set the current protection flags from the second stage lookup of the
base address PTE.

Signed-off-by: Alistair Francis <address@hidden>
Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: Palmer Dabbelt <address@hidden>
 target/riscv/cpu_helper.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
index e2da2a4787..48e112808b 100644
--- a/target/riscv/cpu_helper.c
+++ b/target/riscv/cpu_helper.c
@@ -452,10 +452,11 @@ restart:
         hwaddr pte_addr;
         if (two_stage && first_stage) {
+            int vbase_prot;
             hwaddr vbase;
             /* Do the second stage translation on the base PTE address. */
-            get_physical_address(env, &vbase, prot, base, access_type,
+            get_physical_address(env, &vbase, &vbase_prot, base, access_type,
                                  mmu_idx, false, true);
             pte_addr = vbase + idx * ptesize;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]