12:02:58 <jki> #startmeeting CIP IRC weekly meeting
12:02:58 <collab-meetbot> Meeting started Thu Jun 22 12:02:58 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02:58 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:58 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:03:03 <jki> #topic AI review
12:03:06 <jki> 1. create kernelci pipeline for buster images (arisut)
12:04:02 <arisut> currently it can create the three different versions of isar-cip-core https://storage.kernelci.org/images/rootfs/cip/20230615/qemu-amd64/
12:04:24 <jki> means we are done (for now)?
12:04:32 <arisut> but I'm still finalizing things and also making the kernelci part
12:04:52 <jki> ok, close but not yet :)
12:04:53 <arisut> and will send the patch to isar-cip-core ML
12:05:04 <arisut> yes
12:05:06 <jki> good
12:05:08 <iwamatsu> hi all.
12:05:16 <jki> hi!
12:05:17 <arisut> we made progress but not yet finished yet
12:05:26 <arisut> hi iwamatsu
12:07:08 <jki> anything else on AIs?
12:07:19 <jki> 5
12:07:21 <jki> 4
12:07:23 <jki> 3
12:07:24 <jki> 2
12:07:25 <jki> 1
12:07:27 <jki> #topic Kernel maintenance updates
12:07:42 <masami> This week reported 11 new CVEs and 0 updated CVEs.
12:07:44 <uli> reviewing 6.1.34
12:07:57 <pave1> I did reviews -- 6.1.34 and .35
12:08:21 <iwamatsu> I reviewed 6.1.33, 34 and 35
12:08:45 <pave1> 6.1.x branch should be ready for release.
12:09:05 <iwamatsu> ;-)
12:11:28 <jki> good - anything else?
12:12:04 <jki> 5
12:12:05 <jki> 4
12:12:06 <jki> 3
12:12:07 <jki> 2
12:12:08 <jki> 1
12:12:10 <jki> #topic Kernel release status
12:12:13 <jki> -4.4
12:12:21 <uli> on track
12:12:52 <jki> -4.19
12:13:16 <iwamatsu> on track
12:13:45 <jki> rt as well?
12:13:51 <iwamatsu> yes
12:14:00 <jki> -5.10
12:14:07 <iwamatsu> on track
12:14:11 <jki> indeed :)
12:14:13 <pave1> -rt was released today.
12:14:22 <jki> perfect, thanks!
12:14:26 <jki> -6.1
12:14:33 <jki> ready to launch, I heard
12:14:48 <pave1> I'd say so.
12:15:02 <jki> will then ask for the OK in the TSC meeting on monday
12:15:05 <pave1> I will be based on older -stable by the
12:15:20 <pave1> time we release it, but I guess that's okay.
12:15:50 <iwamatsu> +1
12:15:54 <jki> we need to think about the release cycle we want to commit on here
12:16:07 <jki> 2x per month?
12:16:22 <patersonc[m]> pave1: Is there time to update it to the latest stable before release?
12:16:35 <pave1> I'd say 2x per month -cip, 1x per month -cip-rt and
12:16:53 <pave1> move 5.10 to slower releases.
12:17:14 <jki> what would be the suggest there?
12:17:30 <jki> would we have to make 5.10 slower to handle 6.1?
12:17:32 <pave1> peterson -- it would be better to do -cip1 and then move it forward
12:17:42 <pave1> using normall process.
12:17:52 <patersonc[m]> Okay
12:18:16 <iwamatsu> Who is in charge of 6.1? Pavel?
12:18:32 <pave1> Iwamatsu?
12:18:52 <pave1> You do the regular releases, I do the rt?
12:19:22 <iwamatsu> OK, same as 5.10 and 4.19.
12:19:34 <pave1> I'd suggest that.
12:20:00 <jki> iwamatsu: is that doable for you from your workload situation?
12:21:27 <iwamatsu> Yes, I have spoken to and agreed with my boss about it in this term.
12:21:47 <jki> ok
12:21:51 <jki> thanks
12:21:58 <iwamatsu> s/in this/from this/
12:21:58 <jki> a lot :)
12:22:36 <jki> back to "would we have to make 5.10 slower to handle 6.1?" then
12:22:54 <jki> I want to be clear here when CIP members ask me this
12:23:13 <jki> maybe some will not be happy about that, maybe they are ok, can't predict
12:23:56 <pave1> It would be good so that our workload does not grow too quickly.
12:24:29 <pave1> We can probably handle the extra workload if it is really required.
12:25:02 <jki> ok, some room for negotiation if needed
12:25:13 <pave1> yes.
12:26:31 <jki> just checking https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
12:26:41 <jki> we have 2x per month for 4.19 still
12:27:06 <jki> just -rt is lagging behind there, significantly
12:27:27 <pave1> I believe we should make 4.19-cip slower, too.
12:28:06 <jki> looking at who does regular releases, this is particularly a question for iwamatsu, right?
12:28:21 <pave1> yes.
12:29:28 <iwamatsu> Yes, the 4.19 release cadence is widening.
12:30:02 <jki> then make it official there, ok, noted
12:30:25 <jki> and 5.10 is where we may react on feedback
12:30:33 <jki> let's see...
12:30:52 <jki> reference targets for 6.1 initially?
12:30:54 <jki> qemu only?
12:31:20 <pave1> The boards we have in the lab?
12:32:02 <pave1> I assumed that when we got configs it meant they want it as reference hw.
12:33:40 <iwamatsu> I recieved patches for confog of IPC27e and Renesas devices.
12:33:57 <iwamatsu> RZV2M
12:34:00 <jki> so the list is not full
12:34:09 <jki> where did we put them formally, btw?
12:34:22 <jki> I mean the list
12:34:41 <jki> ah, found: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
12:34:44 <patersonc[m]> https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
12:37:16 <jki> so, we add qemu, ipc227e and ? there
12:37:31 <jki> RZV2M is already listed there?
12:37:41 <jki> HiHope?
12:38:05 <patersonc[m]> RZ/V2M is a different board
12:38:10 <iwamatsu> maybe V2M is other board
12:38:12 <patersonc[m]> We're not proposing it as a reference board
12:38:29 <jki> ok, then qemu and the ipc only
12:38:35 <patersonc[m]> I'm happy for RZ/G1M iwg20m and RZ/G2M hihope to be reference boards
12:38:36 <jki> folks can always ask for more later
12:38:59 <jki> but do we have configs for 6.1 for those already?
12:39:06 <patersonc[m]> Yes
12:39:19 <jki> then I'm adding those as well
12:39:49 <jki> anything else?
12:40:58 <patersonc[m]> Thanks
12:41:17 <jki> then let's move on...
12:41:20 <jki> 5
12:41:22 <jki> 4
12:41:24 <jki> 3
12:41:25 <jki> 2
12:41:27 <jki> 1
12:41:28 <jki> #topic Kernel testing
12:41:44 <arisut> nothing other than the AI
12:41:56 <arisut> for me
12:42:20 <arisut> patersonc[m]:?
12:42:43 <patersonc[m]> sietze and I have been working on a prototype squad server
12:42:56 <patersonc[m]> Nothing to show yet though, but getting there
12:43:18 <jki> coool
12:43:44 <patersonc[m]> That's probably about it other then prepping for next week
12:44:15 <jki> don't mention "next week prepping"... ;)
12:44:20 <jki> ok
12:44:28 <patersonc[m]> :P
12:45:09 <jki> just saw that our reference hardware table lists qemu-riscv64 only as candidate - I think that was accepted, no?
12:45:27 <pave1> I should mention that Prague should be outside of range of terror attack on Zaporohzia...
12:46:35 <pave1> jki -- not sure. We still have no serious risc-v hardware, so
12:46:58 <jki> ...at CIP
12:47:02 <pave1> how much effort should go to risc-v still sounds like open question.
12:47:10 <jki> I'm using a VS2 in local "production" mode
12:47:10 <patersonc[m]> It would be good to add the qemu for risc-v
12:47:23 <jki> VisionFive2 I mean
12:47:30 <patersonc[m]> Nice
12:47:38 <patersonc[m]> I keep meaning to hook one up to my lab at home
12:48:30 <jki> CIP committed on maintaining 5.10, and likely 6.1 as well, for riscv64
12:48:36 <pave1> I'd say that reference board is strong commitment, but if Renesas wants that, lets do it.
12:48:42 <jki> and that implied to me that we commited on qemu at least
12:49:14 <patersonc[m]> I think if we're supporting risc-v we at least need a qemu "reference board"
12:49:15 <pave1> ok.
12:49:48 <jki> we announced to support riscv with the kernel, not userland, not rt yet
12:50:11 <jki> I think the wiki is just outdated, but I can bring that up for clarification in the TSC as well
12:50:46 <patersonc[m]> +1
12:50:51 <iwamatsu> I have it+1
12:51:02 <pave1> All the reference hardware will need to be approved by TSC, right? So these are just our suggestions...
12:51:04 <iwamatsu> +1
12:51:15 <jki> yes
12:51:24 <jki> but I think we got that already, let's clarify
12:52:11 <jki> ok, then anything else on testing?
12:52:22 <jki> 5
12:52:24 <jki> 4
12:52:26 <jki> 3
12:52:28 <jki> 2
12:52:30 <jki> 1
12:52:32 <jki> #topic AOB
12:53:03 <jki> survey update: who all will be in Prague now?
12:53:06 <arisut> I will be away from 28 June to 18 July
12:53:15 <patersonc[m]> o/
12:53:16 <uli> o/
12:53:20 <jki> o/
12:53:25 <iwamatsu> o/
12:53:32 <pave1> I'll be in Prague. Then week of travel.
12:54:11 <hiromotai[m]> o/
12:54:43 <jki> should we skip irc next week then and rather have lunch together, maybe on Thursday?
12:55:08 <jki> (besides all the other meetups we will have anyways ;)
12:55:24 <patersonc[m]> +1
12:56:23 <uli> +1
12:56:30 <pave1> !
12:56:35 <pave1> +1
12:56:41 <iwamatsu> +1
12:56:43 <sietze> +1
12:56:44 <jki> then let's gather at lunch on Thursday at the CIP booth
12:56:49 <jki> great!
12:57:35 <jki> any other business?
12:57:55 <jki> 5
12:57:56 <jki> 4
12:57:58 <jki> 3
12:57:59 <jki> 2
12:58:00 <arisut> I will be away from 28 June to 18 July
12:58:01 <jki> 1
12:58:05 <jki> noteded
12:58:07 <jki> :)
12:58:14 <jki> enjoy!
12:58:25 <jki> #endmeeting