Re: [PATCH v5 13/31] linux-user: Explicitly untag memory management syscalls

2021-02-08 Thread Peter Maydell
On Mon, 8 Feb 2021 at 14:10, Peter Maydell wrote: > > On Wed, 3 Feb 2021 at 19:00, Richard Henderson > wrote: > > > > We define target_mmap et al as untagged, so that they can be > > used from the binary loaders. Explicitly call cpu_untagged_addr > > for munmap, mprotect, mremap syscall entry

Re: [PATCH v5 13/31] linux-user: Explicitly untag memory management syscalls

2021-02-08 Thread Peter Maydell
On Wed, 3 Feb 2021 at 19:00, Richard Henderson wrote: > > We define target_mmap et al as untagged, so that they can be > used from the binary loaders. Explicitly call cpu_untagged_addr > for munmap, mprotect, mremap syscall entry points. > > Add a few comments for the syscalls that are exempted

[PATCH v5 13/31] linux-user: Explicitly untag memory management syscalls

2021-02-03 Thread Richard Henderson
We define target_mmap et al as untagged, so that they can be used from the binary loaders. Explicitly call cpu_untagged_addr for munmap, mprotect, mremap syscall entry points. Add a few comments for the syscalls that are exempted by the kernel's tagged-address-abi.rst. Signed-off-by: Richard