Thursday, 2024-08-08

*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has quit IRC (Quit: hiromotai)01:37
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:17
*** frieder <frieder!~frieder@88.130.219.77> has joined #cip05:59
*** frieder <frieder!~frieder@88.130.219.77> has quit IRC (Ping timeout: 245 seconds)06:05
*** frieder <frieder!~frieder@88.130.219.77> has joined #cip06:18
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)10:01
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip10:33
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)10:46
*** rajm <rajm!~robert@81.170.5.59> has quit IRC (Remote host closed the connection)11:27
*** rajm <rajm!~robert@81.170.5.59> has joined #cip11:31
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip12:23
*** pave1 <pave1!~pavel@2a00:da80:fff0:2::2> has joined #cip12:58
*** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has joined #cip12:58
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has joined #cip12:59
*** FelixM <FelixM!~FelixM@147.161.169.0> has joined #cip12:59
arisuthi12:59
ulihello13:00
patersoncAfternoon13:00
masamihello13:00
iwamatsu__hello13:00
pave1hi!13:00
FelixMHi!13:01
*** jki <jki!~jki@46.128.82.72> has joined #cip13:01
jkihi all13:01
iwamatsu__hello13:01
masamihi13:01
jkilooks like a small round today...13:03
jki#startmeeting CIP IRC weekly meeting13:03
collab-meetbotMeeting started Thu Aug  8 13:03:28 2024 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
collab-meetbotThe 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 review13:03
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:03
jkiSo, no one did that in my absence - seems I have to now :)13:04
pave1I'm reviewing 6.1.103/104.13:04
jkiI didn't find other AIs in the last weeks logs13:04
FelixM- how is linux-rt testing done on the cip kernels?13:04
jkiI think we same topic confusion right now13:05
jkilet's move on to...13:05
jki#topic Kernel maintenance updates13:05
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:05
ulii've released 4.4 and reviewed 6.1.10113:05
pave1I'm reviewing 6.1.103/413:05
masamiThis week reported 19 new CVEs and 58 updated CVEs.13:05
jkiFelixM: please ask later again13:05
jkiother maintenance topics?13:06
patersoncI emailed a query about a CVE13:06
iwamatsu__I reviewed  6.1.10313:07
masamipatersonc: thank you for the report.13:07
masamiI updated13:07
patersoncOh wait, I see you replied - sorry13:07
masaminp13:07
patersoncThank you for updating13:07
jkireminds me of Christoph's work on CVE->config mapping13:08
jkiiwamatsu__: did you have the chance to look into that?13:09
iwamatsu__sorry,  I do not check yet. I will check next week.13:10
jkiok, TIA - will note that as AI ;)13:10
jkianything else?13:10
jki513:10
jki413:11
jki313:11
jki213:11
jki113:11
jki#topic Kernel release status13:11
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:11
jki5.10-rt is late13:11
pave1Yep.13:11
jkimissing stable-rt?13:11
pave1There's todays 5.10rt13:11
pave1available, can I ask for matching13:12
pave1-cip?13:12
jkiiwamatsu__:?13:13
iwamatsu__I can release linux-5.10.y-cip.13:14
pave1Thank you!13:14
iwamatsu__I will release tomorrow ,is it OK?13:14
pave1That's ok.13:14
iwamatsu__;-)13:14
jkigood - moving on then13:14
jki513:14
jki413:15
jki313:15
jki213:15
jki113:15
jki#topic Kernel testing13:15
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:15
FelixMWhile porting over a workload to the cip 6.1 kernel (using isar-cip-core), I noticed that the cip-kernel-config (defconfig) for x86 is not really suited for RT workloads:13:15
FelixMAt least CONFIG_RT_GROUP_SCHED=n and CONFIG_CPU_ISOLATION=y is missing. As we have some RT CIP kernel tests on kernelCI, I'm wondering what base config is used there and how that relates to the cip-kernel-config.13:15
patersoncI've been on hols, so not much from me from the testing side13:16
arisutThe effort on kci-dev tool for kernel maintainer and developers is going on, I released a draft but is still in draft phase13:17
arisutwhen will go into beta I hope cip can start testing it13:17
arisutcurrently just for reference this is the first draft https://github.com/aliceinwire/kci-dev13:18
arisutbut not functional yet13:19
arisutas we are still missing part of the api that the tool will interact to13:19
jkicool, I guess the cip maintainers will be happy to test once ready :)13:20
arisutbut there start to be interest around it13:20
patersoncGreat13:20
jkipavel: can you comment on Felix' question? or who else could?13:21
pave1Felix is telling us we are testing wrong configs.13:21
jkiare we?13:21
pave1I dunno.13:22
FelixMAt least we are not testing the "raw" cip-kernel-configs in the RT tests on kernelci.13:22
pave1We should be able to update them easily.13:22
FelixMIMHO it would be better for our users to have RT defconfigs that are tested and fit most use cases.13:22
jkiwhat are the effectiv configs we are using, in kernelci and in our own labs?13:23
FelixMIt's also about documenting what the cip-kernel-configs are intended to be used for. Is it just an example, or can shall they be used as a baseline for products?13:23
pave1Well -cip maintains our own configs normally.13:23
jkiour own lab is using cip-kernel-config, right?13:23
pave1Unless there's something seriously wrong,13:24
pave1can we get an email with proposed update and some kind of rationale?13:25
FelixMSure!13:25
pave1Others are testing defconfigs, we test these, I dont see urgent need to keep that13:26
pave1consistent.13:26
pave1cc iwamatsu, cip-dev13:26
FelixMOk, I'll prepare a summary and send that to the list + cc's13:26
pave1Thank you!13:27
jkiperfect, thanks!13:27
jkimore testing topics?13:27
jki513:28
jki413:28
jki313:28
jki213:28
jki113:28
jki#topic AOB13:28
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:28
jkianyone anything else for today?13:29
masamiI'll absent next week.13:29
patersoncI'll be absent for 2 weeks13:30
jkiok - enjoy!13:30
jkithen let's close in...13:31
jki513:31
jki413:31
jki313:31
jki213:31
jki113:31
jki#endmeeting13:31
collab-meetbotMeeting ended Thu Aug  8 13:31:17 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:31
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-08-13.03.html13:31
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-08-13.03.txt13:31
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-08-13.03.log.html13:31
*** 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/"13:31
jkithanks, all!13:31
pave1Thank you!13:31
iwamatsu__thank you13:31
ulithanks13:31
FelixMThanks!13:31
masamithank you13:31
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has quit IRC (Quit: Client closed)13:31
arisutthanks13:32
*** FelixM <FelixM!~FelixM@147.161.169.0> has quit IRC (Quit: FelixM)13:32
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:18
*** masami <masami!~masami@FL1-219-107-110-177.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)14:58
*** jki <jki!~jki@46.128.82.72> has quit IRC (Quit: Leaving)15:43
*** uli <uli!~quassel@static.153.40.69.159.clients.your-server.de> has quit IRC (Remote host closed the connection)16:01
*** uli <uli!~quassel@static.153.40.69.159.clients.your-server.de> has joined #cip16:01
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has quit IRC (Quit: Konversation terminated!)18:26
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has joined #cip18:27
*** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has joined #cip18:45
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.113> has quit IRC (Ping timeout: 248 seconds)21:19
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.108> has joined #cip21:20
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.108> has quit IRC (Ping timeout: 265 seconds)21:27
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has joined #cip21:32
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has quit IRC (Client Quit)21:35
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has joined #cip21:35
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has quit IRC (Client Quit)21:38
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has joined #cip21:38
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has quit IRC (Client Quit)21:40
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has joined #cip21:40
*** frieder <frieder!~frieder@88.130.219.77> has quit IRC (Remote host closed the connection)21:42
*** prasmi <prasmi!~prasmi@2a00:23c8:2500:a01:27e5:fd2b:c383:4217> has quit IRC (Ping timeout: 276 seconds)22:30
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has joined #cip23:24
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has quit IRC (Quit: hiromotai)23:32
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has joined #cip23:33

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!