Re: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes on aarch64

like to check the others.) From: ci_not...@linaro.org Date: Monday, April 14, 2025 at 20:36 To: ohno.yasuy...@fujitsu.com , itou.tets...@fujitsu.com , t-kawash...@fujitsu.com Cc: maxim.kuvyr...@linaro.org , Peter Klausler Subject: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86

is anybody using QEMU's iwmmxt/xscale emulation for toolchain testing?

Hi; I'm wondering if anybody is using QEMU's iwmmxt/xscale emulation for toolchain testing. (My suspicion is the answer is "no".) This emulation isn't enabled by default, so to use it you would have to explicitly select an iwmmxt capable CPU (with -cpu or the QEMU_CPU environment variable). The re

Re: [Linaro-TCWG-CI] llvmorg-20-init-15723-gb2c363e2616d: 7 regressions on aarch64

Fixed by https://github.com/llvm/llvm-project/pull/120614. From: ci_not...@linaro.org Date: Wednesday, December 18, 2024 at 21:27 To: ohno.yasuy...@fujitsu.com , itou.tets...@fujitsu.com , t-kawash...@fujitsu.com Cc: maxim.kuvyr...@linaro.org , Peter Klausler Subject: [Linaro-TCWG-CI

LLVM-1446

The results now produced by flang(-new) for Fujitsu Fortran test 0676_0160 are better than the desired results of the test. The test uses the SUM intrinsic function to compute the sum of 100 complex numbers. These values are all identical. The new results from the SUM intrinsic function match

Re: [Linaro-TCWG-CI] llvmorg-20-init-7781-g0f973ac783aa: FAIL: 1 regressions on aarch64

The error message for that test is correct. From: ci_not...@linaro.org Date: Thursday, October 3, 2024 at 06:51 To: ohno.yasuy...@fujitsu.com , itou.tets...@fujitsu.com , t-kawash...@fujitsu.com Cc: maxim.kuvyr...@linaro.org , Peter Klausler Subject: [Linaro-TCWG-CI] llvmorg-20-init-7781

[ACTIVITY] report week ending 28 Jun

Progress: * UM-2 [QEMU upstream maintainership] - patch-review queue has filled up again; reviewed at least some patches ready for an arm pullreq - another KVM Forum PC meeting * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - realized that FEAT_AFP means we need to refactor our FPC

[ACTIVITY] report week ending 21 Jun

Progress: * UM-2 [QEMU upstream maintainership] + code review and target-arm pullreq + Coverity gardening: triage of new issues; update of component definitions + respin of "allow a second UART in virt machine" patchset from last year + KVM Forum programme committee work -- PMM __

[ACTIVITY] report week ending 7 Jun

Progress: * UM-2 [QEMU upstream maintainership] - updated our component definition regexes for Coverity Scan - sent patches with the followon cleanup RTH requested when reviewing my FEAT_WFxT patchset - code review - triage of new coverity issues -- PMM ___

[ACTIVITY] report week ending 31 May

Progress (short week, three days): * UM-2 [QEMU upstream maintainership] - another week of pretty much just code review: + more of RTH's decodetree conversion series (several rounds) + "Connect STM32L4x5 USART devices to the EXTI" v2 + "Check clock connection between STM32L4x5 RCC and p

[ACTIVITY] report week ending 23 May

Progress (short week, three days): * UM-2 [QEMU upstream maintainership] - spent pretty much all week working through the code review backlog that had built up while I was on holiday and at Connect: + RTH's patchset making various updates to the risu random-instruction-sequence teste

[ACTIVITY] report week ending 3 May

Progress: * UM-2 [QEMU upstream maintainership] - last bits of prep and admin for Connect - investigating what we should do with the MPIDR when the user specifies a topology setup when the CPU being emulated is or is not one with MPIDR.MT set. I had written this up as a "bites

[ACTIVITY] report week ending 26 Apr

Progress: * UM-2 [QEMU upstream maintainership] - made the 9.0 release and handed over pullreq processing to RTH for the 9.1 cycle - collected up and sent out the first target-arm pullreq for 9.1 - finished creating JIRA issues for QEMU for FEAT_* features to bring us into sync with

[ACTIVITY] report week ending 19 Apr

Progress: * UM-2 [QEMU upstream maintainership] - got rc4 out of the door; 9.0 release next week - working through the rev K.a Arm ARM to resync the list of architecture features we have implemented and the Linaro JIRA issues that track the ones we haven't. Sent a patchset that updates

[ACTIVITY] report week ending Apr 12

Progress: * UM-2 [QEMU upstream maintainership] - looking at some late-breaking patches for various more-or-less 9.0-worthy bugs - tagged rc3; looks like we'll need an rc4, though - back to looking at cleanups and refactorings of our reset handling: + add support for a new reset type

[ACTIVITY] report week ending 5 Apr

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more pullreq wrangling - more FEAT_NMI patchset review: I think I'm now finally done with this - looked at issue #2150 and produced a short standalone repro case from the logfile the user provided (which was from a bo

[ACTIVITY] report week ending 28 Mar

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more FEAT_NMI patchset review: done with the physical interrupt parts, haven't looked at the virtual interrupt parts yet - usual release related effort - investigated and fixed a bug where we were taking HSTR traps

[ACTIVITY] report week ending 22 Mar

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more softfreeze related work: tagged rc0 this week - spent some time looking through Huawei's FEAT_NMI patchset; this is in basically good shape but there are a number of minor bugs/missing bits of the feature for t

[ACTIVITY] report week ending 14 Mar

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - softfreeze week this week, so a lot of time shepherding patches and pullrequests upstream, looking to see if we have any bugs that we ought to fix for 9.0, etc - looked at our Coverity results and submitted patches

[ACTIVITY] report week ending 8 Mar

Progress: * UM-2 [QEMU upstream maintainership] - code review (softfreeze is next week!): + Add device STM32L4x5 RCC + Add support for I2C in BCM2835 boards + hw/scsi/lsi53c895a: add timer to scripts processing + target/arm: Do memory alignment check for device memory + linux-user

[ACTIVITY] report week ending 1 Mar

Progress: * UM-2 [QEMU upstream maintainership] - code review, notably another round of the raspberry pi 4b emulation series. Reviewed and took a subset of the patches, which is enough to get a working model without PCI or ethernet. We'll work on the landing other parts, but no need

[ACTIVITY] report week ending 23 Feb

Progress: * UM-2 [QEMU upstream maintainership] - code review - finished and sent out for review the patchset that provides a 3-phase-reset version of qemu_register_reset() - The MSYS2 project are dropping their support for 32-bit Windows, which affects QEMU because we use them for o

[ACTIVITY] report week ending 15 Feb

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - various bits of cleanup and maintainer stuff - working on a 3-phase-reset-aware equivalent to qemu_register_reset(): have some basically working code, need to tidy it up and look for where the changes it makes to re

[ACTIVITY] report week ending 9 Feb

Progress: * UM-2 [QEMU upstream maintainership] - code review and pullrequest wrangling + RTH's MTE fixes patchset + Some cleanup patches from Philippe + various other smaller things - sent out some minor patches: + avoid some warnings being printed during 'make check' + fix an

[ACTIVITY] report week ending Feb 2

Progress: * UM-2 [QEMU upstream maintainership] - more code review and pullreq wrangling * QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image] - Wrote code to create the CPUs and the GIC and the UARTs. (Decided in the end not to try to create an a15mpcore-style wrapper device

[ACTIVITY] report week ending 26 Jan

Progress: * UM-2 [QEMU upstream maintainership] - Respin of a series I wrote back in Autumn to properly wire up the NS EL2 timer IRQ on the virt board. The delay was because the change tickles a bug in EDK2 that makes it assert on bootup; but now we have updated EDK2 binaries in QEMU

[ACTIVITY] report week ending Jan 19

Progress: * UM-2 [QEMU upstream maintainership] - patch review: + v4 of the raspi-4 SoC/board model series (this is a big one) + bug in calculation of limit address in designware pci controller model + imx7 serial device: implementation of FIFO and ageing timer + patchset to reduce s

[ACTIVITY] report week ending 12 Jan

Progress: * UM-2 [QEMU upstream maintainership] - further diagnosed the cause of the reported regression in virtio-pci running Linux on 32-bit arm emulation: the kernel the user was using was a non-LPAE one. So the fix is "use an LPAE kernel, or else manually set highmem=off".

[ACTIVITY] report week ending 5 Jan

Progress (short week, 2 days): * UM-2 [QEMU upstream maintainership] - post holiday email/slack/etc catchup - started merging pullrequests (I'm doing release management for the 9.0 cycle) - investigated a reported regression in virtio-pci running Linux on 32-bit arm emulation. T

[ACTIVITY] report week ending 15 Dec

Progress: * UM-2 [QEMU upstream maintainership] - Working through my to-review queue and building up a target-arm queue of patches ready to go when 8.2 releases and we reopen development for 9.0 * QEMU-623 [Nested Virtualization Emulation] - The inner-kernel crash I was looking at

[ACTIVITY] report week ending 8 Dec

Progress: * QEMU-623 [Nested Virtualization Emulation] - Progress on debugging: fixed last week's bugs, and can now get the outer kernel to boot a middle kernel which boots an inner kernel. Unfortunately the inner kernel boot hangs during init of the PF_NETLINK subsystem, whe

[ACTIVITY] report week ending 1 Dec

Progress: * UM-2 [QEMU upstream maintainership] - Sent a pullrequest for this week's rc - Sent a patch which disables SME if SVE is disabled, since QEMU currently asserts if you try to use that combination. * QEMU-623 [Nested Virtualization Emulation] - Mostly working through debugging

[ACTIVITY] report week ending 24 Nov

Progress: * UM-2 [QEMU upstream maintainership] - Usual amount of code review and upstream pull request wrangling * QEMU-623 [Nested Virtualization Emulation] - Since the kernel side of KVM has decided that FEAT_NV alone is not worth supporting, I'm moving on to implementing FEAT_NV2

[ACTIVITY] report week ending 16 Nov

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - put together pull request for a handful of bugfixes for rc0 - fixed the FEAT_MOPS reverse-copy bug and sent a patch for it * QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization] - trying to get a setup with kvmtool and a ke

[ACTIVITY] report week ending 10 Nov

Progress: * UM-2 [QEMU upstream maintainership] - Noticed that if the guest uses the HVC insn at EL3 we incorrectly take the exception to EL2, not EL3; sent a patch to fix this - looking into an issue with FEAT_MOPS copies going backwards across page boundaries * QEMU-292 [ARMv8.3 FEA

[ACTIVITY] report week ending 3 Nov

Progress: * UM-2 [QEMU upstream maintainership] - investigated and fixed a few bugs in FEAT_MOPS; patches sent - reviewed patch fixing bug in virt ACPI table for debug UART; added the necessary update-the-reference-files patches for 'make check'. Debugged why it broke console output on

[weekly][linaro] report week ending 27 Oct

Progress: * UM-2 [QEMU upstream maintainership] - Took a prototype set of patches to add a second UART to the virt board which I'd written before going off on holiday; cleaned them up and got them into shape to send out for review. This is likely to be QEMU 9.0 material because we wa

[ACTIVITY] report week ending 20 Oct

Progress: * UM-2 [QEMU upstream maintainership] - post-holiday catchup on email and code review - respin and resend of a patch fixing a bug in rdma code - sent a target-arm pull request * QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization] - did an initial read-through of the relevant port

[ACTIVITY] report week ending 27 Sep

Progress (short week, three days): * UM-2 [QEMU upstream maintainership] - Sent a patch to fix a bug involving QEMU's PSCI emulation when QEMU is faking being EL3 firmware for a Linux guest - Sent patch to make our handling of the UNPREDICTABLE T32 LDM-of-single-register case match rea

[weekly][linaro] report week ending 22 Sep

Progress: * UM-2 [QEMU upstream maintainership] - Implemented Neoverse N2 CPU model (easy as it's very similar to the Cortex-A710 we just implemented; but because it supports 48 bit physical addresses we can use it in the sbsa-ref board, so it's worth having both) - Wrote code to w

[ACTIVITY] report week ending 15 Sep

Progress: * UM-2 [QEMU upstream maintainership] - sent patches that re-sync our defined set of usermode hwcap bits and ID register bitmasks with what the Linux kernel currently has - code review * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] - FEAT_HBC: wrote and sent patch for this v

[ACTIVITY] report week ending 8 Sep

Progress: * UM-2 [QEMU upstream maintainership] - sent patch fixing some regexes in our documentation - patch review and queueing up an arm pull request - Investigated the mps3-an536 Cortex-R52 FPGA image to see what work would be required to implement a QEMU model of it, wrote a dra

[ACTIVITY] report week ending 1 Sep

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - code review: + RTH's linux-user ESR signal frame patchset + iMX6/7 cleanup patchset + some other minor bits and pieces * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] - FEAT_MOPS: * SETG* instructions (memset +

[ACTIVITY] report week ending 24 Aug

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - code review: + Xilinx Versal CFI support series + v2 of RTH's Cortex-A710 series - a few more -Wvla patches - put together and sent the first arm pullreq for the 8.2 cycle * QEMU-530 [QEMU ARM v9.4 Baseline CPU for

[ACTIVITY] report week ending 18 Aug

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - sent out another couple of "avoid VLA" patches * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] - managed to write some first-pass code for the MTE checks for FEAT_MOPS memset operations. Got something together enough t

[ACTIVITY] report week ending 11 Aug

Progress: * UM-2 [QEMU upstream maintainership] - code review, notably: + RTH's setnegcond series + Jean-Philippe's fixes for various FEAT_RME bugs + Akihiko's series to make KVM '-machine none' not default to 40 bits of IPA space if the host doesn't supoprt that (like the Apple CP

[ACTIVITY] report week ending 4 Aug

Progress: * UM-2 [QEMU upstream maintainership] - some bits and pieces for release - code review, notably: + raspberry pi 4 support patchseries (a big 44-patch set) + Xilinx Versal CFI support patches * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] - more work on FEAT_MOPS: tested m

[ACTIVITY] report week ending 28 Jul

Progress: * UM-2 [QEMU upstream maintainership] - release related stuff: handling merge requests, etc (now passed back to RTH again) - sent some patches for a few easy coverity issues - worked through some code review (in particular some patches from new contributors) - created a g

[ACTIVITY] report week ending Jul 21

Progress: * UM-2 [QEMU upstream maintainership] - fixed some places in our RTC device models where we were putting a time_t or time_t offset into a 32-bit variable - took over from RTH briefly for pullreq merge handling - sent some patches fixing minor Coverity issues - investigated a

[ACTIVITY] report week ending 14 Jul

Progress: * UM-2 [QEMU upstream maintainership] - investigated and fixed a bug in page-table-walk handling of debug accesses that was introduced by the FEAT_RME changes - that prompted me to look at a cleanup of some of the ptw code so that we consistently look at "which space is this

[ACTIVITY] report week ending 6 Jul

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - softfreeze is next week, so spent some time putting together a pull request, fixing the bugs which the CI tests found in it, etc * QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG] - now that we implement all the necess

[ACTIVITY] report week ending 23 Jun (inc. KVM Forum trip report)

Progress: * UM-2 [QEMU upstream maintainership] - catch up on email after a week away - Put together some arm pull requests - sent out draft QEMU summit minutes for review - sent patch to avoid using the buggy __builtin_subcll in Apple Clang 14 - sent patch fixing build error with ne

[ACTIVITY] report week ending 9 Jun

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 icou

[ACTIVITY] report week ending 2 Jun

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

[ACTIVITY] report week ending 25 May

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 th

[ACTIVITY] report week ending 19 May

Progress: * UM-2 [QEMU upstream maintainership] - Reviewed another round of RTH's patchset overhauling atomics - Sent an arm pullreq * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] - Continued with the conversion of the A64 decoder to decodetree: have converted hints, barriers, system r

[ACTIVITY] report week ending May 12

Progress (another short week, May is full of bank holidays :-)): * UM-2 [QEMU upstream maintainership] - usual background level of code review etc - investigated a bug reported by Mozilla where people running x86 Firefox on QEMU on Arm hardware were seeing crashes; narrowed down the cause

[ACTIVITY] report week ending 5 May

Progress (combines two weeks): * UM-2 [QEMU upstream maintainership] - investigated various failures of avocado tests on s390x host. These are at least four different unrelated endianness bugs in different device, board or CPU models. Sent out a set of patches fixing at most of these

[ACTIVITY] report week ending 21 Apr

Progress: * UM-2 [QEMU upstream maintainership] - sent out v3 of the 'deprecate singlestep option' patchset - sorted out the draft QEMU Summit invite list and invitation text - spent some time trying to understand how the imx SoCs arrange their ethernet controllers and PHYs so I can revi

[ACTIVITY] report week ending 14 Apr

Progress: * UM-2 [QEMU upstream maintainership] * trying to get a release out of the door -- due among other things to the Easter holiday weekend, rc4 is a bit late and has rather more changes than I would prefer * more triaging of Coverity issues * sent a few trivial bug fix pa

[ACTIVITY] report week ending 6 Apr

Progress: * UM-2 [QEMU upstream maintainership] * rc3 this week * reworked my "deprecate the misleading -singlestep option" patchset to deal with review feedback, sent out v2 * KVM Forum programme committee work * investigated a regression where the mps3-an547 board asserts on star

[ACTIVITY] report week ending 31 Mar

Progress (short week, holiday and recovering from covid...): * UM-2 [QEMU upstream maintainership] * 8.0 release related work rumbles on * debugged and fixed a regression caused by my work on HSTR_EL2 traps * QEMU-530 [QEMU ARM v9.4 Baseline CPU for TCG] * implemented FEAT_PAN3 (and fixed

[ACTIVITY] report week ending 17 Mar

Progress: * UM-2 [QEMU upstream maintainership] - went through and made estimates for a pile of JIRA tasks relating to implementing features we're missing to get to ARMv9.4 - diagnosed why --enable-werror wasn't affecting warnings from the kerneldoc docs generator, and sent a patch

[ACTIVITY] report week ending Mar 10

Progress: * UM-2 [QEMU upstream maintainership] - Softfreeze was this Tuesday; lots of wrangling of pull requests - Code review; last arm pullreq before softfreeze - various admin type bits and pieces -- PMM ___ linaro-toolchain mailing list --

[ACTIVITY] report week ending 24 Feb

Progress: * UM-2 [QEMU upstream maintainership] - Code review: big FEAT_LSE2 support series, 8.3 pointer auth, gdbstub support for M-profile sysregs, another round of FEAT_RME, and more - discussions about how to handle the fact that QEMU has run out of gitlab CI minutes, and

[ACTIVITY] report week ending 10 Feb

Progress: * UM-2 [QEMU upstream maintainership] - Code review. In particular: reviewed RTH's FEAT_RME series - Wrote and sent an RFC patchset proposing renaming of the badly misnamed '-singlestep' command line option (it actually does "put only one guest instruction in each JIT bas

[ACTIVITY] report week ending 3 Feb

Progress: * UM-2 [QEMU upstream maintainership] - usual upstream maintenance tasks - the CI/tests have got rather flaky of late: trying to find out why... * QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG] - FEAT_FGT: is now upstream -- PMM

[ACTIVITY] report week ending 27 Jan

Progress: * UM-2 [QEMU upstream maintainership] - usual upstream maintenance tasks * QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG] - FEAT_FGT: finished coding, did some testing, sent patches for review -- PMM ___ linaro-toolchain mailing list --

[ACTIVITY] report week ending 20 Jan

Progress: * UM-2 [QEMU upstream maintainership] - usual upstream maintenance tasks * QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG] - FEAT_FGT getting closer towards being done: I just have to mark up the ARMCPRegInfo structs for HDFGRTR traps, and write the code to handle traps on

[ACTIVITY] report week ending 13 Jan

Progress: * UM-2 [QEMU upstream maintainership] - another round of patch review and a pull request * QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG] - Made some useful progress with the FEAT_FGT implementation -- PMM ___ linaro-toolchain mailing li

[ACTIVITY] report week ending 6 Jan

Progress (short week, 2 days): * UM-2 [QEMU upstream maintainership] - Pretty much entirely trying to catch up with the code review backlog that had built up over the holidays. Got it down from 35 items to 7... Absences: * NB: I work a 4 day week, excluding Wednesdays * Apr 26 -- 2

[ACTIVITY] report week ending 20 Dec

Progress: * UM-2 [QEMU upstream maintainership] - I'm now back on merging duty for the 8.0 release cycle, so some time spent on pull request processing - Sent pull requests with accumulated arm and reset-refactoring patches from the freeze period - Trying to cut down my code rev

[ACTIVITY] report week ending 25 Nov

Progress: * UM-2 [QEMU upstream maintainership] - More conversions of devices to 3-phase reset in pursuit of the interim goal of getting rid of device_class_set_parent_reset() - Investigated a regression in a TF-A workload: this was due to recent pagetable walk refactoring breaking

[ACTIVITY] report week ending 18 Nov

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

[ACTIVITY] report week ending 10 Nov

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

[ACTIVITY] report week ending 4 Nov

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

[ACTIVITY] report week ending 28 Oct

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 AR

[ACTIVITY] report week ending 21 Oct

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

[ACTIVITY] report week ending 14 Oct

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 patche

[ACTIVITY] report week ending Oct 7

Progress: * UM-2 [QEMU upstream maintainership] - miscellaneous upstream patch review * QEMU-471 [QEMU ARM v9.0 Baseline CPU for TCG] - sent out patchset implementing FEAT_GTG - sent out patch implementing FEAT_E0PD - code review of RTH's FEAT_HAFDBS patchset -- PMM

[ACTIVITY] report week ending 30 Sep

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

[ACTIVITY] report week ending 25 Aug

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 _

[ACTIVITY] report week ending 19 Aug

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 compli

[ACTIVITY] report week ending 12 Aug

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

[ACTIVITY] report week ending 5 Aug

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

[ACTIVITY] report week ending 29 Jul

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 t

[ACTIVITY] report week ending 21 Jul

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

[ACTIVITY] report week ending 15 Jul

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

[weekly][linaro] report week ending 7 Jul

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 O

[ACTIVITY] report week ending 1 Jul

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

Re: qemu meeting status

On Tue, 28 Jun 2022 at 13:29, Richard Henderson wrote: > > Hi guys. I just realized that today's meeting will be right in the middle of > dinner > plans. I'll organize better next week. Anyway, here's my status: > > - Fourth SME patch set -- parts merged, and some bugs fixed. > - Base/arm-comp

[weekly][linaro] report week ending 24 Jun

Progress: * UM-2 [QEMU upstream maintainership] - First week back after holiday: lots of catchup - Good progress with the code review queue, including getting rid of a few things that had been lurking in it for too long, and another pass through the latest SME series - KVM Forum prog

[ACTIVITY] report week ending 10 Jun

Progress: * UM-2 [QEMU upstream maintainership] - This week was almost entirely code review and similar upstream tasks - managed to review all the preliminary parts of the SME patchset - reviewed several other refactoring series from rth - reviewed a big PS/2 keyboard emulation refactoring

[ACTIVITY] report week ending 31 May

Progress (covers two half-weeks): * UM-2 [QEMU upstream maintainership] - investigating a reported bug with semihosting syscalls over gdbstub - reviewed a massive series from RTH refactoring our SVE code in preparation for handling SME * QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG] - lo

Re: [TCWG CI] Regression caused by gcc: rs6000: Harden mma_init_builtins

On 5/31/22 8:09 AM, ci_not...@linaro.org wrote: > [TCWG CI] Regression caused by gcc: rs6000: Harden mma_init_builtins: > commit 6278065af07634278ba30029d92a82b089969baa > Author: Peter Bergner > > rs6000: Harden mma_init_builtins > > Results regressed to >

Re: [TCWG CI] Regression caused by gcc: rs6000: MMA test case ICEs using -O3 [PR99842]

On 5/30/22 8:58 AM, Maxim Kuvyrkov wrote: > Hi Peter, > > This is, obviously, a fluke. We'll investigate. > > Sorry for the noise, No problem! Peter ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To

[ACTIVITY] report week ending 20 May

Progress: * UM-2 [QEMU upstream maintainership] - Joint Linaro/Arm meeting on the Realm Management Extension (RME). Mostly this was "how the software stack is going to work"; some useful discussion on how this intersects with QEMU, both as a potential emulation platform for software

[ACTIVITY] report week ending 13 May

Progress: * UM-2 [QEMU upstream maintainership] + had a look at adding an option to allow semihosting from userspace (handy for some test case purposes); have a working prototype which I used to test the FEAT_IDST patch, but probably won't pursue further until some refactoring of the

[ACTIVITY] report week ending 6 May

Progress: * UM-2 [QEMU upstream maintainership] + tracked down the UEFI crash with KVM on AArch64 to a combination of (a) host system was heterogenous and user hadn't restricted QEMU to only running on one set of cores and (b) QEMU silently throws away the error it gets from KVM in t

[ACTIVITY] report week ending 28 Apr

Progress: * UM-2 [QEMU upstream maintainership] + investigating a bug report about the guest UEFI crashing on startup when using KVM on AArch64 with an SMP guest (sadly I haven't been able to repro it myself thus far) * QEMU-422 [QEMU Arm Neoverse V1 vCPU for TCG] + audited code to ch

[ACTIVITY] report week ending 22 Apr

Progress (two half-weeks): * UM-2 [QEMU upstream maintainership] + Got the 7.0 release out of the door and handed over pullrequest processing to RTH for the 7.1 cycle \o/ + Code review backlog now pretty nearly empty (worked through several large patchsets from RTH as well as some smal

  1   2   3   4   5   6   7   >