LTSI Project update Long Term Support Ini0a0ve. Tsugikazu SHIBATA, NEC Hisao Munakata, Renesas 20, May 2014 LinuxCon so

Transcription

1 LTSI Project update Long Term Support Ini0a0ve Tsugikazu SHIBATA, NEC Hisao Munakata, Renesas 20, May 2014 LinuxCon so

2 Key ac3vi3es of LTSI Long Term Support Ini3a3ve p Provide a industry managed kernel and maintain Long term based on LTS p Provide a common place for embedded industry to share informamon: Mailing list, Workshop p Provide place to support upstream acmvity : Help industry developer

3 LTSI history Established 2011 in Prague LTSI = LTS + Industry demanded patch (Back ports from the newer version) We have gathered great number of patches from Intel, Toshiba, Renesas and others

4 LTSI 3.10 Released LTSI 3.10 had been released 24 th Feb 2014 LSTI 3.0 : updated base version to and becomes EOL LTSI 3.4 : updated base version to

5 Why LTSI considered You can consider 1) latest version, 2) current development version (lots of experimental features are included, 3) several longterm stable kernels

6 Kernel release cycle Release cycle of Linux kernel is mostly 70 days Version Release Dura3on Version Release Dura3on

7 Released kernel and its maintained status Ver. Status 3.0 EOL, Maintained as Long term 3ll EOL, maintained Mll Maintained as Long term For Debian 3.3 EOL, maintained Mll Maintained as Long term EOL, maintained Mll EOL, maintained Mll EOL, maintained Mll EOL, maintained Mll EOL, maintained Mll Ver. Status 3.10 Maintained as Long term LTSI, RedHat 3.11 EOL, maintained Mll Maintained as Long term For SUSE 3.13 EOL, maintained Mll EOL, maintained Mll 3.16 is out

8 Stable release includes MUST APPY fixes Stable release only back port important bug and security fixes There are thousand fixes happened Version # of Fixes From To Version # of FIxes From To

9 LTS and LTSI release cadence Maintainer choose one LTS version per year Maintain for 2 years from its original release Max 2 LTS maintained 3.0 moves to EOL when 3.10 becomes new LTS 2 years from release 3.0 LTS 3.4 LTS 3.10 LTS

10 LTSI 3.10 DEVELOPMENT RESULTS

11 LTSI3.10 history Event Date kernel 3.10 merge window open kernel 3.10 merge window close kernel 3.10 release Announce of 2013 LTS kernel version LTSI git tree open becomes LTS (=3.12 release) LTSI merge window open patch collec3on period 75 days LTSI rc1 (=merge window close) valida3on period 26 days LTSI release

12 Major contributors for LTSI Contributor Patch count Darren Hart (Intel) 1,197 Simon Horman (for Renesas) 1,122 Daniel Sangorrin (Toshiba) 123 Patrik Jakobsson (for Intel) 46 Mark Brown (linaro) 11 Greg Kroah- Hartman (Linux Founda3on) 11 Total 2,510

13 Major achievement of LTSI 3.10 LTTng Power efficient work queues Intel BayTrail support Intel Minnow board support Renesas R- Car H2/M2 series support Xilinx Zinq board support

14 Yocto and LTSI is connected Yocto is a tool to create own distribumon and LTSI is used as its kernel

15 Discipline of LTSI project management Community LTS + industry demanded extra patches Governed by LF/CEWG Focus on kernel code, not aiming to support BSP CPU architecture neutral Comply with upstream rules Industry friendly acceptance Help embedded industry to umlize Linux

16 LTSI KERNEL TEST PROJECT

17 Overview of general Test Environment Test Packages Automated Test execution Test Target Lib Kernel Cross Build tools Test Results Target HW Test infrastructure

18 Linux tests ac3vi3es Linaro Lava Yocto Gregs s kernel test LTSI test

19 Linux tests: LAVA LAVA (Linaro Automated ValidaMon Architecture)is automated test system including Web framework with extension of scheduling job Support ARM architecture Open Source and be able to create infrastructure for their own Linaro Lab has facility for its members Bug tracking system and mailing lists Test packages seems not delivered

20 Linux tests: Yocto test Yocto is tool to create distribumon and suppormng mulmple architecture(x86, ARM, PPC, MIPS) Yocto project itself is tesmng the distribumon Broad range of tesmng CoreOS feature kernel, file system, driver, Build system, tool chain, Performance and power consumpmon check DistribuMon support run Yocto on top of Ubuntu. Fedora, CentOS Compliance test LSB, LTP, POSIX Stress test

21 Linux tests: Greg s Test Add Make test means: Developers can test minimum test before submit patches That can push back simple unchecked problem Every one can do minimum test when modify kernel Everyone can confirm their modificamon

22 Linux tests: LTSI 1/2 IniMal purpose of LTSI test is to confirm its kernel works well Full automated, easy to manage and monitor its result using web interface Trial version can be used for LTSI member Next steps are: Gather tests from companies to share Deliver test system sooware and be able to run tests by their own site

23 Linux test: LTSI 2/2 Over view of LTSI automated test; Provide Web interface Cross build and run on target HW Both interacmve and batch run Result can be checked using Browser 28 benchmarks and 33 typical tests are integrated More tests need to be merged from companies Test packages could be shared with other project Test system will be able to deliver More discussion for LTSI test will be at Workshop: My 20 th

24 Conclusion Understanding LTS/LSTI mechanism could be important for you product/service plan By using LTS/LTSI, you can gain huge cost for Linux based products and services Current version is LTSI Stay tuned for next version Be prepared if you have your own patches to be merged Test acmvimes are also on going, join us to share your tests

25 THANK YOU 25

26 How you can par3cipate LTSI Follow on Twiqer Web: hqp://ltsi.linuxfoundamon.org Mailing list: hqps://lists.linuxfoundamon.org/mailman/lismnfo/ltsi- dev Git tree : hqp://git.linuxfoundamon.org/?p=ltsi- ernel.git;a=summary 26

27 White paper: Economic value of LTSI Maintenance cost of single LTS version is about 3M$ workgroup/value-of-ltsi 27