14:30 – CentOS: Taking the Excitement out of your Development Process
Speaker: Jim Perrin, CentOS Project Developer
Abstract: Developers and end users have enough to worry about without the operating system getting in the way. CentOS has a proven history for the x86/x86_64 platforms, and now we’re working to bring that same level of dedication to AArch64. We’ll demo installation, development tooling, containers, and discuss how everyone can be a part of the future improvements.
There has been recent work upstream to enable the LKP tests to build and execute on ARM platforms. The QA team has been involved with the integration of these tests into Linaroäó»s Automated Validation Architecture, and this presentation will provide a brief overview of the LKP results that have been obtained. It will also demonstrate useful way to compare the data.
Abstract: Experiences productizing the gateway (from hobby to product) and the challenges for IoT deployment scenarios: Home security, Home automation, Home healthcare, and Enterprise IoT (smart manufacturing).
In this session, Tim Bird will discuss the mainline status of several ARM SoCs used in mobile products. The average phone uses kernel software that is 3 years old, 20 versions behind mainline, and has 1 to 3 million lines of code out-of-tree. Tim will describe the “Device Mainlining” project of the Linux Foundation CE Workgroup, which seeks to address this problem. Some of the activities of this project are:
* publishing tools for mainline analysis
* finding big areas where multiple vendors have code out of tree
* identifying institutional barriers to corporate developer mainlining, and addressing them through education, training, and collaboration
* working with upstream to address deficient sub-systems or needed maintainer assistance
It is hoped that discussion will ensue about ways to continue enhancing this work, to get more SoC code mainlined.
At this session we will get more knowledge about the TEE driver that Linaro has been working on for the last couple of months. Questions to be answered are for example: What are the API’s? How does the TEE driver work as a communication channel. What will a developer need to think of when adding support for another TEE solution?
This session will go through the problems caused by decisions made in the early days of UEFI on ARM, how they are still hurting us - in expanding our validation as well as by providing poor examples for porters to new platforms. But also about projects underway to resolve this legacy once and for all. We will also cover changes to Linaro’s platform infrastructure, as well as our increasing involvement with EDK2 maintainership.
John’s bio: John Simmons is the visionary who inspired Microsoft to play a leadership role in the creation of international media standards. In a 2008 internal memo John envisioned a RESTful, interoperable commercial media stack, predicting its impact on the Web. His efforts resulted in Microsoft publishing specs for DRM-interoperable encoding and adaptive streaming, which in turn culminated in the ISO MPEG standards for Common Encryption and Dynamic Adaptive Streaming over HTTP (DASH). He led the creation of an OAuth 2.0 TV Everywhere authorization standard, initiated the Google-Microsoft-Netflix contributions to W3C for HTML5 Encrypted Media Extensions (EME) and Media Source Extensions (MSE) and authored an open spec to enable embedded browsers to implement EME without the use of proprietary software. At present John is the Media Platform Architect for Microsoft’s Operating System Group.
While QEMU has continued to be optimised for KVM to make use of the growing number of cores on modern systems TCG emulation has been stuck running in a single thread. This year there is another push to get a workable solution merged upstream. We shall present a review of the challenges that need to be addressed: locking, TLB and cache maintenance and generic solution for the various atomic/exclusive operations. We will discuss previous work that has been done in this field before presenting a design that addresses these requirements. Finally we shall look at the current proposed patches and the design decisions they have taken.