civilinfrastructureplatform:tsc-meetings:tsc_mm_jan092018
Differences
This shows you the differences between two versions of the page.
| — |
civilinfrastructureplatform:tsc-meetings:tsc_mm_jan092018 [2018/02/19 12:36] (current) yoshi created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== CIP Technical Steering Committee Meeting ====== | ||
| + | |||
| + | Date: 9 January, 2018 | ||
| + | |||
| + | ===== Roll Call ===== | ||
| + | |||
| + | TSC members | ||
| + | |||
| + | * Noriaki Fukuyasu (The Linux Foundation) | ||
| + | * Annie Fisher (The Linux Foundation) | ||
| + | * Agustin Benito Bethencourt (Codethink) | ||
| + | * Hidehiro Kawai (Hitachi) | ||
| + | * Mine (Hitachi) | ||
| + | * SZ Lin (MOXA) | ||
| + | * Masato Minda (Plat’Home) | ||
| + | * Takehisa Katayama (Renesas) | ||
| + | * Chris Paterson (Renesas) | ||
| + | * Jan Kiszka (Siemens) | ||
| + | * Wolfgang (Siemens) | ||
| + | * Daniel Sangorrin (Toshiba) | ||
| + | * Yoshi Kobayashi (Toshiba) | ||
| + | |||
| + | ===== Discussions ===== | ||
| + | |||
| + | ==== Kernel maintenance ==== | ||
| + | |||
| + | * No major update this week. Ben H. has been busy upstream. | ||
| + | |||
| + | === Timeline meltdown and spectre updates for CIP kernel === | ||
| + | |||
| + | * At this moment the impact of Spectre and Meltdown in modern architectures is incomplete as [[https://www.kb.cert.org/vuls/byvendor?searchview&Query=FIELD+Reference=584653&SearchOrder=4|this table]] shows. | ||
| + | * The initial fixes are stating to land upstream and being backported, as GKH stated in his [[http://www.kroah.com/log/blog/2018/01/06/meltdown-status/|post]]. | ||
| + | * It is early yet to fully understand the strategy towards fixes backports beyond what upstream is doing. Once the current fixes are settle upstream, a discussion should be opened about what to do with the fixes that has not landed to 4.4, especially those related with ARM. | ||
| + | * The original idea is to have a statement about Meltdown/Spectre issue from the CIP kernel maintainer next week. | ||
| + | * Given the communication needs, the goal is to have a software statement by the end of the current week. TODO: Agustin | ||
| + | |||
| + | ==== CIP RT kernel ==== | ||
| + | |||
| + | * CIP RT kernel (Linux 4.4.105-cip15-rt10) was released on 2nd January by Daniel W. | ||
| + | * [[https://www.spinics.net/lists/linux-rt-users/msg18226.html|https://www.spinics.net/lists/linux-rt-users/msg18226.html]] | ||
| + | * Renesas would like to know more about the RT testing (and potentially contribute) and will contact Daniel for more information. | ||
| + | |||
| + | ==== CIP Testing and KernelCI ==== | ||
| + | |||
| + | * Direction about CIP testing (Bold items are potential options for testing.) | ||
| + | * **Maintain current B@D** | ||
| + | * Ben and Daniel Wagner are using B@D. | ||
| + | * Enhancing the feature for B@D | ||
| + | * Could be later | ||
| + | * **Collaboration with AGL to setting up test case repository** | ||
| + | * **Collaboration with KernelCI in CIP side (in LF IT infrastructure)** | ||
| + | * Budget is approved to setup KerneCI infrastructure | ||
| + | * LAVA master in LF | ||
| + | * CIP member can test on the LAVA master | ||
| + | |||
| + | ==== ELC-NA Portland ==== | ||
| + | |||
| + | * Any plans for a F2F TSC meeting? If so how long and when? | ||
| + | * Candidate plan for Next TSC F2F meeting | ||
| + | * 11th March, 2018 (Sunday), 9am to 4pm (Lunch around noon-1pm) | ||
| + | * Note: ELC session 12-15 | ||
| + | * | ||
| + | * Any plans for a technical workshop? | ||
| + | * Any proposal? | ||
| + | * Other meetings | ||
| + | * Edgex | ||
| + | |||
| + | ==== Other updates ==== | ||
| + | |||
| + | * SZ will introduce CIP in a local event in Taiwan. | ||
| + | * [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences|Link]] to presentations from the website. | ||
| + | |||
| + | |||
civilinfrastructureplatform/tsc-meetings/tsc_mm_jan092018.txt · Last modified: 2018/02/19 12:36 by yoshi
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
