13:03:28 <jki> #startmeeting CIP IRC weekly meeting
13:03:28 <collab-meetbot> Meeting 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:28 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:03:28 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:03:34 <jki> #topic AI review
13:03:41 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:04:01 <jki> So, no one did that in my absence - seems I have to now :)
13:04:15 <pave1> I'm reviewing 6.1.103/104.
13:04:15 <jki> I didn't find other AIs in the last weeks logs
13:04:15 <FelixM> - how is linux-rt testing done on the cip kernels?
13:05:04 <jki> I think we same topic confusion right now
13:05:21 <jki> let's move on to...
13:05:23 <jki> #topic Kernel maintenance updates
13:05:43 <uli> i've released 4.4 and reviewed 6.1.101
13:05:43 <pave1> I'm reviewing 6.1.103/4
13:05:46 <masami> This week reported 19 new CVEs and 58 updated CVEs.
13:05:57 <jki> FelixM: please ask later again
13:06:48 <jki> other maintenance topics?
13:06:56 <patersonc> I emailed a query about a CVE
13:07:04 <iwamatsu__> I reviewed  6.1.103
13:07:18 <masami> patersonc: thank you for the report.
13:07:23 <masami> I updated
13:07:27 <patersonc> Oh wait, I see you replied - sorry
13:07:41 <masami> np
13:07:43 <patersonc> Thank you for updating
13:08:35 <jki> reminds me of Christoph's work on CVE->config mapping
13:09:18 <jki> iwamatsu__: did you have the chance to look into that?
13:10:05 <iwamatsu__> sorry,  I do not check yet. I will check next week.
13:10:26 <jki> ok, TIA - will note that as AI ;)
13:10:34 <jki> anything else?
13:10:59 <jki> 5
13:11:00 <jki> 4
13:11:02 <jki> 3
13:11:03 <jki> 2
13:11:05 <jki> 1
13:11:07 <jki> #topic Kernel release status
13:11:15 <jki> 5.10-rt is late
13:11:24 <pave1> Yep.
13:11:33 <jki> missing stable-rt?
13:11:44 <pave1> There's todays 5.10rt
13:12:09 <pave1> available, can I ask for matching
13:12:15 <pave1> -cip?
13:13:41 <jki> iwamatsu__:?
13:14:00 <iwamatsu__> I can release linux-5.10.y-cip.
13:14:15 <pave1> Thank you!
13:14:22 <iwamatsu__> I will release tomorrow ,is it OK?
13:14:34 <pave1> That's ok.
13:14:41 <iwamatsu__> ;-)
13:14:57 <jki> good - moving on then
13:14:59 <jki> 5
13:15:01 <jki> 4
13:15:03 <jki> 3
13:15:04 <jki> 2
13:15:05 <jki> 1
13:15:07 <jki> #topic Kernel testing
13:15:19 <FelixM> While 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:21 <FelixM> At 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:16:56 <patersonc> I've been on hols, so not much from me from the testing side
13:17:20 <arisut> The effort on kci-dev tool for kernel maintainer and developers is going on, I released a draft but is still in draft phase
13:17:58 <arisut> when will go into beta I hope cip can start testing it
13:18:59 <arisut> currently just for reference this is the first draft https://github.com/aliceinwire/kci-dev
13:19:13 <arisut> but not functional yet
13:19:56 <arisut> as we are still missing part of the api that the tool will interact to
13:20:35 <jki> cool, I guess the cip maintainers will be happy to test once ready :)
13:20:37 <arisut> but there start to be interest around it
13:20:42 <patersonc> Great
13:21:27 <jki> pavel: can you comment on Felix' question? or who else could?
13:21:33 <pave1> Felix is telling us we are testing wrong configs.
13:21:47 <jki> are we?
13:22:00 <pave1> I dunno.
13:22:22 <FelixM> At least we are not testing the "raw" cip-kernel-configs in the RT tests on kernelci.
13:22:39 <pave1> We should be able to update them easily.
13:22:41 <FelixM> IMHO it would be better for our users to have RT defconfigs that are tested and fit most use cases.
13:23:30 <jki> what are the effectiv configs we are using, in kernelci and in our own labs?
13:23:50 <FelixM> It'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:51 <pave1> Well -cip maintains our own configs normally.
13:23:52 <jki> our own lab is using cip-kernel-config, right?
13:24:29 <pave1> Unless there's something seriously wrong,
13:25:01 <pave1> can we get an email with proposed update and some kind of rationale?
13:25:37 <FelixM> Sure!
13:26:03 <pave1> Others are testing defconfigs, we test these, I dont see urgent need to keep that
13:26:11 <pave1> consistent.
13:26:31 <pave1> cc iwamatsu, cip-dev
13:26:56 <FelixM> Ok, I'll prepare a summary and send that to the list + cc's
13:27:10 <pave1> Thank you!
13:27:16 <jki> perfect, thanks!
13:27:37 <jki> more testing topics?
13:28:09 <jki> 5
13:28:10 <jki> 4
13:28:12 <jki> 3
13:28:13 <jki> 2
13:28:15 <jki> 1
13:28:17 <jki> #topic AOB
13:29:01 <jki> anyone anything else for today?
13:29:25 <masami> I'll absent next week.
13:30:18 <patersonc> I'll be absent for 2 weeks
13:30:49 <jki> ok - enjoy!
13:31:05 <jki> then let's close in...
13:31:07 <jki> 5
13:31:09 <jki> 4
13:31:11 <jki> 3
13:31:13 <jki> 2
13:31:15 <jki> 1
13:31:17 <jki> #endmeeting