Progress (short week, 2 days):
* VIRT-65 [QEMU upstream maintainership]
+ We got 5.1 out the door. I think this is the first release
in the many years I've been handling them where we managed to
avoid needing an rc4.
+ Spent a fair amount of time helping Paolo to debug his conversion
of the QEMU build system to Meson. We managed to land that today.
+ First of the KVM Forum programme committee meetings
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ More progress with fp16 support work; another handful of insns done.
thanks
-- PMM
[VIRT-327 # Richard's upstream QEMU work ]
Patch review, all over the place.
Patches for pauth impdef algorithm.
Patches for mte WnR bit.
Patches for crypto/cipher cleanup.
[VIRT-349 # QEMU SVE2 Support ]
Split out 20 patches from the SVE2 patch set.
r~
- 2 half days off
== Progress ==
* GCC upstream validation:
- reported several regressions (trunk and release branches)
- committed 2 testcase fixes
* GCC
- resumed work on PR94758 (-mpurecode and cortex-m23). Patch almost ready
* benchmarking:
- Scripts to run coremark on stm32 now merged, working on using them
in production
* misc:
- infra patches/reviews
== Next ==
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
VirtIO RPMB ([STR-5])
=====================
- got program_key and get_write_counter implemented
- finally making progress, the rest "should" be easy ;-)
[STR-5] <https://projects.linaro.org/browse/STR-5>
[testing kernel]
<http://git.linaro.org/people/alex.bennee/linux.git/shortlog/refs/heads/test…>
[qemu tree] <https://github.com/stsquad/qemu/tree/virtio/vhost-user-rpmb>
VirtIO Portability Demo ([STR-13])
==================================
- spent some time getting the MachiatoBin up and running
- system now working with latest 5.8 kernel and KVM support confirmed
- still debugging Xen setup, will return to this when back from
holidays
- currently no graphics available - need to perform [minor surgery] on
the PCI bus
[STR-13] <https://projects.linaro.org/browse/STR-13>
[minor surgery]
<http://wiki.macchiatobin.net/tiki-index.php?page=MACCHIATObin+%28up+to+rev+…>
Upstream Work ([QEMU-109])
==========================
- posted [PATCH v4 00/40] testing/next (vm, gitlab, fixes) Message-Id:
<20200701135652.1366-1-alex.bennee(a)linaro.org> : done
- posted [PULL 00/16] various fixes for rc2 (semihosting, tcg, docker,
tests/vm) Message-Id:
<20200727122357.31263-1-alex.bennee(a)linaro.org>
- a little leadership committee review
[QEMU-109] <https://projects.linaro.org/browse/QEMU-109>
Completed Reviews [2/2]
=======================
[PATCH RFC 00/10] fix some comment spelling errors
Message-Id: <20200812101500.2066-1-zhaolichang(a)huawei.com>
[PATCH 0/2] target/arm: Implement an IMPDEF pauth algorithm
Message-Id: <2219f3f9-7894-f898-0cad-43eccaa2a70d(a)linaro.org>
Absences
========
- short week
- holiday 13th-28th Aug - see you in September
Current Review Queue
====================
* [PATCH] plugins: new syscalls plugin
Message-Id: <20200812115816.4454-1-matthias(a)weckbecker.name>
Added: <2020-08-12 Wed>
* [PATCH v2 00/14] Reverse debugging
Message-Id: <159714365354.18946.2967871683340522027.stgit@pasha-ThinkPad-X280>
Added: <2020-08-11 Tue>
* [PATCH 00/11] Run cross-compilation build tests in the gitlab-CI
Message-Id: <20200804170055.2851-1-thuth(a)redhat.com>
Added: <2020-08-04 Tue>
* [RFC v3 0/8] QEMU cpus.c refactoring part2
Message-Id: <20200803090533.7410-1-cfontana(a)suse.de>
Added: <2020-08-03 Mon>
--
Alex Bennée
== Progress ==
* GCC upstream validation:
- reported a few regressions / minor testcase fix
* benchmarking:
- Created the Jenkins job to run coremark on stm32 (added/updated
scripts for that)
* misc:
- infra patches/reviews
== Next ==
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
I got an email and an irc ping for
http://lab.llvm.org:8011/builders/lldb-aarch64-ubuntu/builds/6924
My change has no relation to the test failure.
Flaky bots aren't allowed to send email or ping, so either make it
non-flaky or make it not send stuff.
Thanks,
Nico
[VIRT-327 # Richard's upstream QEMU work ]
Patch review -- lots of riscv vector stuff.
Fix for PAUTH error indication.
Diagnosed an MTE KASAN problem
-- my theory is a guest os thread error.
Investigation into PAUTH slowdown.
r~
Realised I missed last week so bumper update.
VirtIO Initiative ([STR-9])
===========================
- Inter-VM device emulation (call on Mon 20th July 2020) Message-Id:
<20200715112342.GD18817(a)stefanha-x1.localdomain>
- posted [RFC PATCH v1 0/3] put arm64 kvm_config on a diet Message-Id:
<20200804124417.27102-1-alex.bennee(a)linaro.org>
- EGL Call
- saw an interesting breakdown from other team doing vhost-user
- OpenSynergy
- got a good idea of where they are heading and the various players
[STR-9] <https://projects.linaro.org/browse/STR-9>
VirtIO RPMB ([STR-5])
=====================
- got the return path working
- re-based my [testing kernel] and made more spec conforming tweaks
[STR-5] <https://projects.linaro.org/browse/STR-5>
[simplified testing branch]
<http://git.linaro.org/people/alex.bennee/linux.git/shortlog/refs/heads/revi…>
[kernel]
<http://git.linaro.org/people/alex.bennee/linux.git/shortlog/refs/heads/revi…>
[testing kernel]
<http://git.linaro.org/people/alex.bennee/linux.git/shortlog/refs/heads/test…>
VirtIO Portability Demo ([STR-13])
==================================
- spent some time getting the MachiatoBin up and running
[STR-13] <https://projects.linaro.org/browse/STR-13>
Upstream Work ([QEMU-109])
==========================
- posted [PATCH v4 00/40] testing/next (vm, gitlab, fixes) Message-Id:
<20200701135652.1366-1-alex.bennee(a)linaro.org> : done
- Debugging a failure on m68k with pgd_find_hole_fallback
- seems 4.17+ with no /proc leave mmap_min_addr = 0 and NOREPLACE
hits it
- rth pondering a fix, may get back to it on Monday
- More debugging of icount bug, looks like -icount sleep=off interacts
with [bug 1859021]
- posted [PULL 00/16] various fixes for rc2 (semihosting, tcg, docker,
tests/vm) Message-Id:
<20200727122357.31263-1-alex.bennee(a)linaro.org>
[QEMU-109] <https://projects.linaro.org/browse/QEMU-109>
[bug 1859021] <https://bugs.launchpad.net/qemu/+bug/1859021>
Completed Reviews [6/6]
=======================
[PATCH v2 0/2] linux-user: fix clock_nanosleep()
Message-Id: <20200722174612.2917566-1-laurent(a)vivier.eu>
- CLOSING NOTE [2020-07-24 Fri 21:47]
Queued to my tree
Added: <2020-07-22 Wed>
[PATCH v1 0/3] python/qemu: follow-up changes for ConsoleSocket
Message-Id: <20200717203041.9867-1-robert.foley(a)linaro.org>
- CLOSING NOTE [2020-07-24 Fri 21:47]
Queued to my tree
Added: <2020-07-18 Sat>
[virtio-dev] [PATCH v5 00/10] introduce virtio vhost-user backend device type
Message-Id: <20200518203721.7625-1-ndragazis(a)arrikto.com>
- CLOSING NOTE [2020-07-24 Fri 21:48]
Interesting stuff, sent a few terminology fixes
Added: <2020-07-15 Wed>
[PATCH v2] cputlb: Make store_helper less fragile to compiler optimizations
Message-Id: <20200724195128.2373212-1-scw(a)google.com>
[PATCH 0/4] Refactor get_fpstatus_ptr() ready for AArch32 fp16
Message-Id: <20200806104453.30393-1-peter.maydell(a)linaro.org>
[DRAFT PATCH 000/143] Meson integration for 5.2
Message-Id: <1596741379-12902-1-git-send-email-pbonzini(a)redhat.com>
Absences
========
- 2 days off sick
- "holiday" 13th-25th Aug
Current Review Queue
====================
* [PATCH 00/11] Run cross-compilation build tests in the gitlab-CI
Message-Id: <20200804170055.2851-1-thuth(a)redhat.com>
Added: <2020-08-04 Tue>
* [RFC v3 0/8] QEMU cpus.c refactoring part2
Message-Id: <20200803090533.7410-1-cfontana(a)suse.de>
Added: <2020-08-03 Mon>
* [PATCH 0/2] accel/tcg: remove implied BQL from cpu_handle_interrupt/exception path
Message-Id: <20200731125127.30866-1-robert.foley(a)linaro.org>
Added: <2020-07-31 Fri>
* [PATCH 0/3] float16 APIs and alternative sNaN handling
Message-Id: <1596102747-20226-1-git-send-email-chihmin.chao(a)sifive.com>
Added: <2020-07-30 Thu>
--
Alex Bennée
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ rc3 sent out. Optimistically hoping for release next week.
+ rebased the patchset converting QAPI doc-comments to rST
+ Fixed a bug in syndrome register values for copro insns trapped
from AArch32 to AArch64
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ Finished and sent out the patchset that cleans up the coproc
insn decode and corrects the NOCP handling
+ With assistance from RTH, figured out how to use gvec helpers
to implement fp16 for various Neon insns. Added fp16 support to
20 or so insns; still have 15 or so to go.
thanks
-- PMM
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ More release herding...
+ Sent fixes for some bugs:
- assertion in the imx_epit timer device when guest soft-reset it
- netduino2/netduinoplus2 forgot to configure system clock scale so
using SysTick in "run at CPU frequency" mode would hang
- most M-profile boards failed to make AIRCR.SYSRESETREQ actually
reset the system
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ More progress with fp16: all the VFP insns now handled, including
the new-for-fp16 ones. Still to do: all of Neon...
+ Spent some time working through the details of NOCP vs UNDEF
in the M-profile coprocessor space for the various revisions
of the architecture. v8.1M adjusts things a bit in this area
and I want to clean up this bit of QEMU's current code and
get the v8.1M bits right.
Fact: next Monday (3rd August) will be the 10th anniversary
of my secondment into Linaro!
-- PMM
[VIRT-327 # Richard's upstream QEMU work ]
Misc patch review.
- Largest bit is half of riscv 0.9 vector patch set.
Fix arm E2 bug in ptw_translate.
Fix arm E3 buts in direct kernel startup.
Fix linux-user chroot failure.
r~
[VIRT-327 # Richard's upstream QEMU work ]
Misc patch review.
[GCC]
I looked into Adhemerval's libgomp-scalability patch set. The code looks good,
and I can't see anything wrong.
The cancel-parallel-2 test that's reported to regress, does, sometimes. It
never fails for me on qemu-test (aarch64, tx1). It *only* fails under the
dejagnu test harness on x86_64 and ppc64le. When run by hand it succeeds,
always. I cannot explain that at all. I've run the testsuite with
OMP_DEBUG_ENV=verbose and see that the dejagnu environment is as expected.
Anyway, I can't make forward progress because I can't reproduce the problem
under controlled conditions.
r~
VirtIO Related Work ([STR-9])
=============================
- putting together a demo system with a MacchiatoBin - idea here
Message-Id: <871rlkmzbs.fsf(a)linaro.org>
- posted On doorbells (queue notifications) Message-Id:
<87r1tdydpz.fsf(a)linaro.org> for discussion on RTT
- posted Enhancing virtio-mmio for MSI (new card required?)
Message-Id:
<alpine.DEB.2.21.2007151407190.4124@sstabellini-ThinkPad-T480s>
- started reviewing [virtio-dev] [PATCH v5 00/10] introduce virtio
vhost-user backend device type Message-Id:
<20200518203721.7625-3-ndragazis(a)arrikto.com>
- VIRTIO Sync-up call
- mainly discussing reducing traps MMIO vs PCIe
- need some better figures to justify adding MSI to MMIO
[STR-9] <https://projects.linaro.org/browse/STR-9>
VirtIO RPMB ([STR-5])
- realised the virtio driver in the [kernel] sent extra frames I
wasn't expecting
[STR-5] <https://projects.linaro.org/browse/STR-5>
[kernel]
<http://git.linaro.org/people/alex.bennee/linux.git/shortlog/refs/heads/revi…>
Upstream Work ([QEMU-109])
==========================
- posted [PATCH v4 00/40] testing/next (vm, gitlab, fixes) Message-Id:
<20200701135652.1366-1-alex.bennee(a)linaro.org> : done
- posted [PATCH v2 00/11] misc fixes for rc0 (docker, plugins,
softfloat) Message-Id:
<20200713200415.26214-1-alex.bennee(a)linaro.org>
- posted [PULL 0/9] final misc fixes for 5.1-rc0 Message-Id:
<20200714095247.19573-1-alex.bennee(a)linaro.org>
- took a couple of Message-Id:
<20200715105542.14428-1-alex.bennee(a)linaro.org> attempt to finally
get merged Message-Id:
<20200715111455.19237-1-alex.bennee(a)linaro.org>
- posted [PATCH v1 0/5] candidate fixes for 5.1-rc1 (shippable,
semihosting, OOM tcg) Message-Id:
<20200717105139.25293-1-alex.bennee(a)linaro.org>
[QEMU-109] <https://projects.linaro.org/browse/QEMU-109>
Blog Post ([LBO-34])
====================
- finished writing the [evolution of the translator] blogpost, should
go up next week
[LBO-34] <https://projects.linaro.org/browse/LBO-34>
[evolution of the translator]
<https://docs.google.com/document/d/190BlYjSTt-nZSR8dNdOxptt-swOZiGnASndEuXo…>
Completed Reviews [4/4]
=======================
[PATCH for-5.1 0/4] Document virt and a few other Arm boards
Message-Id: <20200713175746.5936-1-peter.maydell(a)linaro.org>
[PATCH 0/2] python/qemu: follow-up changes for ConsoleSocket
Message-Id: <20200715204814.2630-1-robert.foley(a)linaro.org>
[PATCH 00/13] Reverse debugging
Message-Id: <159316678008.10508.6615172353109944370.stgit@pasha-ThinkPad-X280>
Lost patience with more merge failures.
[PATCH 0/5] linux-user: Support extended clone(CLONE_VM)
Message-Id: <87h7vbyowf.fsf(a)linaro.org>
Current Review Queue
====================
* [virtio-dev] [PATCH v5 00/10] introduce virtio vhost-user backend device type
Message-Id: <20200518203721.7625-1-ndragazis(a)arrikto.com>
Added: <2020-07-15 Wed>
* [PATCH v4 00/22] target/xtensa: implement double precision FPU
Message-Id: <20200711110655.20287-1-jcmvbkbc(a)gmail.com>
Added: <2020-07-13 Mon>
* [PATCH v3 00/19] mailmap: Add more entries to sanitize 'git log' output
Message-Id: <20200702173818.14651-1-f4bug(a)amsat.org>
Added: <2020-07-02 Thu>
* [PATCH v3 0/9] memory: assert and define MemoryRegionOps callbacks
Message-Id: <20200630122710.1119158-1-ppandit(a)redhat.com>
Added: <2020-06-30 Tue>
--
Alex Bennée
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ More wrangling of release stuff and unreliable infrastructure.
* VIRT-364 [QEMU support for ARMv8.1-M extensions]
+ Managed to find a few days to put in some more work pushing fp16
handling forwards. I now have implementations of fp16 for most of
the VFP insns (still todo: VCVT, VSEL, VMAXNM/VMINNM, VRINT*; then
the few insns that are new-for-fp16. Then all of Neon, which is larger.)
thanks
-- PMM
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ softfreeze this week, so a lot of handling of pull requests,
reviewing various patchsets, sorting through newly reported
Coverity issues, etc etc.
thanks
-- PMM
== Progress ==
* GCC upstream validation:
- reported a few regressions / minor testcase fix
- enabled gcc-testresults for release branches, which will send even more emails
* benchmarking:
- added HAL support for the stm32 board we have in the Lab. Will start
testing once the board is actually connected to a builder
* misc:
- infra patches/reviews
== Next ==
* Holidays next two weeks, back on July 28th
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
== Progress ==
* Uploaded binaries for llvm 10.0.1 rc3 and rc4
* More work on Morello (including docs)
== Plan ==
* More Morello
* On vacation between July 20 - 31
4 day week.
[VIRT-327 # Richard's upstream QEMU work ]
Bug hunting vs aa32 ldrex/strex. I had hoped it would be relatively easy to
reproduce -- just run something from the .NET testsuite -- but even getting
that far wasn't obvious. So I put that aside; let's see if Peter's request for
an actual reproducer gets results.
Bug hunting vs aa64 gcc sync-4.c as reported by clyon. I determined that it's
not the fault of the null-pointer dereference, and that something goes wrong
somewhere in libgcc's exception unwind prior to the c++ throw. But it doesn't
fail all of the time. And worse, the problem vanishes when randomize_va_space
is disabled. So I can neither get a "good" vs "bad" trace without needless
differences nor produce a failure under gdb. I should try again with rr and
see if that works...
r~
Linaro folks - why is this buildbot sending mail when it's already red
(looks like this buildbot has been red for a while, at least 11187
seems to be red for the same reason that 11188 is red - so the people
on this blame list aren't relevant)? That adds noise to the buildbot
results & makes it harder for developers to find actionable email.
On Mon, Jul 6, 2020 at 9:30 PM <llvm.buildmaster(a)lab.llvm.org> wrote:
>
> The Buildbot has detected a new failure on builder clang-cmake-armv7-full while building llvm.
> Full details are available at:
> http://lab.llvm.org:8011/builders/clang-cmake-armv7-full/builds/11188
>
> Buildbot URL: http://lab.llvm.org:8011/
>
> Buildslave for this Build: linaro-tk1-08
>
> Build Reason: scheduler
> Build Source Stamp: [branch master] 0c6b6e28e70c06a3cb4704d2d8f90829a689e230
> Blamelist: Amara Emerson <amara(a)apple.com>,Amy Kwan <amy.kwan1(a)ibm.com>,Biplob Mishra <biplmish(a)in.ibm.com>,David Blaikie <dblaikie(a)gmail.com>,Eric Christopher <echristo(a)gmail.com>,Jordan Rupprecht <rupprecht(a)google.com>,LLVM GN Syncbot <llvmgnsyncbot(a)gmail.com>,Nico Weber <thakis(a)chromium.org>,Sanjay Patel <spatel(a)rotateright.com>,Wolfgang Pieb <wolfgang_pieb(a)playstation.sony.com>,Yuanfang Chen <yuanfang.chen(a)sony.com>
>
> BUILD FAILED: failed build stage 2
>
> sincerely,
> -The Buildbot
>
>
>
== Progress ==
* GCC upstream validation:
- reported a few regressions
- added fortran to arm-none-eabi configs
- enabled gcc-testresults for most configurations, which now sends a
lot of emails
* GCC:
- PR94743 (IRQ handler and Neon registers): patch committed.
* benchmarking:
- cleanup of hal lib to run benchmarks on stm32, the board we have in
TCWG is different from the ones we used in ST, I'll have to update the
hal settings accordingly.
* misc:
- switch tcwg_gnu job to use our gcc-compare-results script, to be
able to ignore some tests with random results (especially under qemu)
== Next ==
* GCC/cortex-M testing improvements & fixes
* cortex-m benchmarking
