#asahi-dev · 2026-06-10 13:22
chaos_princesshttps://gist.github.com/networkextension/14fb3997867eeca41309149cb54ef34b#asahi-dev · 2026-06-10 13:22
nickchanmentioned the other day#asahi-dev · 2026-06-10 13:21
nickchanwhere does the name APL_INTENABLE_EL2 comes from #asahi-dev · 2026-06-10 12:54
svenSYS_IMP_APL_VM_TMR_FIQ_ENA_EL2#asahi-dev · 2026-06-10 12:54
svenyeah#asahi-dev · 2026-06-10 12:43
mazthe timer mask register?#asahi-dev · 2026-06-10 12:40
svendid someone check if that aic sysreg is writable on the 27 betas now?#asahi-dev · 2026-06-10 11:39
yukaMight be possible to figure out (at least confirm/disprove that ACC_OVRD is sufficient) using the macho boot mode#asahi-dev · 2026-06-10 10:03
yukasven: I don't know which sysregs we need write access to. possibly ACC_OVRD but it doesn't differ between the boot and secondary cores so it's not the (only) one causing the different wfi behaviour.#asahi-dev · 2026-06-10 09:44
StanfordAppliedCyber[m]but given it's almost 3am this is a problem for later today#asahi-dev · 2026-06-10 09:44
StanfordAppliedCyber[m]something's up with the dcp, it's not completing its firmware handshake#asahi-dev · 2026-06-10 09:44
StanfordAppliedCyber[m]well, there's 150 processes, windowserver is running, it feels like i'm very, very close to a working hypervisor#asahi-dev · 2026-06-10 09:38
svenyuka: can you file a report about that wfi stuff and what sysregs we need write access to? or do you want me to do that?#asahi-dev · 2026-06-10 09:38
StanfordAppliedCyber[m]suffice to say, either of these two problems means 26.5 isnt very appealing#asahi-dev · 2026-06-10 09:38
svenyuuup, heuristics then #asahi-dev · 2026-06-10 09:37
StanfordAppliedCyber[m]sven: i did quite literally nothing but rerun my test and this time i lost every register#asahi-dev · 2026-06-10 09:37
StanfordAppliedCyber[m]well#asahi-dev · 2026-06-10 09:37
StanfordAppliedCyber[m]oh#asahi-dev · 2026-06-10 09:26
StanfordAppliedCyber[m]it's schedule interrupt, write a bunch of registers, wfi, wait for the interrupt to wake us up, dump all registers, return#asahi-dev · 2026-06-10 09:25
svenyuka knows better but I think it was locked in the heuristic retention mode #asahi-dev · 2026-06-10 09:25
StanfordAppliedCyber[m]no this test is artificial#asahi-dev · 2026-06-10 09:25
StanfordAppliedCyber[m]oh ffs#asahi-dev · 2026-06-10 09:25
svenbecause there’s a heuristic that determines if wfi looses state iirc #asahi-dev · 2026-06-10 09:25
StanfordAppliedCyber[m]the test is a dumb asm blob#asahi-dev · 2026-06-10 09:25
svenis the test booting Linux?#asahi-dev · 2026-06-10 09:25
StanfordAppliedCyber[m]i'm being terse#asahi-dev · 2026-06-10 09:25
StanfordAppliedCyber[m]oh yeah that's what i mean#asahi-dev · 2026-06-10 09:24
svenwe don’t really need latest macos on the older socs #asahi-dev · 2026-06-10 09:24
svenokay good #asahi-dev · 2026-06-10 09:24
svenit fine to upstream something that only works on m4:a18 fwiw#asahi-dev · 2026-06-10 09:24
StanfordAppliedCyber[m]yeah i ran the test on a secondary#asahi-dev · 2026-06-10 09:24
svenon secondary cores?#asahi-dev · 2026-06-10 09:23
StanfordAppliedCyber[m]sven: wfi issue is fixed, all register state is saved#asahi-dev · 2026-06-10 09:23
StanfordAppliedCyber[m]my goal is to get it working with the latest macos version on all SoCs including sptm enabled ones#asahi-dev · 2026-06-10 09:23
StanfordAppliedCyber[m]^ at the moment#asahi-dev · 2026-06-10 09:22
StanfordAppliedCyber[m]oh, it's probably worth mentioning making it clear that the hypervisor only supports old macos versions on non sptm enabled socs#asahi-dev · 2026-06-10 08:41
StanfordAppliedCyber[m]sptm itself is not helpful to linux, and my emulator is tainted anyways and i'll never push that code, but we need to find a way to get macos working on sptm enabled systems so we can watch what it does#asahi-dev · 2026-06-10 08:40
StanfordAppliedCyber[m]commpage fixups, timer stuff, register handling, some interrupt stuff (which i'm hoping i can actually delete)#asahi-dev · 2026-06-10 08:40
StanfordAppliedCyber[m]there's a lot of hypervisor stuff that can be upstreamed to m1n1 because it's my code and is definitely needed for the support of newer macos/socs#asahi-dev · 2026-06-10 08:39
Sobek[m]<StanfordAppliedCyber[m]> "for a bit of context on me my..." <- What is this hypervisor doing ? (I thought SPTM emulation was a RE requirement only, not to be upstreamed in Linux ?)#asahi-dev · 2026-06-10 08:38
StanfordAppliedCyber[m]:(#asahi-dev · 2026-06-10 08:38
svenso not fixed yet :(#asahi-dev · 2026-06-10 08:37
StanfordAppliedCyber[m]yeah, msr that register --> Exception: SYNC#asahi-dev · 2026-06-10 08:32
StanfordAppliedCyber[m]sven: reads work fine, writes fault#asahi-dev · 2026-06-10 08:30
StanfordAppliedCyber[m]but this is pure speculation on my part#asahi-dev · 2026-06-10 08:30
StanfordAppliedCyber[m]it's possibly to support machines that don't have exclave support, and the code is basically just vestigal#asahi-dev · 2026-06-10 08:30
StanfordAppliedCyber[m]i wonder why this path even exists? like exclaves are just always turned on#asahi-dev · 2026-06-10 08:25
StanfordAppliedCyber[m]just grep "ex" or "exclave" in the adt#asahi-dev · 2026-06-10 08:25
StanfordAppliedCyber[m]you do have to clean up the adt a bit#asahi-dev · 2026-06-10 08:23
StanfordAppliedCyber[m]how long that'll be true, who knows