The Future of Linux on Arm Shines in the 3.7 KernelPosted on Friday, December 14, 2012 in Blog By Linaro
Arm multi-platform support
Arm multi-platform support adds the ability to build a single Arm kernel image which is able to boot multiple platforms. While not the primary goal of the Linaro kernel consolidation program, a single zImage from Linaro was demonstrated at Demo Friday during the Linaro Connect Europe 2012 (LCE12) event in Copenhagen at the beginning of November by members of the Linaro Kernel Team, and highlights the progress which Linaro has made in regards to its kernel consolidation program. This consolidation effort is what makes the single kernel binary possible. “A single zImage is a key ingredient for Server and as such is important to the Linaro Engineering Group (LEG).” added David Rusling, Linaro CTO.
Mark Orvek, Director for the Kernel Working Group at Linaro also made reference to this single zImage kernel in a video interview at this same event. “The ability to boot a single kernel on multiple hardware platforms within one SoC family has been available for a few years; however, what is now being added is the ability to boot a single kernel image across some of the SoC families that used to be mutually exclusive,” added Arnd Bergmann, Upstream Kernel Engineer at Linaro.
Another fundamental ingredient which contributed to the Arm multi-platform inclusion comes from efforts catalyzed during the first Linaro Connect in August of 2011. Efforts which focused on enabling Device Tree (DT) support on Arm Platforms. Deepak Saxena, Tech Lead for the Linaro Kernel team summed up these efforts in a blog post after that event. Saxena notes in his post that, “Device Tree helps us move towards our goals of being able to boot a kernel on any Arm machine and having a cleaner code base; however, it is only part of the solution. The Arm kernel port has been under development for over a decade and in that time has accumulated a lot of cruft that does not make it possible to build a kernel that supports heterogeneous SOCs.” Now fast forward to the 3.7 Linux Kernel release and you can see how Linaro’s collaboration with member organizations and upstream engineers through the enablement of DT for Arm platforms helped accelerate multi-platform support for Arm.
Bergmann describes the three global efforts in the Arm kernel this way, “Device Tree helps to consolidate code for boards within one SoC family and allows you to boot on future ones without kernel changes. Multi-platform helps to consolidate across SoC families. Moving platform code out into drivers supports the other two and allows to consolidate code across CPU architectures.”
“The newest Arm CPU model, Arm v8, adds 64-bit memory addressing capabilities for first time for the Arm world. The new 64-bit CPUs can run 32 bits code, but the 64-bit instruction set is completely new, not just 64-bit extensions to the 32-bit instruction set, so the Linux support has been implemented as a completely new architecture,” as described on the Kernel Newbies wiki pages about the 3.7 release.
As early as May 2011, enthusiasm for the Armv8(64-bit) architecture was starting to build. Jonathan Corbet with LWN took a look at support for the 64-bit Arm systems. In this article, Corbet highlights the first patches, the naming protocol, and even points to an email thread from Bergmann, which references “much of the relevant thinking” surrounding the AArch 64 Linux Kernel Port. Of note as well, Bergmann has been the primary reviewer for all the architectures that have been merged into the Linux kernel for the past 5+ years and while Linaro didn’t specifically push support for Armv8 upstream it did; however, provide consulting to Arm who did most of the technical development for this added feature.
At Linaro, support for this newest architecture continued to grow and at LCE12 - Copenhagen the first Armv8(64-bit) Mini-Summit was held. Discussions included the current state of Armv8 (64-bit), along with a look at past and future releases. Planning for the next quarter’s work in Linaro including blueprints and various requirements for the continuous integration (CI) loop for 64-bit tools (gcc 4.7 etc.), CI loop for 64-bit kernel and the LAMP stack based on Open Embedded were started. Also highlighted were various ways to coordinate the kernel activities for both 32- and 64-bit architectures and platforms along with the 64-bit bring-up of Linux distributions. A core theme that flowed throughout all theses sessions was the importance enabling the wider development community to get involved with Armv8 (64-bit) development.
Andrea Gallo, Director of the Linaro Enterprise Group (LEG), commented that “Armv8 support in the 3.7 Kernel release represents a major milestone for our work at LEG. We will leverage on it for all our developments on the Arm Foundation model towards enabling the 64-bit enterprise server workloads. We are eager to demonstrate early UEFI and ACPI work on AArch64 and 3.7 kernel at next the Linaro Connect in Hong Kong”
Linaro also made early Armv8 images available to interested developers and provided links to the Armv8 architecture introduction with includes a primer on the Armv8 architecture, the AArch64 execution state and the A64 instruction set. Linaro also points out that while there is no hardware available yet, Arm and Linaro have developed support for AArch64/A64 against virtual platforms and have started sending the resulting patches to various open source projects.
Additional references to Arm support in the 3.7 Linux Kernel include virtualization features as support for Xen in Arm was also added.
Excitement continues to grow throughout the Linux and Arm development communities as articles about the inclusion of Arm support in the 3.7 Linux Kernel circulate.
“Industry efforts have also recently been driven by the Linaro Enterprise Group [LEG], which is pushing Arm development on Linux forward, “ wrote Sean Michael Kerner of ServerWatch in his Linux 3.7 with Arms to the Future post. In November Linaro announced the formation LEG, which Kerner references in his article.
Jon Gold of Network World referenced the inclusion of these new features as “groundbreaking” in his Linux 3.7 adds major new Arm processor support post.
When asked what the inclusion of the various Arm features in the 3.7 Linux kernel really means for the future of Linux on Arm Rusling added, “Arm’s future in the Linux will be less fragmented, but, perhaps, more importantly, instead of being an irritation to the kernel maintainers, the Arm community are engaged as full Linux kernel citizens, helping Linux as it evolves to support diverse hardware platforms that are the hallmark of the Arm architecture and as it takes more sophisticated approaches to power management.”
Linaro engineers continue to collaborate with its members, partners, and the wider development communities to build the future of Linux on Arm as the inclusion of the Arm support in the 3.7 Kernel continues to increase the realization that Arm as a platform is becoming a mainstream player in not only in areas of mobile phones, but also in the Enterprise realm and is poised to change the face of desktop computing as well.
Getting involved with The Linaro Kernel Team
The Kernel Consolidation Working Group targets the Linux kernel. Its goals are to consolidate source repositories, unify support across SoCs, develop new kernel infrastructure and features and more. Our acid test: shipping a single source tree that integrates support for multiple modern Arm SoCs.
Linaro Kernel Tree Explained - https://wiki.linaro.org/WorkingGroups/Kernel/
Mailing List: mailto:email@example.com (subscribe)
IRC Channel: #linaro on irc.linaro.org or irc.freenode.net
More information about the Linaro Kernel Team can be found at: https://wiki.linaro.org/WorkingGroups/Kernel
Linaro is a member-sponsored, not-for-profit engineering organization focused on consolidating and optimizing open source software for member hardware platforms based on the Arm architecture.
Membership is open to Arm licensees, Linux distributions and other companies who wish to influence the future of Linux on Arm
Find out more about how your organization can become a Linaro member at: /members