CIP Technical Steering Committee Meeting

Date: 17 September 2018

TSC members

• Attendees
  • Agustin Benito Bethencourt (Codethink) (Representative)
  • Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
  • Hidehiro Kawai (Hitachi) (Representative) (Voting)
  • Wolfgang Mauerer (Siemens) (Representative) (Voting)
  • Hiroshi Mine (Hitachi)
  • Masato Minda (Plat’Home) (Representative)
  • SZ Lin (MOXA) (Representative)
  • Daniel Sangorrin (Toshiba)
  • Jeff ErnstFriedman (The Linux Foundation)

• Kernel development for next CIP kernel
  • (Ongoing) MOXA: Send the board support package to upstream
    • SZ: https://lkml.org/lkml/2018/8/30/105
      • The TI employee suggests to use “phy-handle” property in dts [1]; however, this property doesn’t work properly in 4.4.y-stable. I’ve fixed this issue and backported patches to 4.4.y-stable [2][3][4][5].

[1] https://lkml.org/lkml/2018/8/30/1136

			[2] [[https://www.spinics.net/lists/stable/msg256121.html|https://www.spinics.net/lists/stable/msg256121.html]]

[3] https://www.spinics.net/lists/stable/msg256124.html

[4] https://www.spinics.net/lists/stable/msg256131.html

[5] https://www.spinics.net/lists/stable/msg256749.html

• CIP Core package list
  • AI(Daniel.S): Send to public mail list to get feedback from Ben. (DONE)
    • [cip-dev] [CIP Core] Criteria for prioritizing security fixes in Debian LTS
    • https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.htm
    • Already submitted to Reproducible builds
• AI(Wolfgang): Contact to Daniel W. to become next CIP-RT maintainer
  • OK.

• <SZ> There is a discussion thread in Debian to discuss the “armel/armhf arch qualification for buster (Debian 10)”
  • https://lists.debian.org/debian-arm/2018/08/threads.html#00009

• Ben Hutchings report to cip-dev in progress.

• Will be update with a feedback from GB meeting.
  • GB approved two proposals for kernel maintainer and mentor
• Discussed at DebConf to decide the structure of CIP kernel team
• CIP kernel team will focus both 4.4 and next CIP (4.20 or 5.0 → 4.19)
  • <SZ> When is the freeze date for backporting new features in kernel 4.4
  • Originally we say approx 5 years.
    • We have to make a commitment to how many years CIP allow to backport features
• CIP kernel team will structured with
  • 1 mentor (Ben H.)
  • 2 maintainers for CIP kernel (Iwamatsu-san), 1 maintainer for CIP-RT (Daniel. W)
  • Other members from each company such as MOXA and Toshiba (Daniel S.)
  • AI(Kernel team members): Define milestone for next CIP kernel
    • Wait until which version Debian will choose.
      • When?
• Kernel configuration
  • Initial blacklist has already prepared by Ben
  • RT will be clarified by Daniel W.
  • Config vs. Board
    • To be discussed
• AI(SZ): Ask to have weekly kernel team meeting at 5pm(JST) (Need to check time for other timezones)
  • Done. Please join the meeting.

US-West US-East UK DE TW JP

01:00   04:00   09:00   10:00   16:00   17:00

• Intel L1 Terminal Fault
  • https://www.intel.com/content/www/us/en/architecture-and-technology/l1tf.html
  • Some fixes in 4.4.148
    • https://lkml.org/lkml/2018/8/16/229
• The release job of kernel 4.19 will hand over to Greg.
  • https://lkml.org/lkml/2018/9/16/167
• CIP contributions to 4.4.y-stable

• Originally it was thought that v4.20 (or v5.0) would be the next LTS. It now looks like v4.19 will be the next LTS Kernel - https://www.kernel.org/category/releases.html
• Does anyone have confirmation of the above from Greg?
• LTS v4.9 will now be supported for 6 years, perhaps v4.19 will be too.
• Does anyone know what Kernel Debian will be using? Or when they will make a decision?
  • Debian makes no announcement but as part of the release.
  • The conversation originally has not started.
  • Ben H. will propose 4.19, as stated in cip-dev

• When will CIP make a final decision on the Kernel version?
  • [Agustin] do we need to hurry? Is there a deadline? Is there any other option nowadays than 4.19?
• When does CIP plan to make the first cip-next release?
  • [Agustin] This is a question for the new Kernel maintainer. I do not think we should impose this decision but both, 4.4 and 4.19 Kernel Maintainers should propose a coherent proposal based on the effort required and capacity available.

• What Kernel configs will we support?
• What hardware/reference platforms will CIP support?
  • All/subset of the current v4.4-CIP reference platforms?
  • Renesas

(copied from above)

• 1 mentor (Ben H.)
• 2 maintainers for CIP kernel (Iwamatsu-san and TBD), 1 maintainer for CIP-RT (Daniel. W)
• Other members from each company such as MOXA and Toshiba (Daniel S.)

• New 4.4 kernel and -rt kernel released. Check cip-dev mailing list for announcements.
• Transition to new CIP kernel maintainer
  • Where will the CIP repo be stored? Gitlab.com?
    • Ben H. provided his view on the topic.
  • Maintainership permission and merge rules for the CIP kernel team
• ELCE 2018 kernel maintainers meeting?
  • (AI:Yoshi) CIP will have a kernel maintainers meeting at ELCE 2018
    • (9/3) Jeff is working to book a room for the meeting.
  • Iwamatsu-san will come to ELCE
    • Good timing to exchange PGP keys for kernel.org
• L1tf mitigation patches expected for the coming CIP kernel release.

• [ACTION]We need a maintainer of the kernelci service.
  • Currently there are no CIP administrators for either server. Ideally member companies should do this. One admin? Or multiple admins?
• Distributed testing
  • KernelCI: https://kernelci.ciplatform.org/
  • Lava Master: https://lava.ciplatform.org/
  • Both of the above installations have default content. We need to personalise the servers for CIP.
  • B@D needs to be updated to submit results to KernelCI server.
  • Remote LAVA Labs need to be integrated into the Lava master.
• For B@D updates please follow the journal.
• Some results will have ELCE depending on accouts on LAVA
• One day after ELCE, Automated testing Summit will be held
  • Key persons will attend
  • Daniel try to get feedback for CIP testing (e.g.How to test more effective way).

• Completed: Run Docker with CIP Core plus additional packages from Deby (meta-debian)
• Created a repository on GitLab under cip-playground
• How many instance when the memory error happend?

• Started to use new roll management (Thanks, Agustin)
  • TSC representatives from each company will be owners, as well as the tool admin, at group level.
  • We will have no group maintainers by default since we will not have repos at this level but we will enclose them in subgroups. So at this group level we will provide Developer or Reporter roles only to CIP participants.
  • We assign the maintainer role to those who should have it, because they are responsible of a specific area, at subgroup level.
  • Specific people can hold the maintainer role at repo (project) level based on the subgroup maintainer decision.
• FYI: Rules for new repository creation or new project launch
  • https://docs.google.com/document/d/1pSl2RwllU4dgqDf5UDuQ_bktbe-4pD4DLyGHDuOP2I8/edit?usp=sharing

• GB decided to fund to RB.