riscv: Don't use stage-2 PTE lookup protection flags
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 <alistair.francis@wdc.com> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Tested-by: Anup Patel <anup@brainfault.org> Message-id: 931db85d6890ed4bc2b527fd1011197cd28299aa.1585262586.git.alistair.francis@wdc.com Message-Id: <931db85d6890ed4bc2b527fd1011197cd28299aa.1585262586.git.alistair.francis@wdc.com>
This commit is contained in:
parent
3ca109c3f8
commit
3847289054
@ -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;
|
||||
|
Loading…
Reference in New Issue
Block a user