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
>
>
>
