#asahi-dev · 2026-05-14 07:08
StanfordAppliedCyber[m]reading from reg-private +0x30 causes an serror storm?#asahi-dev · 2026-05-14 06:18
StanfordAppliedCyber[m]okay, let's replay the macos reads in the exact same order#asahi-dev · 2026-05-14 06:18
StanfordAppliedCyber[m]clean, completely fresh#asahi-dev · 2026-05-14 06:18
StanfordAppliedCyber[m]nothing else#asahi-dev · 2026-05-14 06:18
StanfordAppliedCyber[m]literally p.read32(0x210050020), then cpu0_ps = 0x1f0 and cluster0_ps = 0x21f0#asahi-dev · 2026-05-14 06:16
StanfordAppliedCyber[m]READS are load bearing?#asahi-dev · 2026-05-14 06:16
StanfordAppliedCyber[m]what the fuck#asahi-dev · 2026-05-14 06:16
StanfordAppliedCyber[m]reading from cpu-impl-reg + 0x20 changes the core pstate#asahi-dev · 2026-05-14 06:09
StanfordAppliedCyber[m].......there might be an mmio read here#asahi-dev · 2026-05-14 06:05
StanfordAppliedCyber[m]in a vacuum i'd say this feels like a sysreg-- but afaik sysregs have never been involved in smp init in apple silicon#asahi-dev · 2026-05-14 05:54
StanfordAppliedCyber[m]--> it definitely performed the mmio writes it expected to start the cpu#asahi-dev · 2026-05-14 05:54
StanfordAppliedCyber[m]and this trace is from a run where macos panicked on "waited some ms for cpu core to start"#asahi-dev · 2026-05-14 05:42
StanfordAppliedCyber[m]i'm replaying, quite literally, every single mmio write macos made in the same order#asahi-dev · 2026-05-14 05:42
StanfordAppliedCyber[m]something fishy is going on here#asahi-dev · 2026-05-14 04:46
StanfordAppliedCyber[m]failed to start the secondaries also#asahi-dev · 2026-05-14 04:46
StanfordAppliedCyber[m]the only thing i can think of is that i have a sort of weird setup-- basically chainload.py doesn't work on my machine, so i broke m1n1 into a tiny dumb loader with an embedded kernelcache, which is flashed to 1tr, and the rest of m1n1 which i stream over uart to a specific location in memory then jump to a raw physical address, but i also literally just cloned yuka's m1n1 branch with the commits, flashed that in 1tr, and it#asahi-dev · 2026-05-14 04:44
StanfordAppliedCyber[m]previously i've had other stuff there including _vectors_start, the m1n1 entrypoint, basically anything you can think of#asahi-dev · 2026-05-14 04:41
StanfordAppliedCyber[m]that counter has never been hit#asahi-dev · 2026-05-14 04:40
StanfordAppliedCyber[m]currently i literally just have an instruction that increments a counter then calls WFE just so that if any core drops out of reset i see the side effect#asahi-dev · 2026-05-14 04:40
StanfordAppliedCyber[m]what i've been doing is writing different instructions to that address#asahi-dev · 2026-05-14 04:40
StanfordAppliedCyber[m]sorry, let me clarify, my value in rvbar is 0x10004ef0000 which i can verify i can't change#asahi-dev · 2026-05-14 04:30
StanfordAppliedCyber[m]what i don't get is that for everyone else it seemed to "just work" and nothing in my mmio traces stick out as "wow this is super different about my system"#asahi-dev · 2026-05-14 04:26
StanfordAppliedCyber[m]i did previously try m1n1 entrypoint#asahi-dev · 2026-05-14 04:26
StanfordAppliedCyber[m]well i've tried a bunch of things, right now i'm walking through macos mmio via my hypervisor and we deliberately don't write to rvbar#asahi-dev · 2026-05-14 04:25
StanfordAppliedCyber[m]_vectors_start#asahi-dev · 2026-05-14 04:13
StanfordAppliedCyber[m]i see the pmgr ack, pstate 0x1f0, mailbox bits cleared, and then they just don't execute rvbar#asahi-dev · 2026-05-14 03:30
StanfordAppliedCyber[m]they just.... refuse to execute rvbar#asahi-dev · 2026-05-14 03:01
StanfordAppliedCyber[m]ideally with everything i need already baked in and "it just works", it's possible i'm making a very stupid mistake somehow so i just want to minimize my odds of doing that#asahi-dev · 2026-05-14 02:57
StanfordAppliedCyber[m]i tried replaying quite literally every single macos mmio write and my cores refuse to turn on, going to keep probing, maybe my hardware is different, but "this definitely worked for other people" would be a helpful reference point#asahi-dev · 2026-05-14 02:56
StanfordAppliedCyber[m]does anyone have a branch that, for sure, successfully brings up smp on the neo that i can pull?#asahi-dev · 2026-05-14 02:46
StanfordAppliedCyber[m]it's exactly what it says it is-- generate a mask between the two bit indices#asahi-dev · 2026-05-14 02:46
StanfordAppliedCyber[m]but it literally just fills everything between the two values with 1#asahi-dev · 2026-05-14 02:46
StanfordAppliedCyber[m]first, i recommend using online resources to help answer questions about code :)#asahi-dev · 2026-05-14 02:42
StanfordAppliedCyber[m]same for rtkit, etc#asahi-dev · 2026-05-14 02:41
StanfordAppliedCyber[m]like, if the adt says spi is compatible, test that and see if it actaully works#asahi-dev · 2026-05-14 02:41
StanfordAppliedCyber[m]i'm not the person to talk to here, i just got involved about a week ago, but i think the easiest and obvious thing to do is just classify what works and what doesn't#asahi-dev · 2026-05-14 02:41
StanfordAppliedCyber[m]i'm working on a hypervisor for the a18 pro right now, it can't be merged as is because parts of it will have to be done as cleanroom docs#asahi-dev · 2026-05-14 02:26
StanfordAppliedCyber[m]without more detail on what you're trying to do it's hard to help you, but trust we are working hard on m4 support#asahi-dev · 2026-05-14 02:26
StanfordAppliedCyber[m]we dont support m4 yet#asahi-dev · 2026-05-14 00:03
StanfordAppliedCyber[m]I'm free to post mmio logs from my hypervisor here right? literally just read X bytes from address 0xf000 or whatever#asahi-dev · 2026-05-13 22:48
StanfordAppliedCyber[m]i mean the details of what changed#asahi-dev · 2026-05-13 22:47
StanfordAppliedCyber[m]ya know another option to the sptm emulation, that won't work on the neo because libt8140 isn't in the KDK, is to just see if you can compile your own xnu kernel and patch the old map_page stuff back in, the sptm really is just the old xnu map_page running in gl2 instead of el1#asahi-dev · 2026-05-13 22:42
StanfordAppliedCyber[m]if my nvme emulator is anything to go by then nvme definitely needs fixing (if you want details ask me in the RE channel)#asahi-dev · 2026-05-13 22:42
StanfordAppliedCyber[m]aic is v3 for sure#asahi-dev · 2026-05-13 06:17
StanfordAppliedCyber[m]......i just had the very obvious idea to use the hypervisor i've been building for the last week to watch macos and see what i'm doing wrong#asahi-dev · 2026-05-13 05:27
StanfordAppliedCyber[m]anyways, i need to take a break, there's a reasonable chance this all magically works tomorrow when i wake up and no one will know why#asahi-dev · 2026-05-13 05:26
StanfordAppliedCyber[m]the cpu cores just don't start#asahi-dev · 2026-05-13 05:26
StanfordAppliedCyber[m]tried popping a proxy shell and just running the correct writes and... yeah nothing#asahi-dev · 2026-05-13 05:25
StanfordAppliedCyber[m]i quite literally cloned your m1n1 repo, checked out the pmgr branch, merged the cyc fix, and flashed it in 1tr, and they all failed#asahi-dev · 2026-05-13 05:25
StanfordAppliedCyber[m]yes