Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Working on v2 of the gdbserver patches improving SVE support. Found
and fixed a memory leak in my code while preparing patches for
upstream submission. Continuing preparing the patches.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Analysed failures of “fast_check_gdb” CI jobs over the weekend. They
were caused by unrelated build issues in GCC and libstdc++.
--
Thiago
Project Stratos
===============
- finished [blog post for virtio-camera]
- now live [on web site]
- did a review of [virtio-loopback]
- started reviewing [PATCH v9 0/8] KVM: mm: fd-based approach for
supporting KVM Message-Id:
<20221025151344.3784230-1-chao.p.peng(a)linux.intel.com>
- trying to assess if user-space facing solution for memory sharing
[blog post for virtio-camera]
<https://linaro.atlassian.net/jira/core/projects/LBO/board?selectedIssue=LBO…>
[on web site]
<https://www.linaro.org/blog/the-challenges-of-abstracting-virtio/>
[virtio-loopback] <https://git.virtualopensystems.com/virtio-loopback>
vhost-device maintainer effort ([UM-196])
- debugged regression in virtio-vsock and QEMU
- should have some error message patches to post
[UM-196] <https://linaro.atlassian.net/browse/UM-196>
Single Binary ([QEMU-487])
==========================
- posted [PATCH for 8.0 v5 00/20] use MemTxAttrs to avoid current_cpu
in hw/ Message-Id: <20221111182535.64844-1-alex.bennee(a)linaro.org>
[QEMU-487] <https://linaro.atlassian.net/browse/QEMU-487>
QEMU Upstream Work ([UM-2])
===========================
- posted [PATCH for 7.2-rc1 v2 00/12] testing, docs, plugins, arm
pre-PR Message-Id: <20221111145529.4020801-1-alex.bennee(a)linaro.org>
- posted [PULL for 7.2 00/10] testing and doc updates Message-Id:
<20221115133439.2348929-1-alex.bennee(a)linaro.org>
- did a bunch of follow-up testing to shake out other console bugs
- posted [PATCH for 7.2-rc1 v2 00/12] testing, docs, plugins, arm
pre-PR Message-Id:
<20221111145529.4020801-1-alex.bennee(a)linaro.org>
- posted [PATCH for 7.2? v1 0/2] Arm GICv2 patches Message-Id:
<20221115134048.2352715-1-alex.bennee(a)linaro.org>
[UM-2] <https://linaro.atlassian.net/browse/UM-2>
Other
=====
- hackbox2 upgrade follow-up
- health check content
Completed Reviews [1/1]
=======================
[PATCH] ci: replace x86_64 macos-11 with aarch64 macos-12
Message-Id: <20221116175023.80627-1-berrange(a)redhat.com>
Absences
========
Current Review Queue
====================
TODO [PATCH v6 00/21] Drivers for gunyah hypervisor
Message-Id: <20221026185846.3983888-1-quic_eberman(a)quicinc.com>
==================================================================================================================
TODO [PATCH v2 0/1] tcg: add perfmap and jitdump
Message-Id: <20221114161321.3364875-1-iii(a)linux.ibm.com>
========================================================================================================
TODO [PATCH for-8.0 v3 00/45] tcg: Support for Int128 with helpers
Message-Id: <20221111074101.2069454-1-richard.henderson(a)linaro.org>
=====================================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
-- the usual release cycle work. Looks relatively quiet this
time around.
-- taking the opportunity to try to catch up on some of the for-8.0
code review
* QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG]
-- started thinking about how to implement FEAT_FGT. Looking at
the code where this ought to go, I found a minor bug with how
we implement the existing HSTR_EL2 traps, and a case where we
trap AArch32 ATS12NSO* with the wrong syndrome.
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Working on v2 of the gdbserver patches improving SVE support. Tested new
code for regressions in different systems and configurations and found
none. Preparing new version of the patches for upstream submission. Will
likely post them early next week.
--
Thiago
Project Stratos
===============
- finished [blog post for virtio-camera]
- did a review of [virtio-loopback]
[blog post for virtio-camera]
<https://linaro.atlassian.net/jira/core/projects/LBO/board?selectedIssue=LBO…>
[virtio-loopback] <https://git.virtualopensystems.com/virtio-loopback>
vhost-device maintainer effort ([UM-196])
- review work
Single Binary ([QEMU-487])
==========================
- cleaning up current_cpu in [with mxtxattrs]
- stumbled into regressions in the way of testing
- posted [PATCH for 8.0 v5 00/20] use MemTxAttrs to avoid current_cpu
in hw/ Message-Id: <20221111182535.64844-1-alex.bennee(a)linaro.org>
[QEMU-487] <https://linaro.atlassian.net/browse/QEMU-487>
[with mxtxattrs]
<https://github.com/stsquad/qemu/tree/memtxattrs/cpuid-v5>
QEMU Upstream Work ([UM-2])
===========================
- posted [PATCH for 7.2-rc1 v2 00/12] testing, docs, plugins, arm
pre-PR Message-Id: <20221111145529.4020801-1-alex.bennee(a)linaro.org>
[UM-2] <https://linaro.atlassian.net/browse/UM-2>
Other
=====
- hackbox2 upgrade follow-up
- health check content
Completed Reviews [7/7]
=======================
[PATCH 00/24] accel/tcg: Rewrite user-only vma tracking
Message-Id: <20221006031113.1139454-1-richard.henderson(a)linaro.org>
[PATCH v1 00/12] Introduce xenpv machine for arm architecture
Message-Id: <20221015050750.4185-1-vikram.garhwal(a)amd.com>
[PATCH] Run docker probe only if docker or podman are available
Message-Id: <20221030083510.310584-1-sw(a)weilnetz.de>
[PULL 3/3] linux-test (tests/tcg/multiarch/linux-test.c) add check
Message-Id: <1626902375-7002-4-git-send-email-tsimpson(a)quicinc.com>
[PATCH v5 00/18] tests/qtest: Enable running qtest on Windows
Message-Id: <20221006151927.2079583-3-bmeng.cn(a)gmail.com>
[PATCH v1 00/12] Introduce xenpv machine for arm architecture
Message-Id: <20221015050750.4185-1-vikram.garhwal(a)amd.com>
[PATCH RFC 0/1] tcg: add perfmap and jitdump
Message-Id: <20221012051846.1432050-1-iii(a)linux.ibm.com>
Absences
========
Current Review Queue
====================
TODO [PATCH for-8.0 v3 00/45] tcg: Support for Int128 with helpers
Message-Id: <20221111074101.2069454-1-richard.henderson(a)linaro.org>
=====================================================================================================================================
TODO [PATCH v3 0/7] memory: prevent dma-reentracy issues
Message-Id: <20221028191648.964076-1-alxndr(a)bu.edu>
===========================================================================================================
TODO [QEMU][PATCH v2 0/5] Introduce Xilinx Versal CANFD
Message-Id: <20221022054746.28217-1-vikram.garhwal(a)amd.com>
==================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
-- identified another piece of the reset mechanics that can be
tractably cleaned up: I think we should be able to get
everything (effectively) moved over to the 3-phase reset system
-- sent out various for-8.0 patchsets that convert devices that
were using device_class_set_parent_reset(), since getting rid
of that function is step 1 of that cleanup
-- code review etc
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Confirmed that gdbserver doesn't send a new XML target description
over the wire when the vector length changes, so there's no impact of
these patches on the amount of remote protocol traffic, which was a
concern for GDB maintainers.
- Started doing some up code cleanup and regression tests to prepare for
submitting v2 of the patches.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Committed Gerrit change request adding the new CI job¹ to run fast
subset of GDB tests, which also has stable results. The list of tests
comes from Sourceware's builder project.
--
Thiago
¹ https://ci.linaro.org/view/tcwg_gnu_native/job/tcwg_gnu_native_fast_check_g…
Progress:
* UM-2 [QEMU upstream maintainership]
-- investigated and thought a bit more about a race condition involving
display devices. I know think I understand the problem but the
best idea I could come up with for a solution is pretty painful...
(Still hoping for feedback on whether I've missed something.)
-- collated and sent out a pull request with various bug fixes for rc0
-- sent some more reset-cleanup patches (these will be for 8.0)
-- PMM
Hi guys,
I will attempt to join today, but we've been finding that connectivity is dependent on the
number of rain drops and/or hail in between here and the mast. So I'm not overly hopeful
for later this evening.
Status report:
- Fixed a failure in my x86 TARGET_TB_PCREL patches, which caused
non-booting of some images (in today's tcg PR).
- Revised the TCGv_i128 patch set (not yet posted).
- Lots of work on accel/tcg/{cputlb,user-exec}.c, to honor
atomicity requirements of FEAT_LSE2.
Next up: Adding qemu_ld/st helpers and patterns for i128.
r~
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Finished implementing Luis' idea of having a process-wide target
description in addition to the thread-specific one. Started checking
changes for regressions.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Usual code review and patch handling work
- Cross-checked our boot.c code against the kernel's booting.rst,
and sent patch fixing a few EL3 config bits we weren't setting
- Sent out the minutes from QEMU Summit
* QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG]
- Wrote and sent out patches to implement the extra traps
required for FEAT_EVT
-- PMM
Hello,
# [GNU-796] Stabilise GDB testsuite results in the CI
- Reworked and committed Gerrit change request for jenkins-scripts
adding a new CI job definition in tcwg_gnu-build.sh.
- Also reworked and committed another one to the same script adding a
default manifest file if one isn't specified on the command line.
# [GNU-767] Support changing SVE vector length in remote debugging
- Implemented Luis' suggestion of assuming that if ptrace can't read the
SVE state, then SVE is disabled (which is what gdbserver does before
my patches). It turns out that the only situation where this happens,
gdbserver doesn't actually care about the target description.
- Started exploring/implementing Luis' idea of having a process-wide
target description in addition to the thread-specific one. As Luis
suggests, it may simplify the code.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Usual code review and patch handling work
- Spent a couple of days investigating a long-standing intermittent
test case failure booting a kernel on the raspberry pi. This turned
out to be caused by two linked bugs:
- the test framework unhelpfully disconnects immediately from the
guest serial console when the test ends, rather than staying
connected until the QEMU process exits to capture all the output
- QEMU's socket chardev loses data when the remote end closes the
connection if the guest UART hasn't read all of it
So the test was failing because the guest sometimes only saw
the 'h' of the final 'halt' command the test sent...
- Investigated and fixed a regression caused by some of last week's
reset patches. (Turns out the patch to fix it had been sent back
in 2021 but we accidentally dropped it on the floor. Oops.)
thanks
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued incorporating suggestions from Luis' review of the patches.
Working on a few regressions I introduced in the process.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Started addressing Maxim's comments to my change requests for
jenkins-scripts.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Started looking again at QEMU's rather messy set of reset related APIs.
Dug out the half-a-plan I wrote up a long time back and refreshed my
memory of what I was hoping we might be able to do.
- As an initial step, wrote some patches to get rid of uses of
several deprecated reset-related functions so that I only have to
think about one set of functions and not two...
-- PMM
Hello,
I haven't sent a report since week #36. For that reason, this report
covers three weeks.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Implemented CI job to run fast GDB tests based on the list from
Sourceware's builder. Submitted Gerrit change requests for
jenkins-scripts and ci/job/configs.
- Posted Gerrit change request for jenkins-scripts with an improvement
to tcwg_gnu-build.sh to use a default path for the artifacts file if
one isn't given on the command line.
# [GNU-767] Support changing SVE vector length in remote debugging
- Started incorporating suggestions from Luis' review of the patches.
# Community participation
- Reviewed mailing list patch “[PATCH v3] gdb/arm: Handle lazy FPU
register stacking”
- Attended GNU Tools Cauldron 2022.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- sent out patch which adds a retry-on-EINTR loop to KVM_CREATE_VM ioctls
- wrote up the draft of the minutes for the QEMU Summit for review
- more code review and pullrequest collation (notably the Arm v8R support
patchset)
* QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG]
- read up on the remaining unimplemented features under this epic;
closed out one we'd already implemented, and wrote up enough detail
on the others to be happy with putting them all into the current
sprint (they're all small features)
- started looking at FEAT_GTG
thanks
-- PMM
Project Stratos
===============
- held poll for next meeting
- started planning for virtio-camera/sensor
QEMU Upstream Work ([UM-2])
===========================
- posted [PULL for 7.1 0/3] memory leak and testing tweaks Message-Id:
<CAFEAcA8oPjTq9quHxOCSczckwmmBSP0fY6dtCzwrNs59pMrNCw(a)mail.gmail.com>
- sadly one patch had to be reverted as it exposed another race
- posted [PATCH v1 00/10] plugins/next (disas, monitor, docs, execlog)
Message-Id: <20220921160801.1490125-6-alex.bennee(a)linaro.org>
- posted [PULL 00/30] testing updates (docker, avocado, deprecate
32bit BE MIPS) Message-Id:
<20220920171533.1098094-4-alex.bennee(a)linaro.org>
[UM-2] <https://linaro.atlassian.net/browse/UM-2>
Update docs
- mention -d plugin
- document features of tests/plugin plugins
- clean up command lines to drop builddir
KVM Forum
=========
- Attended KVM forum, gave a talk, helper with another
Completed Reviews [3/3]
=======================
[PATCH 00/62] target/arm: Implement FEAT_HAFDBS
Message-Id: <20220703082419.770989-1-richard.henderson(a)linaro.org>
[RFC PATCH v2] gdbstub: only send stop-reply packets when allowed to
Message-Id: <ba99db564c3aeb1812bdfbc9116849092334482f.1661362557.git.quic_mathbern(a)quicinc.com>
[RFC 0/4] Support interactions between TCG plugins
Message-Id: <20220901182734.2987337-1-fasano(a)mit.edu>
Absences
========
Current Review Queue
====================
TODO [PATCH v4 0/7] tcg: pc-relative translation blocks
Message-Id: <20220906091126.298041-1-richard.henderson(a)linaro.org>
=========================================================================================================================
TODO [PATCH 00/51] tests/qtest: Enable running qtest on Windows
Message-Id: <20220824094029.1634519-1-bmeng.cn(a)gmail.com>
========================================================================================================================
TODO [PATCH v2 00/33] accel/tcg + target/arm: pc-relative translation
Message-Id: <20220816203400.161187-1-richard.henderson(a)linaro.org>
=======================================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
- attended KVM Forum
- catching up with code review, email, etc...
- sent out an Arm pullreq now 7.2 has opened up for development
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- diagnosed a regression caused by the recent FEAT_PMUv3p5 changes
and sent out a fix
KVM Forum trip highlights:
* it was good to be able to meet people face-to-face again after
several years
* Cloud use of Arm hardware has now got to the point where big cloud
companies are working through performance issues and then coming to
present about it; e.g. Google did a talk about perf issues during
migration on an Ampere Altra setup. The solutions seem to be a mix
of "apply the lessons and fixes we already went through with x86"
and "architecture fixes coming down the pipe" (in this case
FEAT_TLBIRANGE and FEAT_BBM).
* lots of Google talks about pKVM (using hypervisor hardware on
Android to improve security). In fact lots of Google all over --
apparently they've made a big push to do more upstream kernel work
and as a result a large chunk of the kernel KVM commits come from
them...
* talk from Xilinx (now with AMD) about doing co-simulation of QEMU
and RTL -- basically (with the aid of a lot of non-upstream stuff)
having QEMU talk to a SystemC environment so you can have eg an
emulated ethernet card in FPGA that plugs into a QEMU VM. This kind
of thing is a use-case which historically upstream have not really
been interested in addressing.
* Which brings me to the BoF session on emulation, perhaps the most
interesting bit of the conference for me. There was a lot of
discussion about whether QEMU might move closer to what I call the
"bag of lego bricks" paradigm, where it provides device models and
users might be able to configure it at runtime to stitch them
together, perhaps adding out-of-tree devices of their own. There is
clearly interest in this (eg from attendees from Xilinx and
Qualcomm); the sticking point is that from upstream's perspective
this seems like "you should do this thing that will benefit us and
not you". My take is that whether this goes anywhere will depend on
whether those who would like this are prepared to coordinate
together to present themselves as a group who are willing to dig in
to the necessary upstream refactoring and cleanup that would be a
precondition for having something like this be anywhere near
supportable, i.e. that they're a group who will come and help
rather than merely consume...
* There was also a shorter discussion in the BoF about the idea of
"heterogenous CPU emulation", eg one QEMU model with both Arm and
Microblaze CPUs. This is not conceptually controversial, it's just
a lot of work. It seemed like maybe a few folk now care enough to
have a go at it.
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Made a few last-minute adjustments to the code and fixed a couple of
regressions on x86_64-linux. Re-ran regression tests on x86_64-linux and
aarch64-linux. Wrote cover letter and descriptions for all the patches.
- Finally posted the patch series upstream¹.
# [GNU-796] Stabilize GDB testsuite results in the Linaro CI
- Started working on this issue. Currently adding a new CI job to run the
same small subset of GDB testcases that Sourceware's buildbot runs. This
subset runs quickly and has stable results so the job will be a good
canary to check that the CI infrastructure is working correctly.
--
Thiago
¹https://inbox.sourceware.org/gdb-patches/20220908064151.3959930-1-thiago.b…
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Cleaned up code for upstream submission, and divided it into patches.
A couple of the patches affect other architectures and OSes, so made
sure the code builds on as many combinations I can test, and now doing
final regression testing on some of them. I'm hoping to finally send
the patches upstream early next week.
--
Thiago
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Finished fixing regressions in my changes to gdbserver for debugging an
inferior which changes the SVE length.
- Started cleaning up code for upstream submission and dividing it into
patches.
# Community participation
- Reviewed mailing list patches:
- [PATCH,v3] [aarch64] Fix removal of non-address bits for PAuth
- [PATCH 1/2] gdb: Fix deleted thread when issuing next command
- [PATCH 2/2] gdb: Improve the resuming of the stepped thread
--
Thiago
Progress (short week, 3 days):
* UM-2 [QEMU upstream maintainership]
- pretty much just tying up loose ends and doing other
miscellaneous bits and pieces
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- respin, resend of PMUv3p5 series
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- v2 of the patches fixing a small SVE bug when debugging in native mode
an inferior which changes the SVE length was committed upstream.
- Continued working on fixing regressions in my changes to gdbserver for
debugging an inferior which changes the SVE length.
--
Thiago
Project Stratos
===============
- continued working on [adding vhost-user-rng to crosvm]
- this is to demo Stratos on Gunyah
- re-built guest kernel with known working backend
- it works :-)
- initial review of Viresh's slides for KVM Forum talk
[adding vhost-user-rng to crosvm]
<https://github.com/stsquad/crosvm/tree/add-vhost-user-rng>
vhost-device maintainer effort ([UM-196])
- prepared a clean-up [branch for new queue interface]
- spent time testing and realised it had broken things
[branch for new queue interface]
<https://github.com/stsquad/vhost-device/tree/update-queue-interface>
QEMU Upstream Work ([UM-2])
===========================
- posted [PULL for 7.1 0/3] memory leak and testing tweaks Message-Id:
<CAFEAcA8oPjTq9quHxOCSczckwmmBSP0fY6dtCzwrNs59pMrNCw(a)mail.gmail.com>
- sadly one patch had to be reverted as it exposed another race
[UM-2] <https://linaro.atlassian.net/browse/UM-2>
Completed Reviews [1/1]
=======================
[PATCH 00/62] target/arm: Implement FEAT_HAFDBS
Message-Id: <20220703082419.770989-1-richard.henderson(a)linaro.org>
Absences
========
- will take a long w/e for August BH
Current Review Queue
====================
TODO [PATCH v2 00/33] accel/tcg + target/arm: pc-relative translation
Message-Id: <20220816203400.161187-1-richard.henderson(a)linaro.org>
=======================================================================================================================================
TODO [PATCH for-7.2 00/21] accel/tcg: minimize tlb lookups during translate + user-only PROT_EXEC fixes
Message-Id: <20220812180806.2128593-22-richard.henderson(a)linaro.org>
===========================================================================================================================================================================
--
Alex Bennée
Progress:
* UM-2 [QEMU upstream maintainership]
- respin and resend for a few patchsets after code review
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- identified what the old ARMv8.5-CMODX feature is now
("prefetch speculation protection") and confirmed that
QEMU is already compliant with the instruction fetch ordering
requirements so there's no coding work required here
- Checked that we implement FEAT_ETS already and sent patches
to advertise it in the ID registers
- Checked that we already conform to the ordering rules required
by "prefetch speculation protection"
- Discovered that we accidentally fail to RAZ for a big chunk
of the reserved-for-new-AArch32-ID-registers space for v8 CPUs;
sent patches fixing that
thanks
-- PMM
Hello Linaro Toolchain Working Group,
clang-arm64-windows-msvc is red for 12 days. The host is missing a correct
version of msvc.
Is somebody looking at this?
Thanks
Galina
Progress:
* UM-2 [QEMU upstream maintainership]
- usual release cycle work: rounded up a couple of last-minute
fixes for "whoops, this crashes" bugs and some safe changes like
docs typo fixes.
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- Finished implementing the FEAT_PMUv3p5 work. In the process of
testing it I found a handful of bugs in our existing PMU
emulation code. Sent out the patchset which fixes those bugs and
adds FEAT_PMUv3p5.
- Cleaned up the epic to remove subtasks we aren't going to
implement (FEAT_SPE, FEAT_TRF), and added one for "actually
define the new CPU model"
- FEAT_LSE2 is the only remaining real work here, and it is
probably going to be seriously tricky...(i.e. I hope to leave
it to RTH ;-))
-- PMM
Project Stratos
===============
- continued working on [adding vhost-user-rng to crosvm]
- this is to demo Stratos on Gunyah
- backend comes up and device is detected but queues are not
consumed
- had some initial discussions with Viresh about talk structure for
KVM Forum
[adding vhost-user-rng to crosvm]
<https://github.com/stsquad/crosvm/tree/add-vhost-user-rng>
vhost-device maintainer effort ([UM-196])
- prepared a clean-up [branch for new queue interface]
[UM-196] <https://linaro.atlassian.net/browse/UM-196>
[branch for new queue interface]
<https://github.com/stsquad/vhost-device/tree/update-queue-interface>
QEMU Upstream Work ([UM-2])
===========================
- posted [PATCH for 7.1 v1 0/8] memory leaks and speed tweaks
Message-Id: <20220811151413.3350684-8-alex.bennee(a)linaro.org>
- will drop most of the speed tweaks until 7.2 opens
[UM-2] <https://linaro.atlassian.net/browse/UM-2>
Completed Reviews [1/1]
=======================
[PATCH 00/62] target/arm: Implement FEAT_HAFDBS
Message-Id: <20220703082419.770989-1-richard.henderson(a)linaro.org>
Absences
========
- 2 day week next week
- will take a long w/e for August BH
--
Alex Bennée
Hello,
I noticed that I didn't send a report for week #30. Sorry about that. For
that reason, this report covers two weeks.
# [GNU-767] Support changing SVE vector length in remote debugging
- Prepared and submitted upstream a fix and a testcase for a small SVE bug
when debugging in native mode an inferior which changes the SVE length.
Luis reviewed it and I submitted v2 addressing his comments.
# Misc
- Was out for 2 days.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- more investigation, triage and fixing of minor bugs in run-up to release
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- starting working on the PMUv8p5 enhancements. These consist of a couple
of new cycle-counter-disable bits (easy) and extension of the event
counters to 64 bits (more tricky). So far I have code for the easy part
and have made a start on the hard part...
-- PMM
Progress:
* UM-2 [QEMU upstream maintainership]
- debugged and sent patch to fix a bug in timer_create
syscall support in linux-user on certain host libcs
- tried and failed to repro a bug where semihosting SYS_HEAPINFO
was returning addresses in the flash rom
- more Coverity issue triage -- now have finished triage of
everything that isn't either in the test suite or an
"insecure data handling" issue. Sent patches for a few
issues, prodded other people about some more...
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Fixed last bug which prevented the sve-ioctls QEMU testcase to be
correctly stepped through in gdbserver. The next step is checking
whether any regression was introduced by my changes, and clean up the
code.
* In the process, spotted small bug in GDB when stepping through the
sve-ioctls QEMU testcase using the existing native support. Started
preparing a patch to submit upstream.
# [LLVM-769] Linaro CI
* Increased tcwg-fx-02 ccache max size to 40 GB.
* Learned a bit about Zorg and started adding “depends_on_projects”
field to builders running on Linaro workers.
--
Thiago
Hi,
I noticed that bots like flang-aarch64-latest-gcc are quite slow and could
benefit from enabling ccache. Could you make it available on the system so
it could be turned on for all these builds?
Thanks,
--
Mehdi
Progress:
* UM-2 [QEMU upstream maintainership]
- softfreeze this week; lots of pullrequest merging
- spent some time going through our backlog of Coverity Scan issues, triaging
them and sending patches for some of them
- sent a patchset fixing portability issues in our configure script which
had crept in recently and were causing problems on OpenBSD and NetBSD
- sent out the invite emails for QEMU Summit
-- PMM
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Rebased the actual SVE vector length changes on top of the stabilised
per-thread target descriptions changes. Now stabilising the result. Fixed
a couple of problems found when remote-debugging QEMU's sve-ioctls test
binary, currently looking into a third one.
# Linaro CI's GDB testsuite results
* Updated and expanded the LLVM Docker Buildbot Maintenance wiki page with
the information about ccache setup I gathered in the past few days. Also
added a link to it to the Buildkite Bot Maintenance wiki page since
libstdc++ buildkites uses the same configuration.
* Increased ccache max size in GNU build jobs on tcwg-jade-02.
* Updated ABE repo's tested branch with my commits from last week to
improve the GDB testsuite results. Confirmed that the GDB testsuite went
from 538 unexpected failures to 307. There's still room for improvement
though.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- took over pullreq handling from RTH for the next couple of weeks
- wrote and sent patches that fix a mishandling of Secure stage 2
translation caused by QEMU not noticing that some config bits are
in VTCR_EL2 and some in VSTCR_EL2. Removed an ancient microoptimization
that was getting in the way of fixing that.
- sent patch fixing incorrect syndrome value for data abort on some
post-indexed load/store insns
- RTH's SME patchset is now upstream, so now would be a good time to
test it if anybody has compiler test cases or similar they were
thinking of running under QEMU
- softfreeze next Tuesday: started reviewing and collecting up
minor patches for a pre-freeze pullreq
-- PMM
Hello,
I went through the LLVM build bots (and also the libc++ buildkites) and
increased their ccache max size. There was a big impact on the flang
builds on tcwg-jade-01 (which went from 1h–2h to 10min–30min), but not
on other builds. One reason is probably that since I made this change
earlier today, there wasn't time yet to finish enough several-hours-long
builds to warm up the caches.
Since different machines have different disk sizes and free space I
chose different ccache max sizes for them, as follows:
* tcwg-fx-02 hosts the following build bots:
- clang-aarch64-sve-vls-2stage
- clang-aarch64-sve-vls
- clang-aarch64-sve-vla-2stage
- clang-aarch64-sve-vla
All share the same ccache. I changed its max size to 20 GB. It's not a
lot, but this machine is also used as a dev box so I though it would
be good to preserve a fair amount of space.
* tcwg-jade-01 hosts the following build bots:
- clang-armv8-lld-2stage
- clang-armv7-vfpv3-2stage
- clang-armv7-global-isel
- clang-armv7-quick
- clang-armv7-2stage
- clang-armv7-lnt
- flang-aarch64-latest-gcc
- flang-aarch64-rel-assert
- flang-aarch64-release
- flang-aarch64-latest-clang
- flang-aarch64-debug
- flang-aarch64-out-of-tree
- flang-aarch64-sharedlibs
- flang-aarch64-dylib
- clang-aarch64-full-2stage
- clang-aarch64-global-isel
- clang-aarch64-lld-2stage
- clang-aarch64-quick
All armv7 and armv8 bots share one ccache, and all aarch64 bots share
another. I changed the max size of each one to 100 GB.
* tcwg-jade-04 hosts the following build bots:
- lldb-aarch64-ubuntu
- lldb-arm-ubuntu
- buildkite-linaro-armv8-libcxx-01
- buildkite-linaro-armv8-libcxx-02
- buildkite-linaro-armv8-libcxx-03
- buildkite-linaro-armv8-libcxx-04
The buildkite bots share a 50 GB ccache, while lldb-arm-ubuntu uses
another 50 GB ccache due to being based on a different distro version.
And lldb-aarch64-ubuntu also uses its own 50 GB ccache.
* tcwg-llvmbot_tk1-01.tcwglab hosts the following build bot:
- silent-linaro-tk1-01
I changed the max cache size to 10 GB. There's not a lot of free space
on the machine.
* tcwg-llvmbot_tk1-03.tcwglab hosts the following build bot:
- normal-linaro-tk1-02
I changed the max cache size to 20 GB.
* tcwg-llvmbot_tk1-05.tcwglab hosts the following build bot:
- silent-linaro-tk1-08
I changed the max cache size to 10 GB.
* The following tcwg-llvmbot_tk1-* machines are currently unreachable so
I couldn't examine them:
- tcwg-llvmbot_tk1-02.tcwglab
- tcwg-llvmbot_tk1-04.tcwglab
* The following tcwg-llvmbot_tk1-* machines are running an llvmbot
container but no builder container, so I didn't change their ccache
configuration:
- tcwg-llvmbot_tk1-06.tcwglab
- tcwg-llvmbot_tk1-07.tcwglab
- tcwg-llvmbot_tk1-08.tcwglab
- tcwg-llvmbot_tk1-09.tcwglab
* tcwg-jade-02 is a GNU builder, and from peeking into a few containers
running build jobs I have the impression that it doesn't use ccache.
Should I look into it?
* Going through our ssh config file I didn't find these build bots that
are listed at http://llvm.validation.linaro.org/ so I didn't check
their ccache usage:
- clang-arm64-windows-msvc-2stage
- clang-arm64-windows-msvc
- clang-arm64-windows-msvc-2stage
- clang-arm64-windows-msvc
- clang-native-arm-lnt-perf
- clang-armv7-vfpv3-full-2stage
- clang-thumbv7-full-2stage
- libcxx aarch64
- libcxx aarch64 -fno-exceptions
--
Thiago
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Analysed and fixed a couple more regressions in my branch. The change to
per-thread target descriptions in gdbserver (which was the more
challenging part) is now free of regressions. Now cleaning up the part
that actually deals with the SVE vector length change.
# Linaro CI's GDB testsuite results
* Increased ccache's max size on most build bots. Sent email to the
linaro-toolchain list summarising the current status of their ccache
setup.
* Started looking more closely into how ccache configuration is put
together in our container scripts to document it on the wiki (together
with the steps I took to change the ccache max size).
--
Thiago
Hello Linaro Toolchain Working Group,
linaro-clang-armv8-lld-2stage <https://lab.llvm.org/buildbot/#/workers/140>
has been red since June 7th.
Is anybody looking at the issue?
Thanks
Galina
Progress: (short week, 3 days)
* UM-2 [QEMU upstream maintainership]
- More code review, as softfreeze is now quite close. I think we've
finally got there with the SME patchset (the remaining problems
with v5 were very minor)
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- QEMU-315 OS Lock/DoubleLock work now upstream
-- PMM
Hello,
# Linaro CI's GDB testsuite results
* Implemented new version of change in the Abe shell script to correctly
set auto-load-safe-path so that GDB can load libthread_db.so.1. Since
GDB's configure script needs to be passed an argument containing
literal dollar signs, use '@@' instead of '$' to avoid the shell
misinterpreting it and substitute at the point of use. This version
worked and was merged to the Abe repo.
* Implemented and merged change in the Abe shell script to set variables
pointing to language-specific target tools only if they are present in
the path. This fixes Ada test failures in the GDB testsuite.
* Implemented and merged improvement to our tcwg_gnu-build.sh script to
allow specifying on the command line the Abe repo and branch to use.
# [GNU-767] Support changing SVE vector length in remote debugging
* Analysed and fixed a couple more regressions in my branch.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Code review (misc, plus another round on the SME patchset)
- KVM Forum programme committee work
* QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG]
- Wrote and sent patches that deal with the last of the "small and
uninteresting" dependencies of the V1 support epic (this one covers
Feat_DoubleLock, which lets guest OSes suppress debug events as
part of their power-down-a-CPU sequence)
-- PMM