[loongarch64-linux-user] cannot execute on systems with 16K page size
<!--
This is the upstream QEMU issue tracker.
If you are able to, it will greatly facilitate bug triage if you attempt
to reproduce the problem with the latest qemu.git master built from
source. See https://www.qemu.org/download/#source for instructions on
how to do this.
QEMU generally supports the last two releases advertised on
https://www.qemu.org/. Problems with distro-packaged versions of QEMU
older than this should be reported to the distribution instead.
See https://www.qemu.org/contribute/report-a-bug/ for additional
guidance.
If this is a security issue, please consult
https://www.qemu.org/contribute/security-process/
-->
## Host environment
- Operating system: Debian Sid
- OS/kernel version: 6.12.94
- Architecture: loongarch64
- QEMU flavor: qemu-loongarch64
- QEMU version: 11.0.2
- QEMU command line:
<!--
Give the smallest, complete command line that exhibits the problem.
If you are using libvirt, virsh, or vmm, you can likely find the QEMU
command line arguments in /var/log/libvirt/qemu/$GUEST.log.
-->
```
./qemu-loongarch64 /usr/bin/busybox
```
## Emulated/Virtualized environment
- Operating system: N/A
- OS/kernel version: N/A
- Architecture: loongarch64
## Description of problem
When running qemu-loongarch64 on loongarch64 systems with 16K page size, the executable cannot load the shared libraries correctly.
## Steps to reproduce
1. Install qemu-loongarch64 and busybox on a loongarch64 system
2. Execute qemu-loongarch64 /usr/bin/busybox
3. The execution will fail with error: `/bin/busybox: error while loading shared libraries: libresolv.so.2: failed to map segment from shared object`
## Additional information
<!--
Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
If using libvirt, libvirt logs and XML domain information may be relevant.
-->
Normally loongarch64 kernels use 16K page size by default. However, the user space emulator uses 4K page, which cannot work on 16K page size systems.
<!--
The line below ensures that proper tags are added to the issue.
Please do not remove it.
-->
issue