Thursday, 2024-01-04

« Wednesday, 2024-01-03 Index Friday, 2024-01-05 »
*** rajm <rajm!~robert@82.27.50.32> has joined #cip07:32
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip07:50
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip09:14
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip12:15
*** jki <jki!~jki@46.128.89.130> has joined #cip12:56
*** masami <masami!~masami@fl1-219-107-72-235.tky.mesh.ad.jp> has joined #cip12:59
jkihappy new year, everyone!13:00
sietzeHappy new year!13:00
patersoncHappy new year!13:00
ulihappy new year13:00
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip13:00
masamihappy new year13:00
pave1happy new year :-)13:00
jkithen let's get this started...13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbot`Meeting started Thu Jan  4 13:01:33 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
jki#topic AI review13:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:01
jkistill on my list...13:01
jkiI don't have more recorded - anything missing?13:02
jki513:02
jki413:02
jki313:02
pave1I think that's all.13:02
jki213:02
jki113:02
jki#topic Kernel maintenance updates13:02
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
masamiThis week reported 4 new CVEs and 2 updated CVEs.13:02
pave1I did reviews, 6.1.70 and 71.13:02
ulireviewing 6.1.7013:02
pave1masami: I see you now track 4.4-st. Nice, thanks!13:03
masamipavel: your welcome :)13:03
jkianything else?13:04
jkino corrupted filesystems or broken wifi so far in this year? ;)13:05
jki513:06
jki413:06
jki313:06
pave1Just broken hw, but saving that for "aob" section :-)13:06
jki213:06
jki113:06
uliraid1 in 4.4 fixed last year, but only released this year; does that count?13:06
jkiall good :)13:06
jkithen let's move on13:06
jki#topic Kernel release status13:06
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:06
jkinobuhiro's script should go here13:07
jki4.413:07
pave1basically we are ok. Continue? :-)13:07
ulii guess. :) cip83 is out13:07
jkiyeah, I think I only saw no update to 5.10-rt yesterday13:08
jkiso, 4.4, 4.19, 6.1 - all recently updated13:08
jki5.10 vanilla as well13:09
pave1I believe 5.10-rt is due next month?13:09
jkiend of this month13:10
jkiok13:10
jkino problems ahead as well, I assume13:10
jkithen moving on...13:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel testing13:10
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:10
patersoncHello13:10
patersoncI've spent a bit of time looking into some of the SW update use cases in LAVA, but other then that I've mainly been on holiday feasting13:11
jkithere were a lot of discussions on the related issue, indeed13:12
patersoncOn the positive side, all of the labs stayed online throughout the holiday period13:13
jkithat's kind of them13:14
jkiother testing topics?13:14
pave1You may want to check 6.6-stable results13:14
pave1https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/112599008213:14
pave1de0nanosoc always fails.13:15
pave1iirc it is not a fluke.13:15
patersoncThanks pave1, will do13:15
pave1(y)13:15
jkiis that board in our lab?13:16
patersoncYou have one13:17
patersoncOther two are in the denx lab13:17
jkiso the issue is not lab-specific, rather board-related13:18
patersoncMore than likely, but we'll have to investigate13:19
jkilooks like the siemens config passes13:19
jkiok13:19
jkithen move on...?13:19
jki513:19
jki413:19
jki313:19
jki213:19
jki113:19
jki#topic AOB13:20
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:20
pave1Ok, so buggy hardware.13:20
patersoncjkl: Yes, it's multi_v7_defconfig that's failing13:20
patersoncSo maybe a kernel configuration issue13:20
pave1After the kernel patch discussion about the Renesas R-V board, I don't believe we should make that official "cip board".13:21
pave1OTOH the kernel patches seem quite reasonable.13:21
pave1I see no problem taking them.13:21
pave1But the problems in userland really seem bad.13:21
jkiwe have up to option 3 in Chris' list at least (userland from other sources, just for basic testing)13:22
patersoncThe emulation approach that jkl suggested could work, but would be a lot of work to get running13:22
jkiyes, I'm afraid of that as well13:22
patersoncI don't know if it's a route RISC-V is planning in general or not13:23
jkibut you still wanted to check if the rebuild impact could be limited to certain packages13:23
patersoncYes, prabhakarlad is looking into that13:23
jkino, this is no general risc-v topic, it remains specific to your IP13:23
jkithat is the reason why there will be no general userland solution13:24
pave1One small chance would be...13:24
pave1...if it was discovered that starting at 0x50000 is a bad idea because it is not on 2MB (or whatever) boundary13:25
pave1and it impacts performance in general due to increased TLB pressure.13:25
jki...that should have been discovered earlier, no?13:25
pave1Dunno. putting code this low seems strange.13:26
pave1Or maybe that putting code this low is bad for security because bigger guard area is needed.13:26
jkiwell, the binutils patch was reject upstream already IIRC13:27
pave1Send them a chocolate or something :-).13:28
patersoncHa13:28
pave1Dunno. 0x50000 is in the middle of PMD, so it seems like wrong start address. Putting code at start of PUD could be a tiny bit better for TLBs and thus performance.13:29
pave1If it is, that could convince someone. And chocolate, I guess :-).13:29
prabhakarladjki: yep binutils patch was rejected. Palmer suggested to handle it in the toolchain.13:30
pave1And can it be handled in the toolchain?13:30
jkiwhat does "handle it in the toolchain" mean?13:30
prabhakarladhttps://paste.debian.net/1303035/13:32
prabhakarladlet me find the complete link.13:32
jki"and we might want that as a tunable for13:33
jkidistros anyway (for huge page alignment, for example)."13:33
jkithat's what pavel is talking about13:33
pave1Yep :-).13:33
jkiyou need to follow up on that - before the gates are closing for trixie!13:33
patersoncSo for now, is CIP okay to take the kernel support as-is?13:36
patersoncOn the assumption that "official" reference platform acceptance is only if a working solution is found for userspace13:36
pave1Kernel patches look reasonable.13:36
jkibecause even if we had that tunable, it still takes Debian (or any other distro) to tune that as needed, for whole riscv6413:36
jkianything else?13:39
pave1So...13:40
pave1Is the plan to just apply the kernel patches even when we don't have the userspace?13:40
jkiprovided renesas looks after testing, it should be a way forward13:40
jkibut they also need to push harder on a userspace solution IMHO13:41
pave1Ok, sounds good. So I expect another series, not marked "RFC" when testing is sorted out.13:41
patersoncI'll add some support for simple boot testing to start with, using a Poky image13:42
patersoncAnd test the RFC with it13:42
patersoncIf it works we'll submit a v113:43
pave1Could we also get some qemu risc-v testing?13:44
pave1Right now I don't see one.13:44
pave1https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/112599038013:44
patersoncYes this is needed13:45
pave1Thank you!13:45
jkiwe should soon have isar-cip-core generating riscv images more reliably again13:45
jkiif that helps as well13:45
patersoncyep13:46
jkiok, I can plug something together based on my pending isar patches13:47
jkimore topics for today?13:47
jki413:47
jki313:47
jki213:47
jki113:47
jki#endmeeting13:47
collab-meetbot`Meeting ended Thu Jan  4 13:47:48 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:47
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/01/cip.2024-01-04-13.01.html13:47
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/01/cip.2024-01-04-13.01.txt13:47
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/01/cip.2024-01-04-13.01.log.html13:47
*** 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:47
jkithank you all!13:47
patersoncCheers13:48
pave1Thank you!13:48
masamithank you13:48
ulithanks13:48
sietzeThanks!13:48
*** masami <masami!~masami@fl1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:48
*** jki <jki!~jki@46.128.89.130> has quit IRC (Quit: Leaving)13:55
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)14:05
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip15:25
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)15:51
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:56
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip15:56
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)15:59
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)22:38
*** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 245 seconds)22:44
« Wednesday, 2024-01-03 Index Friday, 2024-01-05 »

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