#
✕ nick:StanfordAppliedCyber[m]
#asahi-dev · 2026-06-03 21:15
StanfordAppliedCyber[m]also wanted to ask about a specific edge case-- we have to pass a big struct to xnu containing information about sptm, memory mappings, a bunch of other stuff
#asahi-dev · 2026-06-03 21:06
StanfordAppliedCyber[m]not to mention i figured the risk is extremely low-- even if the traces end up just confirming what we know about dart, it's functionally just the same as looking at an m1n1 hv trace and doesn't taint the people working on it
#asahi-dev · 2026-06-03 21:03
StanfordAppliedCyber[m]this may be a theoretical barrier, maybe yuka or others are just better devs than me and can get it working just with the high level overview, but my expectation is that with a runtime trace resolving some of these edge cases will be extremely difficult if not impossible
#asahi-dev · 2026-06-03 21:02
StanfordAppliedCyber[m]there's a reason i'm not using the m1n1 code as it is currently
#asahi-dev · 2026-06-03 21:01
StanfordAppliedCyber[m]re: traces, the thing that concerns me is that there's a lot of edge case behavior that in some cases took me days/weeks to get to the bottom of because the failure symptoms were so far removed from the actual root cause
#asahi-dev · 2026-06-03 21:01
StanfordAppliedCyber[m]sven: thanks for the advice here!
#asahi-dev · 2026-06-03 11:18
StanfordAppliedCyber[m]yeah i expected that much, but i'm hoping it's just added/removed some fields, not oh hey we just totally changed the way the whole interface works
#asahi-dev · 2026-06-03 11:17
StanfordAppliedCyber[m]oh it's quite different? unfortunate, i was hoping it'd be similar, but this is apple so i knew better than to expect
#asahi-dev · 2026-06-03 11:16
StanfordAppliedCyber[m]this is in reply to my 3 part plan? or to yuka's question
#asahi-dev · 2026-06-03 11:14
StanfordAppliedCyber[m]i'm hoping it's not obviously, but at minimum initdata will need some fixes
#asahi-dev · 2026-06-03 11:14
StanfordAppliedCyber[m]but that's what i want to check :)
#asahi-dev · 2026-06-03 11:14
StanfordAppliedCyber[m]no clue
#asahi-dev · 2026-06-03 11:09
StanfordAppliedCyber[m]also in the meantime i'm very interested in the gpu and i assume i'm free to use the hypervsior to start REing the firmware interface? i've never disassembled any of the gpu kexts or firmware and am totally untainted
#asahi-dev · 2026-06-03 11:03
StanfordAppliedCyber[m]not to mention that sptm is a very ornery piece of software that is pretty much always unhappy in my experience
#asahi-dev · 2026-06-03 11:03
StanfordAppliedCyber[m]s/say/think/, s/viable/promising/, s/forward//
#asahi-dev · 2026-06-03 11:02
StanfordAppliedCyber[m]by contrast, on our own custom emulator, we can inspect state and then this becomes a lot easier, and i think supporting exclaves is absolutely something we want to do eventually because apple is going to keep putting more stuff in them and it'll likely be required to fully trace the hardware
#asahi-dev · 2026-06-03 11:01
StanfordAppliedCyber[m]i say this is the most viable path forward btw because if we take the "just run sptm in a VM, proxy requests" option i think we're going to hit a LOT of issues, none of which are fundamentally unsolvable, but would delay progress by months if not years. it would also make exclaves way harder because sptm is responsible for organizing the shared memory between exclaves and xnu
#asahi-dev · 2026-06-03 11:00
StanfordAppliedCyber[m]is this a viable path forward?
#asahi-dev · 2026-06-03 10:59
StanfordAppliedCyber[m]yuka has volunteered to do the clean room RE work
#asahi-dev · 2026-06-03 10:57
StanfordAppliedCyber[m]literally just:... (full message at <https://matrix.org/oftc/media/v1/media/download/AYYzAOtCaNonclsiuno_tZ5d9TqV7v2ErCcbOhrtr9iOi0rhI_UkYmJhzP-0H8OIwsOZbeskc6GOZbEj6yYtsQJCee1TsWJwAG1hdHJpeC5vcmcvZ1JaZFN3SFZDUUVIamtkcXJFSVBPY3Rn>)
#asahi-dev · 2026-06-03 10:56
StanfordAppliedCyber[m]3. a runtime trace from my emulator just describing inputs and outputs
#asahi-dev · 2026-06-03 10:56
StanfordAppliedCyber[m]2. clean room docs on how sptm works that i'm very careful to ensure don't include tainted info
#asahi-dev · 2026-06-03 10:55
StanfordAppliedCyber[m]1. upstream, myself, all the hypervisor stuff that does NOT involve sptm. this is my own code, where i own the copyright, there's some timer stuff that comes to mind
#asahi-dev · 2026-06-03 10:55
StanfordAppliedCyber[m]basically, my current plan is the following things:
#asahi-dev · 2026-06-03 10:54
StanfordAppliedCyber[m]i'm at the point where i really need to think about how to upstream the sptm emulator because i'm 100% certain this is going to work and i think is the best option, looking for some maintainer input here
#asahi-dev · 2026-06-01 23:03
StanfordAppliedCyber[m]s/with/side/
#asahi-dev · 2026-06-01 23:03
StanfordAppliedCyber[m]and yeha you just install a second macos container in permissive security along with the first one
#asahi-dev · 2026-06-01 23:02
StanfordAppliedCyber[m]paulwalker: how much systems background do you have? tl;dr step 1 is get m1n1 up and running, with a nice usb stack (ie the full usb2 speed) and try to upstream whatever you have to to get it working
#asahi-dev · 2026-06-01 22:39
StanfordAppliedCyber[m]still some issues, macos immediately rebooted into recovery, but progress
#asahi-dev · 2026-06-01 22:37
StanfordAppliedCyber[m]WE'RE IN USERSPACE!
#asahi-dev · 2026-05-28 20:39
StanfordAppliedCyber[m]oh btw yuka if traces would help lmk, more than happy to assist
#asahi-dev · 2026-05-28 07:22
StanfordAppliedCyber[m]not to mention every other SPTM enabled device
#asahi-dev · 2026-05-28 07:19
StanfordAppliedCyber[m]i'm almost to userspace
#asahi-dev · 2026-05-28 07:18
StanfordAppliedCyber[m]also i'm doing a bunch of dev work on the macbook neo right now, tl;dr i'm trying to port the m1n1 hypervisor to the macbook neo by emulating SPTM. my emulator is tainted and thus can't be upstreamed (with the exception of the UAT endpoints which are completely clean) but i'm committed to writing very nice clean room docs and finding a way to get it upstreamed so that others can start REing the neo
#asahi-dev · 2026-05-28 07:16
StanfordAppliedCyber[m]specifically the macvdmtool readme
#asahi-dev · 2026-05-28 07:16
StanfordAppliedCyber[m]..........I don't want to be mean but please RTFM
#asahi-dev · 2026-05-28 07:14
StanfordAppliedCyber[m]it's a pain, and you need another apple silcion mac and a very nice usb cable
#asahi-dev · 2026-05-28 07:14
StanfordAppliedCyber[m]yeah i did
#asahi-dev · 2026-05-27 21:43
StanfordAppliedCyber[m]one consequence of this is that the emulator will only work for one macos version-- not too different from the previous hypervisor, but new devices will require more bringup work than previously because of it assuming this is the method we converge to for m1n1 hypervisor
#asahi-dev · 2026-05-27 21:42
StanfordAppliedCyber[m]facepalm
#asahi-dev · 2026-05-27 21:41
StanfordAppliedCyber[m]i was using an old firmware revision by accident
#asahi-dev · 2026-05-27 21:41
StanfordAppliedCyber[m]....well i found the source of the problem i had earlier, tl;dr 26.5 changed literally every dart endpoint from 26.4.1
#asahi-dev · 2026-05-26 19:48
StanfordAppliedCyber[m]ie, i had to fix a lot of timer stuff in the hypervisor to support 26.5, not to mention a bunch of sysregs
#asahi-dev · 2026-05-26 19:48
StanfordAppliedCyber[m]unfortunately i'm not sure if it's sptm emulation related or other stuff related
#asahi-dev · 2026-05-26 19:47
StanfordAppliedCyber[m]i suppose i'll check again
#asahi-dev · 2026-05-26 19:46
StanfordAppliedCyber[m]yeah, trust me that's the first thing i did
#asahi-dev · 2026-05-26 19:30
StanfordAppliedCyber[m]i'm willing to put in the work but it's clear that on this one i'm out of my depth
#asahi-dev · 2026-05-26 19:30
StanfordAppliedCyber[m]magical opaque hardware fabric between the reported error and the thing causing the error
#asahi-dev · 2026-05-26 19:29
StanfordAppliedCyber[m]i've made essentially 0 progress in a week because i'm not sure how to debug this
#asahi-dev · 2026-05-26 19:29
StanfordAppliedCyber[m]this is the same panic i posted two days ago

plus ›