[ACTIVITY] week ending 12 May 2019
[VIRT-343 # ARMv8.5-RNG, Random Number Generator ] Posted v4, v5, v6. I think this is now ready for merge. [VIRT-327 # Richard's upstream QEMU work ] Posted v3 of the CPUNegativeOffset patch set. Posted v2, v3, and a pull request for the tlb_fill patch set. Debugged one more fix for Sparc testthreads. Reposted some long dormant linux-user fixes. Started reviving the do_syscall split patch set, since Laurent asked after it. r~ ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 6 - 10 May 2019
== This Week == * PR88837 (9/10) - Addressing review comments from Richard. Coming quite close should hopefully be committed next week. * Misc (1/10) - LLVM Buildbot babysitting - Meetings == Next Week == - Continue ongoing tasks ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] week ending May. 12 2019
QEMU Tooling ([VIRT-252])
=
QEMU plugin support ([VIRT-280])
- posted {PULL 0/5} demacro SoftMMU Message-Id:
<20190510200101.31096-1-alex.ben...@linaro.org>
[VIRT-280] https://projects.linaro.org/browse/VIRT-280
Upstream Work ([VIRT-109])
==
- more chasing of headers/byteswap/s390x/softfloat bug
- could not reproduce but now exact steps have been documented
Message-Id:
- posted {PATCH v1 00/23} current testing/next queue (docker/system &
io tests) Message-Id:
<20190509165912.10512-1-alex.ben...@linaro.org>
- posted {PATCH v3} tests/qemu-iotests: re-format output to for make
check-block Message-Id:
<20190510102918.2705-1-alex.ben...@linaro.org>
- posted {PATCH v4} tests/qemu-iotests: re-format output to for make
check-block Message-Id:
<20190510135247.31278-1-alex.ben...@linaro.org>
- posted {RFC PATCH} target/arm: semihosting docs, formatting and
return clean-ups Message-Id:
<20190510191051.5973-1-alex.ben...@linaro.org>
[VIRT-109] https://projects.linaro.org/browse/VIRT-109
Completed Reviews [1/1]
===
{Qemu-devel} {PATCH} tests: Force Python I/O encoding for check-qapi-schema
Message-Id: <20190506213817.14344-1-ehabk...@redhat.com>
Other
=
- Student accepted for [GSoC TCG project]
[GSoC TCG project]
https://wiki.qemu.org/Internships/ProjectIdeas/TCGCodeQuality
Absences
- A few afternoons between 20-24th May (CBG Beer Festival)
Current Review Queue
* {RFC v2 00/38} Plugin support
Message-Id: <20181209193749.12277-1-c...@braap.org>
* {PATCH v9 00/27} gdbstub: Refactor command packets handler
Message-Id: <20190502081554.5521-1-ari...@gmail.com>
* {PATCH 00/13} tests/vm: serial console autoinstall, misc fixes.
Message-Id: <20190508085645.11595-1-kra...@redhat.com>
* {Qemu-devel} {PATCH 00/26} tcg: Add CPUClass::tlb_fill
Message-Id: <20190403034358.21999-1-richard.hender...@linaro.org>
* {PATCH 0/5} tests/vm: Python 3, improve image caching, and misc
Message-Id: <20190329210804.22121-1-waine...@redhat.com>
* {Qemu-devel} {PATCH for-4.1 v2 00/36} tcg: Move the softmmu tlb to
CPUNegativeOffsetState
Message-Id: <20190328230404.12909-1-richard.hender...@linaro.org>
--
Alex Bennée
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] report week ending 10 May
(short week: 3 days) Brief writeup of a pair of talks I attended on Tuesday at the Cambridge University Computer Lab by some people from Amazon: Diana Popa talked about Amazon's new "Firecracker" VMM (virtual machine monitor -- the userspace component that uses the kernel's KVM APIs to create and control virtual machines; kvmtool and QEMU are both VMMs). Their use case is the AWS Lambda service, where VMs are generally fairly short-lived (on the order of hours), startup time matters a lot, and the VMs typically don't need very much CPU/RAM resource. Firecracker is written in Rust, and provides a very simple guest device model (virtio block and network devices), booting a kernel that knows it is virtualized. It boots the kernel directly, without running a BIOS. It has a memory footprint of less than 5MB and a boot time of 125ms. They are currently working on Arm support (they have it booting, but some bits still need work, eg the VM doesn't get the right time because there is no RTC device exposed to the guest). My feeling was that this shows an advantage of the KVM design: the kernel/userspace split makes it easy to replace the userspace VMM part with something customised for the task at hand if you don't need a full-fat all-bells-and-whistles general-purpose solution. Andreea Florescu talked next, about the "rust-vmm" libraries. This is a set of open-source Rust crates which are intended to abstract out some of the common building blocks for VMMs. Firecracker started as a fork of Google's crosvm project, but since the use-case requirements for the two projects are markedly different the code diverged fairly rapidly. rust-vmm is intended to allow the projects to share code for things like "nice Rust interfaces to the KVM ioctls" and "implementations of virtio devices". The project is still in quite an early stage of development -- they have a few crates that have made it to the "stable, published on crates.io" phase, but most are either in "being developed" or still just "planned/proposed/discussed". It's currently Apache-2.0 licensed, but they are planning to dual-license to Apache-2.0 | 3-BSD because Apache-2.0 isn't GPL-2.0 compatible, and they have had some interest in being able to experiment with using these crates with QEMU. (That sounds a bit outlandish but it's actually something I'm planning to look into myself -- the nice thing about Rust is that you can potentially incrementally add it to an existing C codebase without requiring a ground-up rewrite, so allowing security hardening of the more "risky" parts. This is very definitely all still just "exploratory prototyping" though.) Progress: * just miscellaneous upstream stuff thanks -- PMM ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 6-10 May 2019
* 1 day off (public holiday) == Progress == * FDPIC - rebased GCC FDPIC patches. Fixing conflict with fstack-protector. * GCC upstream validation: - Fixed ST internal validation broken since GCC bumped to version 10. Still some spurious failures probably caused by NFS. Testing workarounds. - reported a couple of regressions * GCC - ubsan on bare-metal toolchain: no news. * Infra - [stalled] working on adding binutils regression testing to round-robin jobs == Next == FDPIC: - GCC: fix problems with fstack-protector UBSAN/bare-metal: look at how to make it easier to use on CPUs that lack sync primivites (eg cortex-m0) ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[Activity] Week ending Friday 10th May 2019
[LLVM-158] buildbot maintenance - Increased timeouts on some libfuzzer tests, aarch64 full bots should fail less frequently under load. [LLVM-534] -n -N support in LLD (needed for Linux kernel allyesconfig CI with LLD on AArch64) Rewrote using a different approach after upstream comments [LLVM-122] BTI and PAC support in LLD Wrote an implementation, it compiles, but completely untested as of today. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 19
o 4 days week.
o LLVM
* Machine outliner:
- Fixed LR save issue, when saved into a register.
- Dealing with LR save/restore when outlined region is a
pop{...,PC} tail-call.
- Investigating potential issue with condition flags.
o Misc
* Various meetings and discussions.
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain
