| *** rajm <rajm!~robert@82.0.180.44> has joined #cip | 01:44 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:39 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 09:46 | |
| *** uli <uli!~uli@175.176.15.146> has joined #cip | 11:12 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 12:08 | |
| *** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:2ed4:ea8a:a603:bdfb> has joined #cip | 12:09 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 12:55 | |
| *** jki <jki!~jki@147.161.145.35> has joined #cip | 12:57 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 12:58 | |
| jki | Hi all! | 13:01 |
|---|---|---|
| uli | hello | 13:01 |
| masami | hi | 13:01 |
| alicefm | Hi | 13:01 |
| *** iwamatsu` is now known as iwamatsu | 13:03 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot` | Meeting started Thu Feb 23 13:03:46 2023 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:03 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:03 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:03 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | #topic AI review | 13:03 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | 1. enable more stable trees for testing (patersonc) | 13:04 |
| jki | there were some updates via the ML | 13:04 |
| jki | looks like "WIP", started now | 13:04 |
| jki | 2. report 6.1 test plan to LKML (pavel) | 13:05 |
| jki | [skip, due to 1.] | 13:05 |
| jki | anything else? | 13:05 |
| iwamatsu | hi all | 13:05 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 13:06 | |
| jki | if not, moving on in... | 13:06 |
| pave1 | hi | 13:06 |
| jki | 3 | 13:06 |
| jki | 2 | 13:06 |
| jki | 1 | 13:06 |
| jki | #topic Kernel maintenance updates | 13:07 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
| pave1 | I did some reviews, mostly 5.10.168. | 13:07 |
| masami | This week reported 4 new CVEs and 0 updated CVEs. | 13:07 |
| uli | i did reviews/backports from 4.14 to 4.4 | 13:07 |
| iwamatsu | I reviewed 5.10.168. | 13:08 |
| jki | uli: backport efforts still reasonable? | 13:11 |
| uli | yeah. most stuff that doesn't apply cleanly is for non-existing code | 13:11 |
| jki | good | 13:11 |
| jki | anything else here? | 13:12 |
| jki | 3 | 13:13 |
| jki | 2 | 13:13 |
| jki | 1 | 13:13 |
| jki | #topic Kernel testing | 13:13 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:13 | |
| jki | oopps, missed one section | 13:13 |
| jki | but now testing first | 13:13 |
| alicefm | No updates. Still working at the previous pull request. | 13:13 |
| alicefm | Working on fixing kselftest tests with cip kernel config | 13:14 |
| jki | question: we are planning to suggest an alternative x86 target (to replace the existing SIMATIC IPC). how many boards would be needed for testing? 3 again? | 13:16 |
| alicefm | Depend from what the usage will be, probably. | 13:21 |
| jki | one will be reference target for IEC 61443 certification - that will come on top | 13:22 |
| alicefm | Sorry but I don’t have a clear answer for this, probably patersonc knows more as lava cip administrator | 13:22 |
| jki | ok, no problem | 13:23 |
| jki | anything else regarding testing (before going back to kernel releases)? | 13:23 |
| alicefm | Not from me | 13:23 |
| jki | 3 | 13:24 |
| jki | 2 | 13:24 |
| jki | 1 | 13:24 |
| jki | #topic Kernel release status | 13:24 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:24 | |
| jki | -4.4 | 13:24 |
| uli | on track. i'll send a request for review for a handful of manual backports tomorrow or on monday. | 13:25 |
| jki | good | 13:25 |
| jki | RT is later | 13:25 |
| jki | -4.19 | 13:25 |
| iwamatsu | LTS version is v4.19.273, and latest RT is v4.19.271-rt120. | 13:26 |
| iwamatsu | RT does not follow LTS yet. | 13:26 |
| jki | will that affect our schedule already? | 13:27 |
| iwamatsu | There is no effect on the schedule yet. | 13:29 |
| jki | good | 13:30 |
| jki | -5.10 | 13:30 |
| pave1 | 5.10 -- we need to either do 5.10.168-cip to match with -rt, or wait for next -rt. | 13:30 |
| jki | is RT due now? | 13:30 |
| jki | or will it be only, thus we have more time to wait? | 13:31 |
| pave1 | I'll need to check. But -rt releases are quite infrequent. | 13:32 |
| iwamatsu | Will this week's CIP release be 5.10.168? | 13:33 |
| jki | then an "exceptional" matching non-rt might be needed if it's not much effort | 13:33 |
| iwamatsu | Latest RT is v5.10.168-rt83. | 13:34 |
| pave1 | iwamatsu -- if we are doing 5.10-cip this week, | 13:35 |
| pave1 | i'd suggest doing it on .168. | 13:35 |
| iwamatsu | OK, release it in 168 to match RT. | 13:36 |
| pave1 | thank you! | 13:36 |
| jki | perfect | 13:36 |
| jki | then move on | 13:37 |
| jki | #topic AOB | 13:37 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:37 | |
| jki | I put "topics for eTSC" on the table | 13:37 |
| jki | chris mentioned: "Sources files in cip-kernel-config" | 13:38 |
| jki | didn't check yet what it is about | 13:39 |
| iwamatsu | cip-kernel-config also manages the source code to build. I think it's about that. | 13:41 |
| jki | those all.sources files? | 13:42 |
| jki | I guess I give Chris the stage to explain the topic during the TSC meeting ;) | 13:42 |
| iwamatsu | or cip_qemu.sources and others | 13:43 |
| iwamatsu | Or I can ask Chris about this before eTSC. | 13:43 |
| jki | yeah, we should sort ourselves before to clarify what we want to achive - or clarify | 13:44 |
| jki | a classic topic for eTSC would be "next CIP kernel" | 13:45 |
| jki | should we ask to officially start the development of 6.1-cip and announce that? | 13:45 |
| pave1 | jki> on that topic... I don't believe there's | 13:46 |
| pave1 | a commitment to maintain 6.1-lts-rt at the moment. | 13:46 |
| jki | ok, but that could be communicated as well | 13:47 |
| jki | is anyone in touch with folks from RT on that? | 13:48 |
| pave1 | Yeah. At the moment we should start preparing explaining the issues etc. | 13:48 |
| jki | there is also the RT Project quarterly meeting next Monday | 13:49 |
| pave1 | I'd say "we are maintaining 6.1-cip" is topic for next eTSC | 13:50 |
| jki | pavel: will you also participate? maybe a topic there as well | 13:50 |
| pave1 | Yes, I have it on my schedule. | 13:50 |
| pave1 | And yes, that's likely good topic there. | 13:50 |
| jki | then let's keep that in mind | 13:51 |
| pave1 | Is cip willing to offer resources if noone else steps up | 13:51 |
| pave1 | ? | 13:51 |
| jki | valid question - how much effort would you estimate? | 13:53 |
| pave1 | No idea I'm afraid. I guess we could ask on the rt meeting... | 13:54 |
| jki | Daniel had about a day per week back then, but that also included CIP-RT | 13:55 |
| jki | and he did both 4.4 and 4.19, right? | 13:55 |
| pave1 | That was before my time. | 13:56 |
| pave1 | -cip-rt is low effort when corresponding -rt is maintained. | 13:56 |
| jki | that is what I recall him saying as well | 13:57 |
| jki | and was the reason we commited on lts-rt in the same run | 13:57 |
| jki | ok... | 13:58 |
| pave1 | That makes sense. You'll be at the same meeting for Siemens, right? | 13:58 |
| jki | yep | 13:59 |
| pave1 | And this would be TSC decision I guess. | 13:59 |
| pave1 | But I believe our position is | 13:59 |
| jki | when it is also about budget, the board is needed afterwards | 13:59 |
| pave1 | 'it is not out of question'. | 14:00 |
| jki | anything else for eTSC? or for AOB? | 14:02 |
| pave1 | aob -- that cpu bug mentioned last week was amd | 14:03 |
| jki | yeah, read it | 14:03 |
| pave1 | -- and only affecting virtualisation, so we don't care much. | 14:03 |
| jki | and KVM | 14:03 |
| jki | exactly | 14:03 |
| jki | well, we do care about KVM | 14:03 |
| jki | but not on all version, and we are not alone | 14:04 |
| jki | will a fix end up in 4.19? or did it already? | 14:04 |
| pave1 | I don't believe I seen it. It usually takes longer. | 14:05 |
| jki | we should keep an eye on it, but I'm personally not aware of AMD KVM users with CIP kernel | 14:05 |
| jki | maybe check if we have KVM enabled for AMD on that kernel versions | 14:06 |
| jki | back than (at least 4.19), AMD was not yet that popular again | 14:06 |
| jki | ok | 14:06 |
| jki | anything else? | 14:06 |
| jki | 3 | 14:08 |
| jki | 2 | 14:08 |
| jki | 1 | 14:08 |
| jki | #endmeeting | 14:08 |
| collab-meetbot` | Meeting ended Thu Feb 23 14:08:27 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:08 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-23-13.03.html | 14:08 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-23-13.03.txt | 14:08 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-23-13.03.log.html | 14:08 |
| *** 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 13: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/" | 14:08 | |
| jki | thank you all, have a nice day! | 14:08 |
| uli | thanks | 14:08 |
| iwamatsu | Thank you | 14:08 |
| masami | thank you | 14:08 |
| pave1 | thank you! | 14:08 |
| *** uli <uli!~uli@175.176.15.146> has left #cip (Leaving) | 14:12 | |
| alicefm | Thank you | 14:12 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 14:12 | |
| *** jki <jki!~jki@147.161.145.35> has quit IRC (Quit: Leaving) | 14:17 | |
| patersonc[m] | iwamatsu: I don't suppose you remember where the original defconfig came from for the Beagle Bone Black board do you? | 15:17 |
| patersonc[m] | https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/commit/e28e124c4b0bdbf9d9552a3ee77ba29b4247f86f | 15:17 |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 17:05 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 17:05 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 20:38 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 20:48 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 22:14 | |
| *** rajm <rajm!~robert@82.0.180.44> has quit IRC (Ping timeout: 252 seconds) | 22:53 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!