#
✕ nick:yuka
#asahi-dev · 2026-05-06 19:59
yukaon the m1n1 side latest main + comment out some things: https://yuyu.yuka.dev/public/m1n1-comment-out-things-for-neo-smp.diff
#asahi-dev · 2026-05-06 19:53
yukachewyeclaire: try https://yuyu.yuka.dev/public/0001-HACK-always-save-registers-before-wfi-stub-out-wfit.patch
#asahi-dev · 2026-05-06 19:53
yukachewyeclaire: you need nothing close to this complicated to get smp running
#asahi-dev · 2026-05-06 19:52
yukathanks
#asahi-dev · 2026-05-06 19:25
yukajannau: you forgot to check in t6031-dieX.dtsi on asahi-wip?
#asahi-dev · 2026-05-06 19:04
yukaI think its purpose was not SErroring on attempting to set the boot cpu rvbar, which is now served by the new check
#asahi-dev · 2026-05-06 19:03
yukathe cpu.state == running also felt like a footgun in case the boot cpu rvbar _was_ changed it would silently be skipped
#asahi-dev · 2026-05-06 19:02
yukawhatever started m1n1 might have skipped setting the secondary rvbars
#asahi-dev · 2026-05-06 19:02
yukaI'm not so sure about the secondary cpu rvbars
#asahi-dev · 2026-05-06 18:55
yukathis is done by smp.c
#asahi-dev · 2026-05-06 18:54
yukaFor chainload.py, I would say this is ok since here the purpose is not to clear the lock bit
#asahi-dev · 2026-05-06 18:54
yukawhat do you think about this? https://github.com/AsahiLinux/m1n1/pull/577/changes/4263ab7a661de8ebe578f5bc1f0bfc88e8f322dd
#asahi-dev · 2026-05-06 18:53
yukaso just make the assumption that the current rvbar should be the currently running m1n1's base
#asahi-dev · 2026-05-06 18:53
yukaOhh
#asahi-dev · 2026-05-06 18:49
yuka"the code", so you would still do the write?
#asahi-dev · 2026-05-06 18:48
yukawill do
#asahi-dev · 2026-05-06 18:48
yukaAh no, replacing it with a check and erroring out
#asahi-dev · 2026-05-06 18:47
yukaThis means basically removing the entire "Setting secondary CPU RVBARs...", right?
#asahi-dev · 2026-05-06 18:42
yukaAlthough I would assume anyone working on that right now can also just comment out the smp_start_secondaries call in linux.py / chainload.py
#asahi-dev · 2026-05-06 18:41
yukaI guess it could be reverted until we have fixed that
#asahi-dev · 2026-05-06 18:41
yukaIf anything it might cause people to run into the SError
#asahi-dev · 2026-05-06 18:40
yukaAh
#asahi-dev · 2026-05-06 18:40
yukais _not_ wrong?
#asahi-dev · 2026-05-06 18:40
yukaI don't think we have something like cpu_features->cyc_ovrd in the proxyclient side
#asahi-dev · 2026-05-06 18:39
yukaFor chainload.py, is there any case where we are actually setting rvbar to something different?
#asahi-dev · 2026-05-06 18:35
yukaimo there's nothing wrong with that one
#asahi-dev · 2026-05-06 18:35
yukano
#asahi-dev · 2026-05-06 18:28
yukaI always applied this on my local checkout
#asahi-dev · 2026-05-06 18:28
yukaAnd I think the switch boot core function is quite useful to have
#asahi-dev · 2026-05-06 18:28
yukaI was going to ask: can you merge the smp.c bits from #563 after reverting #536? Then we have less rebase/merge pains later
#asahi-dev · 2026-05-06 18:27
yuka536 vs 563
#asahi-dev · 2026-05-06 18:27
yukaAhh
#asahi-dev · 2026-05-06 18:27
yuka(number)
#asahi-dev · 2026-05-06 18:27
yuka#536 is the wrong PR
#asahi-dev · 2026-05-06 18:27
yukaSorry
#asahi-dev · 2026-05-06 18:24
yuka2. the purpose of setting the cpu_impl_reg[0] is setting rvbar to the correct value (-> also wrong, the purpose is also to clear the lock bit so that the rvbar can be set again later once the core is started)
#asahi-dev · 2026-05-06 18:23
yuka1. the lock bit means we can not write the rvbar (-> wrong, we can clear it, depending on whether this core is already running and what platform we are on)
#asahi-dev · 2026-05-06 18:22
yuka#536 was fundamentally based on wrong assumptions:
#asahi-dev · 2026-05-06 18:22
yukathen I will start from a clean slate
#asahi-dev · 2026-05-06 18:22
yukathat's ok
#asahi-dev · 2026-05-06 18:22
yukaI think I now know the wrong assumptions and I will come up with something
#asahi-dev · 2026-05-06 18:18
yukaall P-Cores
#asahi-dev · 2026-05-06 18:16
yukaP-Cores SError on write, E-Cores silently ignore the write
#asahi-dev · 2026-05-06 18:16
yukaon M4, P-Cores and E-Cores behave differently
#asahi-dev · 2026-05-06 18:16
yukaAh
#asahi-dev · 2026-05-06 18:11
yuka> > > read64(0x210050000) = 0x10010002114001
#asahi-dev · 2026-05-06 18:11
yuka> > > write64(0x210050000, 0x10010002114000)
#asahi-dev · 2026-05-06 18:11
yuka> > > read64(0x210050000) = 0x10010002114001
#asahi-dev · 2026-05-06 18:11
yukait doesn't SError but it also doesn't apply the new value
#asahi-dev · 2026-05-06 18:11
yukaAh no

plus ›