| Message ID | 20240515173132.2462201-1-gustavo.romero@linaro.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | Add MTE stubs for aarch64 user mode | expand |
Gustavo Romero <gustavo.romero@linaro.org> writes: > This patchset adds the stubs necessary to support GDB memory tagging > commands on QEMU aarch64 user mode. On application I'm getting the following failure on configure which makes me think something is missing: Program scripts/undefsym.py found: YES (/home/alex/lsrc/qemu.git/builds/all/pyvenv/bin/python3 /home/alex/lsrc/qemu.git/scripts/undefsym.py) Program scripts/feature_to_c.py found: YES (/home/alex/lsrc/qemu.git/builds/all/pyvenv/bin/python3 /home/alex/lsrc/qemu.git/scripts/feature_to_c.py) ../../meson.build:3851:4: ERROR: File gdb-xml/aarch64-mte.xml does not exist. A full log can be found at /home/alex/lsrc/qemu.git/builds/all/meson-logs/meson-log.txt ninja: error: rebuilding 'build.ninja': subcommand failed FAILED: build.ninja /home/alex/lsrc/qemu.git/builds/all/pyvenv/bin/meson --internal regenerate /home/alex/lsrc/qemu.git /home/alex/lsrc/qemu.git/builds/all make: *** [Makefile:167: run-ninja] Error 1 Compilation exited abnormally with code 2 at Tue May 28 16:59:05
This patchset adds the stubs necessary to support GDB memory tagging commands on QEMU aarch64 user mode. These new stubs handle the qIsAddressTagged, qMemTag, and QMemTag packets, which allow GDB memory tagging subcommands 'check', 'print-allocation-tag', and 'set-allocation-tag' to work. The remaining memory tagging commands ('print-logical-tag' and 'with-logical-tag') will also work, but they don't rely on any stub because they perform local operations. Since the memory tagging stubs are not common to all architectures, this patchset also introduces three functions: set_query_supported_arch, set_gdb_gen_query_table_arch, and set_gdb_gen_set_table_arch. These functions can be used to extend the target-specific 'qSupported' feature string and the handlers for the 'q' (query) and 'Q' (set) packets. These new functions are used to add the MTE stubs for the aarch64 gdbstub. Note that this patchset requires a GDB that supports the qIsAddressTagged packet (recently added to GDB), so the gdbstub MTE tests introduced by it must be run using GDB's master branch, since the GDB in the distros hasn't picked up the change yet. Once GDB is built and installed locally, the tests can be exercised, for example, this way: make GDB=~/.local/bin/gdb run-tcg-tests-aarch64-linux-user -j 32 Cheers, Gustavo Gustavo Romero (4): gdbstub: Add support for target-specific stubs gdbstub: Add support for MTE in user mode tests: Gently exit from GDB when tests complete tests/tcg/aarch64: Add MTE gdbstub tests configs/targets/aarch64-linux-user.mak | 2 +- gdbstub/gdbstub.c | 108 +++++---- gdbstub/internals.h | 22 -- gdbstub/syscalls.c | 1 + include/exec/gdbstub.h | 86 ++++++- target/arm/cpu.c | 1 + target/arm/gdbstub.c | 321 +++++++++++++++++++++++++ target/arm/internals.h | 2 + tests/guest-debug/test_gdbstub.py | 2 +- tests/tcg/aarch64/Makefile.target | 11 +- tests/tcg/aarch64/gdbstub/test-mte.py | 86 +++++++ tests/tcg/aarch64/mte-8.c | 102 ++++++++ 12 files changed, 670 insertions(+), 74 deletions(-) create mode 100644 tests/tcg/aarch64/gdbstub/test-mte.py create mode 100644 tests/tcg/aarch64/mte-8.c