[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-riscv] [Qemu-devel] [PATCH v3 1/7] target/riscv: Don't set wri
|
From: |
Bin Meng |
|
Subject: |
Re: [Qemu-riscv] [Qemu-devel] [PATCH v3 1/7] target/riscv: Don't set write permissions on dirty PTEs |
|
Date: |
Fri, 16 Aug 2019 21:59:04 +0800 |
On Fri, Aug 16, 2019 at 5:41 AM Alistair Francis
<address@hidden> wrote:
>
> Setting write permission on dirty PTEs results in userspace inside a
> Hypervisor guest (VU) becoming corrupted. This appears to be because it
> ends up with write permission in the second stage translation in cases
> where we aren't doing a store.
>
> Signed-off-by: Alistair Francis <address@hidden>
> ---
> target/riscv/cpu_helper.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
Reviewed-by: Bin Meng <address@hidden>
- [Qemu-riscv] [PATCH v3 0/7] RISC-V: Hypervisor prep work part 2, Alistair Francis, 2019/08/15
- [Qemu-riscv] [PATCH v3 1/7] target/riscv: Don't set write permissions on dirty PTEs, Alistair Francis, 2019/08/15
- Re: [Qemu-riscv] [Qemu-devel] [PATCH v3 1/7] target/riscv: Don't set write permissions on dirty PTEs,
Bin Meng <=
- [Qemu-riscv] [PATCH v3 3/7] target/riscv: Create function to test if FP is enabled, Alistair Francis, 2019/08/15
- [Qemu-riscv] [PATCH v3 2/7] riscv: plic: Remove unused interrupt functions, Alistair Francis, 2019/08/15
- [Qemu-riscv] [PATCH v3 4/7] target/riscv: Update the Hypervisor CSRs to v0.4, Alistair Francis, 2019/08/15
- [Qemu-riscv] [PATCH v3 5/7] target/riscv: Use both register name and ABI name, Alistair Francis, 2019/08/15
- [Qemu-riscv] [PATCH v3 6/7] target/riscv: Fix mstatus dirty mask, Alistair Francis, 2019/08/15