| *** masashi910 has joined #cip | 04:04 | |
| *** rajm has joined #cip | 06:38 | |
| *** KaidenPK_Yu_MOXA has joined #cip | 07:35 | |
| *** KaidenPK_Yu_MOXA has left #cip | 07:36 | |
| *** tpollard has joined #cip | 08:02 | |
| *** KaidenPK_Yu_MOXA has joined #cip | 08:49 | |
| *** wens has joined #cip | 08:57 | |
| *** fujita3 has joined #cip | 08:59 | |
| *** suzuki12 has joined #cip | 08:59 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger | Meeting started Thu Apr 9 09:00:00 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 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | please say hi if you're around | 09:00 |
| szlin | hi | 09:00 |
| punit | hi | 09:00 |
| KaidenPK_Yu_MOXA | hi | 09:00 |
| iwamatsu | hi | 09:00 |
| fujita3 | hi | 09:00 |
| suzuki12 | hi | 09:00 |
| wens | hi | 09:00 |
| patersonc | hi | 09:00 |
| masashi910 | #topic AI review | 09:00 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | 1. Combine root filesystem with kselftest binary - Iwamatsu-san | 09:00 |
| bwh | hi | 09:01 |
| iwamatsu | masashi910: I do not have update to this. | 09:01 |
| masashi910 | iwamatsu: Noted. Thanks. | 09:01 |
| masashi910 | 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team | 09:01 |
| masashi910 | The current discussion among the kernel team is described in the following document. | 09:01 |
| masashi910 | https://docs.google.com/document/d/1U4-txCx_uofNH7YXc9LgKILdY-BPgb-nYm3DFrs-9Ns/edit?usp=sharing | 09:01 |
| masashi910 | If you have any ideas, please write down to the document. | 09:02 |
| masashi910 | so, let me move on. | 09:02 |
| *** pave1 has joined #cip | 09:02 | |
| masashi910 | 3. Upload a guideline for reference hardware platform addition - masashi910 | 09:02 |
| pave1 | hi | 09:02 |
| masashi910 | Updates can be reported around June timeframe. | 09:02 |
| masashi910 | so, let me move on. | 09:02 |
| masashi910 | 4. Identify target boards and configs for RT kernel testing (4.4rt and 4.19rt) - masashi910 | 09:02 |
| masashi910 | Last week, it was decided to identify target boards and configs for RT kernel testing. | 09:02 |
| masashi910 | I sent out an inquiry mail to ask CIP members to respond by April 16 (Thu). | 09:02 |
| masashi910 | So far only Renesas (Chris-san) responded. I will follow up at the TSC call next week. | 09:03 |
| masashi910 | any other topics? | 09:03 |
| masashi910 | 3 | 09:03 |
| masashi910 | 2 | 09:03 |
| masashi910 | 1 | 09:03 |
| masashi910 | #topic Kernel maintenance updates | 09:03 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:03 | |
| wens | nothing special on my end this week | 09:04 |
| pave1 | I did reviews on 4.19.114. Sorry for -rt delays. | 09:04 |
| pave1 | I currently believe that adding patch similar to one we have in 4.19-rt to 4.4-rt is the best way forward, even if I can't test it properly. | 09:05 |
| bwh | I reviewed updates to kernel-sec and kernel-config | 09:05 |
| iwamatsu | masashi910: I reviewd 4.4.218 and I send to backport patches for 4.4.y to stable ML. | 09:05 |
| patersonc | Thanks bwh: | 09:05 |
| patersonc | * Thanks bwh | 09:05 |
| masashi910 | iwamatsu: thanks for adding (CIP) after your name when you sent to the stable ML! | 09:06 |
| masashi910 | wens, pave1, bwh, iwamatsu: Thanks for your reports! | 09:07 |
| masashi910 | any other topics? | 09:07 |
| masashi910 | 3 | 09:08 |
| masashi910 | 2 | 09:08 |
| masashi910 | 1 | 09:08 |
| masashi910 | #topic Kernel testing | 09:08 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:08 | |
| masashi910 | patersonc: the floor is yours | 09:08 |
| patersonc | Hello | 09:08 |
| patersonc | #info Added RT configs for RZ/G1 and RZ/G2 platforms to cip-kernel-config. | 09:08 |
| patersonc | #info New USB hubs arrived at Renesas yesterday. I plan to install them later today. Hopefully this will resolve the disconnection issues we currently have. | 09:08 |
| patersonc | #info lab-cip-denx is online now, although we're seeing an issue with corrupted u-boot commands on the beaglebone-black board. | 09:08 |
| patersonc | #info Started adding support for RT tests, starting with cyclictest, cyclicdeadline and hackbench. | 09:09 |
| patersonc | #info Main issue/annoyance at the moment is that the tests use a Python script to parse the results, which currently is missing from the RFS. | 09:09 |
| patersonc | #link https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/merge_requests/36 | 09:09 |
| patersonc | If there are any other RT tests that would be helpful please let me know. | 09:09 |
| pave1 | Thanks a lot for the work on the RT tests. | 09:09 |
| patersonc | np, sorry it took so long to get around to it ;) | 09:09 |
| pave1 | I believe cyclictest+hackbench should be pretty good. | 09:10 |
| patersonc | Just let me know if there is anything you want tweaked | 09:10 |
| patersonc | (see my comments on GitLab) | 09:10 |
| pave1 | If we can get numbers on de0-nano, I'll know more. | 09:10 |
| pave1 | Yes, I need to take a deeper look. | 09:10 |
| patersonc | https://lava.ciplatform.org/scheduler/job/14181 | 09:11 |
| masashi910 | patersonc: thanks for your works! | 09:11 |
| punit | patersonc: There seems to be a driver for cyclictest - rteval (https://git.kernel.org/pub/scm/utils/rteval/rteval.git/). It supposedly generates background load | 09:11 |
| patersonc | Btw I'm off on "holiday" next week | 09:11 |
| punit | I wonder if it'll help with what you're doing | 09:12 |
| szlin | patersonc: stay safe :D | 09:12 |
| patersonc | Thanks punit, I'll take a look | 09:12 |
| masashi910 | patersonc: so, please stay safe. do you have any other topics? | 09:13 |
| patersonc | pave1: cyclictest+hackbench on de0-nano-soc board: https://lava.ciplatform.org/scheduler/job/14279 | 09:14 |
| patersonc | masashi910: Nothing else from me | 09:14 |
| masashi910 | patersonc: thanks again! | 09:14 |
| masashi910 | are there any other queries? | 09:14 |
| masashi910 | 3 | 09:14 |
| masashi910 | 2 | 09:14 |
| masashi910 | 1 | 09:14 |
| masashi910 | #topic CIP Core | 09:15 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:15 | |
| masashi910 | punit: the floor is yours. | 09:15 |
| punit | Thanks, masashi910 | 09:15 |
| punit | One of the action items from discussions around Embedded world was target EOL dates for CIP Core components. | 09:16 |
| punit | I sent an email to cip-dev to kickstart the discussion! | 09:16 |
| punit | Once we have some agreement, I propose to update the wiki to capture this informatoin | 09:16 |
| punit | Please let me know if there is any feedback on the topic | 09:17 |
| punit | Another item - | 09:17 |
| punit | There is a preference to use python3 to the extent possible. | 09:17 |
| punit | As python2 is EOL it'll get hard to support it for long term | 09:18 |
| punit | The discussion was driven by Security WG query regarding backup software | 09:19 |
| punit | That's it from me. Thank you | 09:19 |
| yoshidak[m] | Thank you for concluding this, Punit! | 09:19 |
| pave1 | If I may chime in. | 09:19 |
| pave1 | It is hard to comment without knowing what exact requirements for backups are. | 09:20 |
| pave1 | duplicity is complex piece of software IIRC, and it seems somehow interesting to be critical part of core system. | 09:20 |
| pave1 | python2 to python3 port of large code base will be "interesting" and may need quite a bit of testing. | 09:20 |
| punit | I agree - yoshidak[m] had sent an excel sheet with requirements sometime back based on our request | 09:20 |
| pave1 | (Or you may be lucky). | 09:21 |
| punit | But it maybe worth extracting it from the excel to an easier to discuss format | 09:21 |
| punit | For the second part, I hope yoshidak[m] can clarify | 09:22 |
| punit | btw, upstream has migrated to python3 (also in bullseye) | 09:22 |
| punit | So hopefully, the backport is easier. From what I could find, most of the dependencies (except librsync2) are already in buster | 09:23 |
| punit | But agreed, somebody needs to take a deeper look at what porting actually involves | 09:23 |
| punit | And how to verify the port | 09:24 |
| pave1 | ...and if it is right for us to do the porting, as opposed to declaring "sorry but CIP can not serve that usecase". | 09:24 |
| pave1 | ...because CIP normally tries to package well-maintained software and maintain it for years... | 09:25 |
| pave1 | ...while this is doing cutting edge development. | 09:25 |
| pave1 | I mean... it will be useful to have duplicity working with python3 as python2 will disappear one day, | 09:25 |
| pave1 | but I'm not sure if it should be us doing so. | 09:26 |
| punit | Good point - it depends on how strong the requirement for duplicity (backup software) is in CIP | 09:26 |
| punit | At the least, I would like to see it in buster-backports | 09:27 |
| masashi910 | pave1, punit: thanks for the discussion. this is very important topic. | 09:27 |
| masashi910 | and I think this kind of discussion is also initiated in the ML. | 09:28 |
| masashi910 | we need to continue to discuss. | 09:28 |
| yoshidak[m] | I'll clarify the requirement about sytem-backup, and consider the necessity of duplicity as well. | 09:28 |
| masashi910 | yoshidak[m]: thanks for your comment. | 09:29 |
| masashi910 | if further discussion is needed, shall we do that after the irc or in the ML? | 09:29 |
| punit | My suggestion would be to continue on mailing list to allow people time to research before replying | 09:30 |
| masashi910 | punit: +1 | 09:31 |
| masashi910 | punit: thanks for your report! | 09:31 |
| masashi910 | shall we move on? | 09:31 |
| masashi910 | 3 | 09:31 |
| masashi910 | 2 | 09:31 |
| masashi910 | 1 | 09:32 |
| masashi910 | #topic Software update | 09:32 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:32 | |
| masashi910 | Suzuki-san, the floor is yours | 09:32 |
| suzuki12 | Hello. | 09:32 |
| suzuki12 | I'm afraid I don't have major updates since last meeting. | 09:32 |
| suzuki12 | That's it from me. | 09:32 |
| masashi910 | suzuki12: noted. thanks for your report. | 09:32 |
| masashi910 | are there any queries? | 09:32 |
| masashi910 | 3 | 09:33 |
| masashi910 | 2 | 09:33 |
| masashi910 | 1 | 09:33 |
| masashi910 | #topic CIP Security | 09:33 |
| *** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)" | 09:33 | |
| masashi910 | Yoshida-san, the floor is yours | 09:33 |
| yoshidak[m] | We are waiting to get approved the budget to start the gap assessment with the certification body. | 09:33 |
| yoshidak[m] | Next governing board meeting will be held at 27 or 28 April, so we are confirming to Exida about the valid period of the estimate. | 09:33 |
| yoshidak[m] | In parallel, we started to prepare the documentation for certification. | 09:33 |
| yoshidak[m] | Documents created for certification will be the main outcomes from the Security WG for users. | 09:34 |
| yoshidak[m] | However, we have just begun to consider what is needed. | 09:34 |
| yoshidak[m] | Hope to start discussion w/ Exida soon. | 09:34 |
| yoshidak[m] | That's all from me in this week. | 09:34 |
| masashi910 | yoshidak[m]: thanks for your report. | 09:35 |
| masashi910 | are there any queries? | 09:35 |
| masashi910 | 3 | 09:35 |
| masashi910 | 2 | 09:35 |
| masashi910 | 1 | 09:35 |
| masashi910 | #topic AOB | 09:35 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:35 | |
| masashi910 | Are there any business matters to discuss? | 09:35 |
| masashi910 | 3 | 09:35 |
| masashi910 | 2 | 09:35 |
| masashi910 | 1 | 09:36 |
| masashi910 | #endmeeting | 09:36 |
| brlogger | Meeting ended Thu Apr 9 09:36:04 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:36 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2020/04/cip.2020-04-09-09.00.html | 09:36 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/04/cip.2020-04-09-09.00.txt | 09:36 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2020/04/cip.2020-04-09-09.00.log.html | 09:36 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:36 | |
| masashi910 | Thank you! Stay safe! | 09:36 |
| pave1 | Thank you! | 09:36 |
| szlin | thank you | 09:36 |
| iwamatsu | thank you! | 09:36 |
| suzuki12 | Thank you! | 09:36 |
| punit | Thank you! | 09:36 |
| KaidenPK_Yu_MOXA | Thank you! | 09:36 |
| fujita3 | Thank you! | 09:36 |
| wens | Thank you! | 09:36 |
| *** suzuki12 has quit IRC | 09:36 | |
| bwh | thanks | 09:36 |
| *** fujita3 has quit IRC | 09:38 | |
| pave1 | patersonc: Thanks for all the realtime work. | 09:39 |
| patersonc | no worries | 09:39 |
| patersonc | Hopefully it'll help your work | 09:39 |
| pave1 | patersonc: It seems good enough for a start. | 09:39 |
| pave1 | patersonc: Can it be integrated in such a way that "maximum latency" over 100usec fails the test, else it passes? | 09:40 |
| patersonc | Good | 09:40 |
| patersonc | Yes, but the current setup relies on python to process this | 09:40 |
| pave1 | Will I need to modify .yml files in the -rt trees? | 09:40 |
| patersonc | No need for .gitlab-ci.yaml updates. I can handle that in the linux-cip-pipelines repo, once the current MR is merged. | 09:41 |
| pave1 | And problem is "there's no python in the images" or "we need python2 and only have python3"? | 09:41 |
| pave1 | I'll need to take a look at cyclicdeadline test. | 09:43 |
| patersonc | I don't think there is any python in the current images, although I'm not sure I've looked/tried the isar images yet | 09:43 |
| patersonc | pave1: There are also other RT tests, take a look through https://github.com/Linaro/test-definitions/tree/master/automated/linux and take your pick | 09:44 |
| pave1 | Thanks, will take a look. | 09:45 |
| pave1 | BTW good luck with the virus thing. It looks like it will be very interesting in next week or so for you. | 09:45 |
| pave1 | We managed to "pause" it for now, which is either very good or very bad thing, depending on what happens next, but it is currently boring here. | 09:46 |
| patersonc | Yea. Just need to stay in doors and hope we don't get anything when we go shopping | 09:46 |
| pave1 | Yes, shopping is a bit scary :-(. Outdoors away from other people should not actually be bad. (At least here, we still have < 0.1% infected). | 09:49 |
| pave1 | I don't understand what cyclicdeadline is.. all I see is binaries. | 09:50 |
| pave1 | Usual non-rt tests still make sense to run in -rt configs, but I guess we are doing that. | 09:51 |
| pave1 | cyclictest+hackbench should be okay for now. | 09:51 |
| pave1 | Eventually, I'd expect -cip-rt users to ask for particular tests... | 09:52 |
| patersonc | cyclicdealine description, see: https://github.com/Linaro/test-definitions/blob/master/automated/linux/cyclicdeadline/cyclicdeadline.yaml#L4 | 09:52 |
| pave1 | Aha, thanks! | 09:52 |
| pave1 | Okay, so that one does make sense to run, and I assume it will also need hackbench in the background to be useful. | 09:53 |
| patersonc | Probably | 09:54 |
| patersonc | I'm going afk for a while. Can you make any requests on the MR? | 09:54 |
| pave1 | Or actually.. this is basically scheduler test. So it we need cyclictest _or_ cyclicdeadline, but unless debugging scheduler | 09:54 |
| pave1 | ... this is not critical. And I don't plan to debug scheduler :-). | 09:54 |
| pave1 | Ok, will do; | 09:54 |
| pave1 | but the best way would be to just merge it :-). | 09:54 |
| pave1 | See you! | 09:55 |
| *** KaidenPK_Yu_MOXA has quit IRC | 10:15 | |
| *** pave1 has quit IRC | 10:35 | |
| *** rajm has quit IRC | 13:24 | |
| *** rajm has joined #cip | 14:28 | |
| *** tpollard has quit IRC | 16:58 | |
| *** pave1 has joined #cip | 19:07 | |
| *** pave1 has quit IRC | 19:36 | |
| *** rajm has quit IRC | 22:20 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!