| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:30 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 252 seconds) | 06:45 | |
| *** uli <uli!~uli@55d42941.access.ecotel.net> has joined #cip | 08:12 | |
| *** toscalix <toscalix!~toscalix@227.red-81-37-26.dynamicip.rima-tde.net> has joined #cip | 08:24 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:50 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 11:58 | |
| *** jki <jki!~jki@195.145.170.147> has joined #cip | 12:01 | |
| jki | Hi all! | 12:01 |
|---|---|---|
| iwamatsu | hi! | 12:01 |
| pave1 | Hi! | 12:01 |
| masami | hi | 12:01 |
| uli | hello | 12:01 |
| patersonc[m] | Afternoon | 12:02 |
| jki | #startmeeting CIP IRC weekly meeting | 12:03 |
| collab-meetbot | Meeting started Thu Sep 1 12:03:01 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:03 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:03 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:03 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | #topic AI review | 12:03 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | 1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm | 12:03 |
| alicef | hi | 12:03 |
| alicef | no updates | 12:03 |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 12:03 | |
| jki | but the ball regarding this is correctly in your field ATM? | 12:04 |
| alicef | yes, we was discussing it with fbezdeka | 12:05 |
| jki | ok | 12:05 |
| jki | 2. Check cip devices on kernelci old pull request - patersonc | 12:06 |
| patersonc[m] | Still not done | 12:06 |
| jki | any other AIs from last weeks? | 12:06 |
| jki | 3 | 12:07 |
| jki | 2 | 12:07 |
| pave1 | No, IIRC. | 12:07 |
| jki | 1 | 12:07 |
| jki | #topic Kernel maintenance updates | 12:07 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:07 | |
| uli | finished reviewing 5.10.137 | 12:07 |
| pave1 | I'm travelling this week. Some reviews done on 5.10.138 and 5.10.140. 5.10.139 contains single patch. | 12:07 |
| masami | This week reported 11 new CVEs and 7 updated CVEs. | 12:08 |
| iwamatsu | I am reviewing 5.10.140 | 12:08 |
| pave1 | I'm not sure if I'll be able to make it to the meeting tommorow (sorry). | 12:08 |
| jki | which meeting? | 12:09 |
| pave1 | I may be mistaken. I thought there's one on Zoom. | 12:09 |
| pave1 | CIP TSC meeting. | 12:10 |
| jki | eTSC was yesterday ;) | 12:10 |
| pave1 | Aha. Sorry :-). | 12:10 |
| pave1 | That makes things simpler. | 12:10 |
| jki | there are some follow-ups from the meeting, more later | 12:12 |
| jki | maybe for reference and discussion here: I did some stats on releases since April | 12:13 |
| jki | 5.10: 10 | 12:13 |
| jki | 5.10-rt: 2 | 12:13 |
| jki | 4.19: 9 | 12:13 |
| jki | 4.19-rt: 2 | 12:13 |
| jki | 4.4: 2 | 12:13 |
| jki | 4.4-rt: 2 | 12:13 |
| jki | we were on track with 5.10 and 4.19 and with 4.4-rt IIRC | 12:14 |
| jki | 5.10-rt, 4.19-rt and 4.4 are a bit behind the targets | 12:14 |
| jki | OTOH, no one complained so far | 12:15 |
| pave1 | AFAICT last 5.10-rt was in July, so we should do one ASAP. | 12:16 |
| pave1 | 4.19-rt was also in July, so next should be sometime in September. | 12:16 |
| pave1 | 4.4-rt was in August, so next one should be in October. | 12:17 |
| jki | 4.19-rt is indeed fine as well - 0.5 per month | 12:18 |
| jki | 5.10-rt is one per month | 12:18 |
| jki | so is 4.4 | 12:18 |
| jki | https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#kernel_maintainership | 12:19 |
| pave1 | Agreed. We should do 5.10-cip-rt when next 5.10-rt is released. | 12:20 |
| jki | would be good | 12:20 |
| iwamatsu | But it depends on the RT release.... | 12:21 |
| jki | well, if they are releasing at lower rates than what we promise, we need to account for that | 12:22 |
| jki | which likely mean lowering our promises and communicating that | 12:22 |
| pave1 | Let me check. Trouble with -stable-rt is that 4.9-rt, 4.19-rt and 5.10-rt each have different maintainer with different release rates. | 12:23 |
| pave1 | 5.10 rt has one release a month for | 12:25 |
| jki | that would still fit | 12:25 |
| jki | worst case if we miss one: one month without a release, but next one with 2 then | 12:26 |
| pave1 | 2022 (or more). | 12:26 |
| pave1 | But did not have one in August, AFAICT. | 12:26 |
| pave1 | So we should get "soon" when he releases. | 12:27 |
| jki | good | 12:27 |
| jki | any other maintenance topics? | 12:27 |
| patersonc[m] | The other option is to fund the RT project and ask for more frequent releases | 12:28 |
| jki | well, we do that already | 12:28 |
| jki | but not so much for maintenance | 12:28 |
| patersonc[m] | Then maybe we should ask them what is possible | 12:28 |
| jki | I don't think that is directly paid out of the LF project | 12:28 |
| jki | we can still ask for clarification and can try to prioritize this once the mainline merge is "done" | 12:29 |
| jki | I think the next RT meeting is end of Sept | 12:29 |
| jki | move on? | 12:30 |
| jki | 3 | 12:30 |
| jki | 2 | 12:30 |
| jki | 1 | 12:31 |
| jki | #topic Kernel testing | 12:31 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:31 | |
| alicef | still no updates on CIP pr progress | 12:32 |
| jki | anything is? | 12:34 |
| alicef | KernelCI have some updates and still working on CIP pr but no updates | 12:34 |
| jki | ok, anything else? | 12:38 |
| jki | 3 | 12:39 |
| jki | 2 | 12:39 |
| jki | 1 | 12:39 |
| jki | #topic AOB | 12:39 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:39 | |
| jki | RISC-V and 5.10-cip | 12:39 |
| jki | in order to ramp up support for RISC-V and then add the RZ-Five, I suggested to first officially declare support for that arch in our latest kernel | 12:40 |
| jki | that would become a proposal to the TSC to vote on | 12:40 |
| pave1 | Ok. I guess we can do that for kernel. | 12:40 |
| jki | right, only for the kernel so far | 12:41 |
| iwamatsu | I think so | 12:41 |
| iwamatsu | QEMU too? | 12:41 |
| pave1 | I was not able to get working userspace so far, and it looks like userspace is a bit of "work in progress" at the moment. | 12:41 |
| pave1 | Yeah, I guess we should do QEMU if we claim RISC-V support. | 12:41 |
| jki | userspace depends on where you pick it up from, and when | 12:41 |
| jki | right qemu-riscv64 would become the first target | 12:42 |
| iwamatsu | Okay | 12:42 |
| jki | for 5.10-cip then | 12:42 |
| pave1 | Do we want to claim risc-v-realtime? | 12:42 |
| jki | good question... | 12:42 |
| jki | I doubt that this is already seriously looked it, is it? | 12:42 |
| pave1 | I have not checked really, but -rt only supports listed architectures. | 12:43 |
| jki | and is RISC-V listed at all? | 12:43 |
| jki | if not, that would be easy for us :) | 12:43 |
| pave1 | I'd have to check. Lets add it to my todo list. | 12:44 |
| jki | please check soon, then I can also send out the proposal sooner | 12:45 |
| jki | so, what do we do for userspace for now? | 12:45 |
| jki | buildroot? some frozen and known-to-be-good(TM) debian sid-version? | 12:45 |
| patersonc[m] | Can we just use the Renesas/Yocto userspace for now? | 12:45 |
| patersonc[m] | Does it need to be Debian? | 12:46 |
| jki | does it have all features we need to kernel testing? | 12:46 |
| jki | eventually, it has to be Debian, sure, but we can start differently | 12:46 |
| pave1 | So... I tried various debian versions and one Ubuntu version. | 12:46 |
| patersonc[m] | May need some additions for LTP etc. | 12:46 |
| pave1 | On each version I tried, ldconfig segfaults and gcc segfaults. | 12:46 |
| jki | against QEMU or RZ/Five? | 12:47 |
| pave1 | On RZ/Five. Other software worked quite well.. so this is quite suspect. | 12:47 |
| jki | let's focus on QEMU first, I would say | 12:47 |
| pave1 | That makes sense, I guess. | 12:47 |
| jki | meanwhile, chris & Co. can double-check your findings | 12:48 |
| patersonc[m] | Ah yes, can't use the Renesas BSP for qemu - sorry :P | 12:48 |
| iwamatsu | If we don't need a big application (GNOME etc), I think there's no problem with Debian/unstable. | 12:48 |
| jki | Debian unstable is only stable when you freeze it via snapshot.d.o | 12:48 |
| jki | but, yes, you can use that for even bigger applications | 12:49 |
| jki | we have ROS2 running on it | 12:49 |
| jki | with hacks... | 12:49 |
| iwamatsu | No problem, Debian does not support ROS2 all packages yet... :-P | 12:50 |
| jki | anyway, we should take what is easiest to enable for kernel testing, works on QEMU and should be easy to run on RZ/Five as well | 12:50 |
| patersonc[m] | +1 | 12:52 |
| iwamatsu | BTW, I can't find RT-Linux Project and RISC-V support information. Probably not in the list. | 12:52 |
| iwamatsu | +1 | 12:52 |
| jki | ok, then I will draft a proposal over adding RISC-V as architecture to 5.10-cip and adding qemu-riscv64 as new reference target | 12:53 |
| jki | mentioning that -rt is not in scope as upstream does not support it yet | 12:53 |
| patersonc[m] | Thank you | 12:54 |
| jki | likely not even in 6.0-rt | 12:54 |
| pave1 | iwamatsu: Yes, I suspect so. AFAICT x86-64 is highest priority for -rt, arm64 being second one. | 12:54 |
| iwamatsu | OK | 12:54 |
| jki | perfect | 12:54 |
| jki | any other business? | 12:55 |
| patersonc[m] | Just apologies for not being here for the testing bit. I've nothing to add regardless | 12:56 |
| jki | np | 12:58 |
| jki | then let's close... | 12:58 |
| jki | 3 | 12:58 |
| jki | 2 | 12:58 |
| jki | 1 | 12:58 |
| jki | #endmeeting | 12:58 |
| collab-meetbot | Meeting ended Thu Sep 1 12:58:23 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:58 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-01-12.03.html | 12:58 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-01-12.03.txt | 12:58 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-01-12.03.log.html | 12:58 |
| *** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"" | 12:58 | |
| jki | thanks all! | 12:58 |
| alicefm | This week I was busy with OSS europe presentation | 12:58 |
| uli | thanks | 12:58 |
| iwamatsu | Thank you | 12:58 |
| masami | thank you | 12:58 |
| alicefm | https://osseu2022.sched.com/event/15z4y/merging-your-kernel-testing-code-into-kernelci-alice-ferrazzi-hirotaka-motai-miracle-linux-powered-by-cybertrust-japan-co-ltd if some is interested | 12:58 |
| pave1 | Thank you! | 12:58 |
| alicefm | Thank you | 12:58 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:58 | |
| fbezdeka | Thanks! | 12:59 |
| patersonc[m] | Thank you alicef | 12:59 |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 12:59 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 13:01 | |
| *** jki <jki!~jki@195.145.170.147> has quit IRC (Quit: Leaving) | 13:44 | |
| *** uli <uli!~uli@55d42941.access.ecotel.net> has left #cip (Leaving) | 13:47 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 13:53 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 15:13 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 17:04 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 17:29 | |
| *** toscalix <toscalix!~toscalix@227.red-81-37-26.dynamicip.rima-tde.net> has quit IRC (Quit: Konversation terminated!) | 18:39 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 252 seconds) | 21:52 | |
| *** helmut_ <helmut_!helmut@subdivi.de> has joined #cip | 21:58 | |
| *** helmut <helmut!helmut@subdivi.de> has quit IRC (Ping timeout: 244 seconds) | 21:59 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!