aboutsummaryrefslogtreecommitdiff
path: root/rust/qemu-api
diff options
context:
space:
mode:
authorPierrick Bouvier <pierrick.bouvier@linaro.org>2025-04-14 08:30:27 -0700
committerPeter Maydell <peter.maydell@linaro.org>2025-05-06 15:01:22 +0100
commite1781b38af5e5c2e8a4b8f11e3e54de393a82eb2 (patch)
tree94069c634355c151aaa7fb13accaa90e0a85338e /rust/qemu-api
parent63201878f1cab185110f4d738ca41e05689aebd7 (diff)
downloadqemu-e1781b38af5e5c2e8a4b8f11e3e54de393a82eb2.zip
qemu-e1781b38af5e5c2e8a4b8f11e3e54de393a82eb2.tar.gz
qemu-e1781b38af5e5c2e8a4b8f11e3e54de393a82eb2.tar.bz2
target/arm/ptw: fix arm_cpu_get_phys_page_attrs_debug
It was reported that QEMU monitor command gva2gpa was reporting unmapped memory for a valid access (qemu-system-aarch64), during a copy from kernel to user space (__arch_copy_to_user symbol in Linux) [1]. This was affecting cpu_memory_rw_debug also, which is used in numerous places in our codebase. After investigating, the problem was specific to arm_cpu_get_phys_page_attrs_debug. When performing user access from a privileged space, we need to do a second lookup for user mmu idx, following what get_a64_user_mem_index is doing at translation time. [1] https://lists.nongnu.org/archive/html/qemu-discuss/2025-04/msg00013.html Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org> Message-id: 20250414153027.1486719-5-pierrick.bouvier@linaro.org Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'rust/qemu-api')
0 files changed, 0 insertions, 0 deletions