Hello,
# TCWG CI — GDB
- Changed tcwg_gnu-build.sh to apply GDB testsuite patch to avoid infinite
loop in tcwg_gdb_check--master-arm jobs, while it isn't committed
upstream.
- Started investigating corrupt gdb.sum.1 file in
tcwg_gdb_check--master-arm jobs. I can't reproduce it by manually
running the CI's "make check-gdb" command line, nor by using ABE. I can
reproduce it with tcwg_gnu-build.sh though.
- Came up with validate_failures.py change to make it cope with the
corrupt gdb.sum.1 file, while the underlying cause isn't known.
Submitted the change upstream.
# TCWG Infrastructure
- Reviewed some Gerrit requests for our CI scripts.
# Misc
- Did some travel planning for Linaro Employee Meeting and GNU Tools
Cauldron.
--
Thiago
Project Orko
============
- more virtio-gpu discussion, blog post soon
Enable Arm Architecture in QEMU
===============================
- prep for KVM Forum talk
Other
=====
- various syncs
Absences
========
- KVM Forum next week
Current Review Queue
====================
TODO [RFC v2 0/6] Native Library Calls
Message-Id: <20230607164750.829586-1-fufuyqqqqqq(a)gmail.com>
=================================================================================================
TODO [PATCH] Add virtio-sound and virtio-sound-pci devices
Message-Id: <20230526204845.673031-1-manos.pitsidianakis(a)linaro.org>
==============================================================================================================================
TODO [PATCH v2 00/10] hw/virtio: Build various target-agnostic objects just once
Message-Id: <20230524093744.88442-1-philmd(a)linaro.org>
======================================================================================================================================
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
Progress:
* UM-2 [QEMU upstream maintainership]
- code review (including a new board-and-devices
patchseries for a TI Tiva C devboard)
- Put together an arm pull request
- Investigated some bug reports, sent patches:
* regression in Allwinner A10 interrupt controller
* hang in icount mode on microbit with Zephyr guest
* LDG doesn't return the right values when ATA==0
- prep for next week's KVM Forum trip
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- handling review comments and rebasing of decodetree
load/store conversion
- investigating a few issues I noticed in the process
-- PMM
Hello,
# TCWG CI — GDB
- Addressed review comments and sent v2 and v3 of the patch fixing loop
in gdb.reverse/step-reverse.exp. The testcase's original author gave his
Reviewed-by, now waiting for approval by a maintainer. In the meantime,
set up our CI to apply the patch locally.
- Sent patch to the GDB mailing list implementing configure option
'--with-additional-debug-dirs' to allow building a GDB binary with a
custom install prefix but which also looks for debug info in
/usr/lib/debug. This should solve the SIGILL issue on armhf-linux in our
CI, and allow a few more tests to run on aarch64-linux.
# TCWG Infrastructure
- Reviewed some Gerrit requests related to notification and baseline
updating.
--
Thiago
Hello,
# TCWG CI — GDB
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying to detect shared library loading/unloading. Noticed
that the problem happens only in tests that use the distro's toolchain
(either because they're for a language we don't build in ABE gcc, or
because GDB itself is built with the distro toolchain), so the impact
isn't as widespread as I initially thought. It still frequently causes
trouble for our CI loop though. Working on a fix.
- Investigated and fixed loop in gdb.reverse/step-reverse.exp that was
causing tcwg_gdb_check--master-arm-build jobs to get stuck, as
reported by Maxim. Posted patch to the GDB mailing list.
# TCWG Infrastructure
- Reviewed Gerrit requests about testing mailing list patches in our CI.
--
Thiago
Progress (another short week, May is great this year):
* UM-2 [QEMU upstream maintainership]
- More review on some of RTH's atomics related patchsets
- Put together an arm pull request
- Sent out a call for agenda items for QEMU Summit
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- decodetree load/store conversion done, patches sent out for review.
After this I plan to go back to the FEAT_MOPS implementation
(and then do the last part of the integer A64 decodetree
conversion later in this release cycle).
-- PMM
Hello,
# TCWG CI — GDB
- Investigating issue in CI jobs where touching all C files causes GDB
to show a warning about the source being newer than the executable.
This interferes with a few GDB tests.
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying to detect shared library loading/unloading. Found
out that the GDB testsuite binaries are using the distro's ld.so
rather than the one built by ABE and which is the one expected to be
used. Because we don't have debuginfo installed for the distro's
ld.so, we hit the GDB bug in armhf-linux. The ld.so built by ABE has
debuginfo and would avoid hitting the issue.
# TCWG Infrastructure
- Reworked CI job to sanity check tcwg_gnu_fast_check_{gcc,gdb} and
posted new version for review.
- Reviewed some Gerrit requests for jenkins-scripts and ABE.
--
Thiago
Progress (short week, three days):
* UM-2 [QEMU upstream maintainership]
- Sent a patch fixing a bug where we broke some M-profile uses
(resulting in assertion failures) when we added v8R support
* QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG]
- Implemented support for a new feature in the decodetree
generator that I need for the A64 decodetree conversion,
sent patches out for review
- More progress on A64 decodetree: loads and stores
-- PMM
Hello,
# TCWG CI — GDB
- Analysed a number of potential regressions found by our CI on
aarch64-linux and armhf-linux. They aren't exactly regressions but bug
fixes or new features that work on other arches (or perhaps whose
testcases correctly detect PASSes on other arches) but not on
aarch64-linux or armhf-linux.
- armhf-linux has an important problem where a bug with detecting shared
library loading/unloading is causing many tests to fail. The result is
that every new GDB commit that adds a test is flagged by the bisect
job. This was caused by a GDB commit from November 2022. Luis reported
it at the time and the patch author was going to look into it, but
this probably fell through the cracks. I'm investigating to understand
the problem better and provide a fix.
--
Thiago
