09:00:02 <masashi910> #startmeeting CIP IRC weekly meeting
09:00:02 <brlogger> Meeting started Thu Apr  2 09:00:02 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:02 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:02 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:10 <masashi910> #topic rollcall
09:00:20 <masashi910> please say hi if you're around
09:00:23 <wens> hi
09:00:26 <yoshidak[m]> hi
09:00:31 <suzuki67> hi
09:00:35 <fujita3> hi
09:00:38 <sangorrin> hi
09:00:44 <szlin> hi
09:00:50 <szlin> sangorrin: welcome back!!!
09:01:05 <masashi910> indeed.
09:01:11 <patersonc> hi
09:01:13 <pave1> hi
09:01:16 <masashi910> #topic AI review
09:01:23 <masashi910> 1. Combine root filesystem with kselftest binary - Iwamatsu-san
09:01:24 <sangorrin> thank you!
09:01:34 <masashi910> Quote from Iwamatsu-san "No update."
09:01:41 <punit> hi
09:01:45 <masashi910> 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
09:01:53 <masashi910> The current discussion among the kernel team is described in the following document.
09:02:01 <masashi910> https://docs.google.com/document/d/1U4-txCx_uofNH7YXc9LgKILdY-BPgb-nYm3DFrs-9Ns/edit?usp=sharing
09:02:02 <bwh> hi
09:02:10 <masashi910> If you have any comments, please add as "comment"s to the document.
09:02:16 <masashi910> 3. Upload a guideline for reference hardware platform addition - masashi910
09:02:23 <masashi910> Updates can be reported around June timeframe.
09:02:36 <masashi910> any other topics?
09:02:55 <masashi910> 3
09:02:58 <masashi910> 2
09:03:00 <masashi910> 1
09:03:03 <masashi910> #topic Kernel maintenance updates
09:03:11 <masashi910> Quote from Iwamatsu-san "No update. But I reviewed and checked other LTS kernel."
09:03:42 <wens> nothing from me this week
09:03:43 <pave1> I have started reviewing 4.19.114, and started working on v4.4-rt release.
09:04:11 <masashi910> wens: noted. thanks.
09:04:56 <masashi910> pave1: Thanks for your works.
09:05:03 <pave1> And I believe we should talk about realtime.
09:05:15 <pave1> Is it suitable time to do it now?
09:05:56 <masashi910> pave1: yes, please go ahead.
09:06:38 <pave1> So... we have a list of supported boards for 4.4 and 4.19.
09:06:56 <pave1> Would it make sense to separate support for 4.4-rt and 4.19-rt?
09:07:42 <pave1> List is here: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/ciprefer
09:07:43 <pave1> +encehardware
09:08:06 <masashi910> pave1: I believe so.
09:08:17 <pave1> Not every hardware is suitable for realtime.
09:08:38 <bwh> Agreed
09:08:58 <masashi910> pave1: so, should we ask board proposers for their preference?
09:09:16 <patersonc> FYI, I've asked some colleagues to add RT configs for the Renesas boards to cip-kernel-config
09:09:29 <patersonc> This means we can add them for testing the RT Kernels
09:09:48 <pave1> I believe that would be the way to go. "Do you believe your board is suitable for realtime operation, and should we support 4.x-rt on it?"
09:09:54 <patersonc> I agree to expanding the table on the wiki, makes sense to me
09:10:27 <patersonc> Presumably the RT Kernel should still run on non-RT boards though, with non-RT configs?
09:10:48 <patersonc> Or is the RT Kernel only ever expected to run in RT use cases?
09:10:53 <masashi910> pave1, patersonc: ok, then I will send an inquiry to mailing list.
09:10:59 <fujita3> pave1: which one do you think now not suitable for RT?
09:11:04 <punit> It's good for sanity testing
09:11:09 <bwh> It should do, since the RT stuff is supposed to go upstream eventually
09:11:10 <pave1> massashi910: Thank you.
09:11:23 <bwh> (it should work in non-RT configurations, that is)
09:11:29 <pave1> Well, it is configuration we recently discovered bugs in.
09:11:58 <pave1> OTOH... you don't patch your kernel with huge/intrusive patch just to disable it ;-).
09:12:44 <punit> Another approach would be to just use the RT kernel always and only enable RT for users who care
09:12:56 <bwh> Yes, it's not that important for *us* to test that now.
09:13:10 <punit> As bwh said, RT patches are intended to be mainlined eventually
09:13:45 <pave1> fujita3: I'm not sure which boards are unsuitable. My notes say thinkpad x60 is not suitable.
09:14:00 <pave1> fujita3: I'd expect x86 boards with SMM bios to be unsuitable.
09:14:27 <fujita3> pave1: Ah, okay.
09:14:30 <pave1> fujita3: But normally it is advertised the other way around, "this one is good for realtime".
09:14:37 <pave1> punit: No.
09:15:11 <masashi910> so as a first step, we will identify boards to be tested on 4.4 and/or 4.19 by asking the board proposers.
09:15:28 <fujita3> masashi910: +1
09:15:31 <pave1> bwh: So... yes, testing non-real-time config on realtime kernel is good excersise to catch bugs (and that's de0-nano issue), but I'm not sure if we should dedicate resources to that.
09:15:32 <masashi910> then, we will determine which config we should use for our testing.
09:15:57 <pave1> Makes sense.
09:16:35 <pave1> patersonc: Would it be possible to get RT configuration for at least one Renesas board tested for realtime?
09:16:55 <pave1> patersonc: cyclictest + find / in the background should be good first start.
09:17:15 <patersonc> pave1: Planning to add a PR to cip-kernel-config in the next week or two for this
09:17:57 <masashi910> thanks to all for your discussions.
09:18:04 <masashi910> any other topics?
09:18:19 <masashi910> 3
09:18:24 <masashi910> 2
09:18:27 <masashi910> 1
09:18:29 <masashi910> #topic Kernel testing
09:18:33 <patersonc> fujita3: I've just copied you in on the internal email
09:18:42 <masashi910> patersonc: the floor is yours
09:19:15 <patersonc> I'm in the process of setting up a 'staging' copy of our LAVA setup
09:19:19 <fujita3> masashi910: thanks
09:19:24 <patersonc> Got some hardware from the office yesterday to set up a little lab at home
09:19:27 <patersonc> The x86 reference platform is up again
09:19:39 <patersonc> Currently working with Denx to get their lab operational
09:19:54 <patersonc> I think that's about it
09:20:09 <masashi910> patersonc: thanks for your works.
09:20:17 <fujita3> (sorry patersonc, I copied wrong line)
09:20:33 <masashi910> any queries?
09:20:48 <masashi910> 3
09:20:53 <masashi910> 2
09:20:56 <masashi910> 1
09:20:58 <masashi910> #topic CIP Core
09:21:06 <masashi910> Punit-san, the floor is yours
09:21:15 <punit> Thanks, masashi910
09:21:29 <punit> This week there are no updates from CIP-core!
09:21:54 <masashi910> punit: noted. thanks for your report.
09:22:01 <masashi910> any queries?
09:22:11 <masashi910> 3
09:22:14 <masashi910> 2
09:22:17 <masashi910> 1
09:22:20 <masashi910> #topic Software update
09:22:21 <punit> I am looking to setup a CIP core members meeting to discuss maintenance issues
09:22:26 <masashi910> Suzuki-san, the floor is yours
09:22:33 <suzuki67> Hello
09:22:36 <yoshidak[m]> masashi910: see the above comment from Punit
09:22:37 <suzuki67> I don't have major progress since the last meeting.
09:23:00 <suzuki67> I'm still working on integrating deby + meta-swupdate. (https://gitlab.com/cip-project/cip-core/deby/-/issues/8)
09:23:08 <suzuki67> That's all from me.
09:23:25 <masashi910> punit: Sorry, I misunderstood your comment.
09:23:44 <masashi910> suzuki67: thanks for your report.
09:24:11 <punit> No worries! I am having latency issues so comments are taking a long time
09:24:35 <masashi910> punit: sorry. do you have any other reports?
09:25:28 <punit> I'll send a doodle to find a suitable slot
09:25:33 <punit> That's it. Thank you
09:25:46 <masashi910> punit: Thank you!
09:26:02 <masashi910> so, back to Suzuki-san's report.
09:26:09 <masashi910> are there any queries?
09:26:42 <masashi910> 3
09:26:51 <masashi910> 2
09:26:56 <masashi910> 1
09:27:01 <masashi910> #topic CIP Security
09:27:08 <masashi910> Yoshida-san, the floor is yours
09:27:42 <yoshidak[m]> Hi
09:27:48 <yoshidak[m]> I don't have any update this week, but I'd like to discuss about python version issues as the dependency of security package.
09:28:27 <yoshidak[m]> Then, I'll post it to CIP-Dev ML, so let's discuss about @CIP core team
09:28:40 <punit> +1
09:29:22 <masashi910> yoshidak[m]: thanks. do you have any other reports?
09:29:29 <yoshidak[m]> masashi910: That's all from me this week, thank you
09:29:52 <masashi910> yoshidak[m]: thank you!
09:29:57 <masashi910> any queries?
09:30:11 <masashi910> 3
09:30:18 <masashi910> 2
09:30:23 <masashi910> 1
09:30:26 <masashi910> #topic AOB
09:30:33 <masashi910> Are there any business matters to discuss?
09:30:48 <masashi910> 3
09:30:53 <masashi910> 2
09:30:58 <masashi910> 1
09:30:59 <masashi910> #endmeeting