The Per Entity Load Tracking (PELT) is a key stone in tasks placement of the scheduler but suffers of some weakness when it’s not just bugs. During the last LPC, it has been decided to fix all pending issues of PELT before starting to consider another load tracking mechanism for scheduler and/or EAS. This session will show the improvement reached since the last connect and the LPC as well as the next ones. We will also looks at the RT class which lacks a good load tracking.
By definition, ‘unplanned’ session for people to come and discuss anything around AOSP - including AOSP for members, AOSP for non-Android Linux devs, OPTEE/Security, AOSP TV, to name a few. An initial list of topics for discussion could include:
- An Intro: Uses of AOSP codebase at Linaro and members
- AOSP for Linux developers (an intro to the AOSP codebase for regular Linux guys?
- AOSP TV
- Perhaps Completely open graphics stack
LMG team, in collaboration with Toolchains team, has worked on multiple areas related to clang, gcc and native AOSP builds. Bero and Renato will take us through what has been done, and what we need to continue to do. This presentation will focus on LMG efforts around the following:
- Clang CI efforts
- Getting AOSP to build with gcc 6/7
- Building kernels with clang
- Native AOSP builds and development
Device Tree is well established in the Linux kernel. But since there could be other bootloader(s) and firmware components involved that needs to configure the hardware and thereby also needs to update the Device Tree blobs before passing it to Linux kernel. Therefore we are looking for a well established way for firmware to also make use and modify the Device Tree blobs before handing them over to Linux kernel. With this BoF session we would like to get started a gather ideas etc.
"Delivering a well working distribution is hard. There are a lot of different hardware platforms that need to be verified and the software stack is in a big flux during development phases. In rolling releases, this gets even worse, as nothing ever stands still.
The only sane answer to that problem are working Continuous Integration tests. The SUSE way to check whether any change breaks normal distribution behavior is OpenQA. Using OpenQA we can automatically run tests that hard working QA people did manually in the old days. That way we have fast enough turnaround times to find and reject breaking changes
This session shows how OpenQA works, what pitfalls we had to make ARM work with OpenQA and what we're doing to improve it for ARM specific use cases."
Kernelci.org has been hailed as “the most successful, public build and test system for Linux, in the world". To keep that reputation, there is a need to do more testing faster, and we believe LAVA v2 will help us get there. Come learn about the effort underway to transition the testing system from LAVA v1 to LAVA v2, and the benefits that it will bring.
In this session will we review the new architecture for distributed testing that LAVA v2 will enable. Also, providing status of what’s working currently, and what is still in progress. Come be a part of the solution and help make the Linux kernel the best it can be!
An important base for security is the beginning of the boot process. It is necessary to be able to verify signatures before upgrading images. This session will discuss the mcuboot project, the efforts to port this to Zephyr, and the functionality available. It will include a small demo of its functionality.
The TI SimpleLink CC32xx family of MCUs provides an SoC and supporting SDK which completely offloads the WiFi stack onto an integrated network coprocessor. The SimpleLink SDK currently has no explicit support for the Zephyr IoT OS, but is designed to be portable. A native IP stack for Zephyr is currently under development, which includes an experimental IP offload option. This session reviews the challenges of integrating a vendor TCP/IP offload engine into an existing OS IP stack in general, and in particular, evaluates options for integrating the TI SimpleLink WiFi stack into Zephyr.