#asahi-dev · 2026-07-09 01:43
StanfordAppliedCyber[m]so the options I see are: 1. patch the kernelcache text directly (what I currently do, ugly af, hardcoded addresses, disasm for every new kernel) or 2. patch it in memory#asahi-dev · 2026-07-09 01:43
StanfordAppliedCyber[m]ie, there's no switch to turn them off#asahi-dev · 2026-07-09 01:43
StanfordAppliedCyber[m]but some of them are hardcoded + inlined straight into the kernelcache#asahi-dev · 2026-07-09 01:43
StanfordAppliedCyber[m]some of the values can be controlled via boot args#asahi-dev · 2026-07-09 01:42
StanfordAppliedCyber[m]i'm not sure how to do this in an upstream friendly way#asahi-dev · 2026-07-09 01:42
StanfordAppliedCyber[m]one of the big things my hypervisor adds is i patch the xnu commpage to convince userspace it's in a vm#asahi-dev · 2026-07-08 23:49
StanfordAppliedCyber[m]currently refactoring my entire HV (minus the sptm emulator) to be upstreamable with the standard utilities#asahi-dev · 2026-07-08 21:39
StanfordAppliedCyber[m]the standard hv dev process is chainload a new m1n1 image then run the default entrypoint and send the kernelcache over the wire right?#asahi-dev · 2026-07-08 08:49
StanfordAppliedCyber[m]woah#asahi-dev · 2026-07-08 08:49
StanfordAppliedCyber[m]we have 80k users?#asahi-dev · 2026-07-08 08:48
StanfordAppliedCyber[m]anyways time to sleep at a reasonable hour for once#asahi-dev · 2026-07-08 08:48
StanfordAppliedCyber[m]the hypervsior pr will need a lot of massaging before it can be upstreamed, but that's a problem we can work through and come with with solutions that everyone can be happy about#asahi-dev · 2026-07-08 08:48
StanfordAppliedCyber[m]i'm about 70% of the way writing cleanroom docs on my emulator already#asahi-dev · 2026-07-08 08:47
StanfordAppliedCyber[m]knock wood i can get a hypervisor PR out in a few days#asahi-dev · 2026-07-08 08:47
StanfordAppliedCyber[m]apparently otherwise the dcp causes a lot of problems for reasons we don't quite understand, but also do not care about#asahi-dev · 2026-07-08 08:46
StanfordAppliedCyber[m]i had to set nodisplay#asahi-dev · 2026-07-08 08:46
StanfordAppliedCyber[m]with yuka's help i have successfully gotten debugusb to work on the neo#asahi-dev · 2026-07-08 08:15
StanfordAppliedCyber[m]pmgr says they started but they don't execute our code#asahi-dev · 2026-07-08 08:15
StanfordAppliedCyber[m]yeah same symptom as my macbook neo#asahi-dev · 2026-07-08 07:56
StanfordAppliedCyber[m]smp is broken as in you do the cpustart write and nothing happens?#asahi-dev · 2026-07-07 23:28
StanfordAppliedCyber[m]or virtualize sptm, idrc, i think it's a higher risk approach but how yall get it to work it doesn't matter to me#asahi-dev · 2026-07-07 23:27
StanfordAppliedCyber[m]i think the emulator should be ~2k lines of code, my implementation is about 6k but that's because i chose not to reuse any of m1n1's utilities for the iommus#asahi-dev · 2026-07-07 23:27
StanfordAppliedCyber[m]from there if you care i can get whatever logs/traces/whatever from my emulator that you could ever want for a clean room re project#asahi-dev · 2026-07-07 23:26
StanfordAppliedCyber[m]dw once debugusb works i'll have it in upstreamable shape within a few days#asahi-dev · 2026-07-07 23:26
StanfordAppliedCyber[m]and given you volunteered to help me upstream this by clean rooming the tainted bits I REALLY do not want to taint you by accident#asahi-dev · 2026-07-07 23:25
StanfordAppliedCyber[m]i'm worried about tainting you there,s because i can't just ship you a binary because about half the emulator is in python#asahi-dev · 2026-07-07 23:24
StanfordAppliedCyber[m]my hv?#asahi-dev · 2026-07-07 23:24
StanfordAppliedCyber[m]give what a try?#asahi-dev · 2026-07-07 23:24
StanfordAppliedCyber[m]since for linux dev i'm planning on doin g the stream the kernel over debugusb thing#asahi-dev · 2026-07-07 23:24
StanfordAppliedCyber[m]re: hypervisor, i think the real accomplishment would be someone else successfully boooting macos under the hv#asahi-dev · 2026-07-07 23:23
StanfordAppliedCyber[m]the main blocker for that, debugusb working, is also the blocker for linux dev#asahi-dev · 2026-07-07 23:23
StanfordAppliedCyber[m]oh yeah upstreaming the hypervisor is what i'm currently working on#asahi-dev · 2026-07-07 23:01
StanfordAppliedCyber[m]i think i'm the poster child for smp boot instability lol#asahi-dev · 2026-07-07 22:47
StanfordAppliedCyber[m]what's the best place to find that? asahi-wip?#asahi-dev · 2026-07-07 22:47
StanfordAppliedCyber[m]i assume step 1 is to figure out what parts alrady work, ie, iirc yuka found that pcie is basically unchanged#asahi-dev · 2026-07-07 22:43
StanfordAppliedCyber[m]by usb does usb2 work or do we need usb3 for release#asahi-dev · 2026-07-07 22:42
StanfordAppliedCyber[m]i'll try to do those#asahi-dev · 2026-07-07 22:42
StanfordAppliedCyber[m]no promises but yeah i'll do those#asahi-dev · 2026-07-07 22:42
StanfordAppliedCyber[m]m3 is close to being there right?#asahi-dev · 2026-07-07 22:42
StanfordAppliedCyber[m]yeah that's fair#asahi-dev · 2026-07-07 22:40
StanfordAppliedCyber[m]maybe after actually trying i will indeed be convinced lol#asahi-dev · 2026-07-07 22:39
StanfordAppliedCyber[m]again, perhaps i'm hopelessly naive, but i'm not yet convinced of that#asahi-dev · 2026-07-07 22:39
StanfordAppliedCyber[m]the first target is a working system without gpu acceleration, which i'll define as screen, keyboard, trackpad, wifi, and maybe some form of usb#asahi-dev · 2026-07-07 22:38
StanfordAppliedCyber[m]but i like working on multiple things in parallel#asahi-dev · 2026-07-07 22:38
StanfordAppliedCyber[m]yeah i was gonna do the others first#asahi-dev · 2026-07-07 22:34
StanfordAppliedCyber[m]what would prevent 26.6 from working? i assume wfi is never going to be properly resolved but we're building that solution right now#asahi-dev · 2026-07-07 22:33
StanfordAppliedCyber[m]the only downside i can think of is the lack of tso but there's a decently high chance apple never enables it#asahi-dev · 2026-07-07 22:32
StanfordAppliedCyber[m]asking because i'm going to start poking the gpu firmware abi and i don't want the effort to be wasted if we support another version#asahi-dev · 2026-07-07 22:32
StanfordAppliedCyber[m]fine*#asahi-dev · 2026-07-07 22:32
StanfordAppliedCyber[m]are we find to target 26.6 for the official asahi linux release on m4/a18 pro?