#asahi-re · 2026-09-09 20:24
yukado you think this is related to https://en.wikipedia.org/wiki/ARM_Cortex-X1#asahi-re · 2026-09-09 20:19
yukabut the kernel was already arm64e iirc? At least when linking kexts there were some errors regarding that#asahi-re · 2026-09-09 19:33
yukamaybe they started shipping some of the ML models in the ipsw#asahi-re · 2026-07-30 09:16
yukaand if there's a chicken bit, we probably can't change it#asahi-re · 2026-07-30 09:14
yukajannau: m5pro ID_AA64MMFR4_EL1: 0x0 (https://termbin.com/ki1q)#asahi-re · 2026-07-22 05:45
yukathat paper also says GL1#asahi-re · 2026-07-22 05:44
yukaGL1 or GL0 would make more sense, if it's running "under SPTM"#asahi-re · 2026-07-22 05:44
yukaare you sure exclavecore runs in GL2?#asahi-re · 2026-07-22 05:34
yukahttps://arxiv.org/pdf/2510.09272#asahi-re · 2026-07-22 05:34
yukahttps://www.theregister.com/security/2025/03/08/how-apple-rearranged-its-xnu-kernel-with-security-exclaves/1352740#asahi-re · 2026-07-22 05:26
yukaIs there one for M4+?#asahi-re · 2026-07-22 05:07
yukawhat does "sptm managed" mean?#asahi-re · 2026-07-21 19:55
yukaAhh fair#asahi-re · 2026-07-21 19:49
yukaor does SPTM not allow setting up the pagetables that way#asahi-re · 2026-07-21 19:49
yukais that just how macOS does it, or does the normal EL2/EL1 separation just not work?#asahi-re · 2026-07-21 19:45
yukaI don't know if the SPTM guest can even have its own guests, or if everything virtualization shaped needs to go via SPTM#asahi-re · 2026-07-21 19:38
yukayeah, so it would be nice if someone had a closer look at that boot mode, but it's probably not an easy task#asahi-re · 2026-07-21 19:37
yukaor even get m1n1 running fully#asahi-re · 2026-07-21 19:37
yukaI haven't verified any of this, but if you actually run under SPTM it might be very annoying to even get debug output in any way#asahi-re · 2026-07-21 19:36
yukabecause that's pretty much how you install m1n1 nowadays, and the assumption is if you attempted to install the macho version on recent platforms you would be dropped into an environment running under SPTM#asahi-re · 2026-07-21 19:36
yukaI assume you have been doing the raw boot object path#asahi-re · 2026-07-21 19:32
yukathere is a lot of reasons to assume this is an iboot bug, though it is somewhat difficult to prove (but your analysis with reading pc of the secondary cores kinda supports it)#asahi-re · 2026-07-21 19:31
yukadj: for context, on the base M4 model there was also specific macOS/iboot versions which had broken smp (possibly in a similar way) and then it worked again just like that after one with 26.x updates#asahi-re · 2026-07-21 19:30
yukawhat is locked where is a bit unknown, but things are definitely locked down a lot#asahi-re · 2026-07-21 19:30
yukaright#asahi-re · 2026-07-21 19:29
yuka*or with the non-raw / macho kernel objects on M4+#asahi-re · 2026-07-21 19:29
yukaI personally haven't verified if this is also the case when using a newer iboot (one from an SPTM-enabled build) on an M3 device, or with the non-raw / macho kernel objects#asahi-re · 2026-07-21 19:28
yukathere are things which are known to be locked (though not under which specific conditions?), like pretty much all apple specific imp regs / msrs on the usual setup (install raw boot object via kmutil -r) on M4#asahi-re · 2026-07-21 19:27
yuka> <sven> and the fuos path needs to somehow lock down all sysregs, etc.#asahi-re · 2026-07-21 19:27
yuka> <chaos_princess> it is unlikely that you will succeed. the relevant bits are in iboot, and you can't change it#asahi-re · 2026-07-21 19:26
yukaas people have been telling you, we would all expect this stuff to be locked down in your device/setup#asahi-re · 2026-07-21 19:24
yukachainloading another m1n1 shouldn't affect privileges in any way, but I suspect you mean something else?#asahi-re · 2026-07-21 14:07
yukadj: if you can figure out what the impact of the individual init things are (x makes y writable), having documentation of this would be amazing#asahi-re · 2026-07-21 07:31
yukahttps://github.com/AsahiLinux/m1n1/pull/633#asahi-re · 2026-07-21 06:56
yukat8142 pcie reg layout looks close enough that it could#asahi-re · 2026-07-21 06:52
yukaI would also like someone to check if the same works for t8142#asahi-re · 2026-07-21 06:51
yukaSo I request permission to publish the code change for that directly#asahi-re · 2026-07-21 06:50
yukaAccording to the RE policy the code I have locally is derived from binary RE and someone else should write it again from the information I documented here, but I find it a bit laughable since I narrowed it down to this trivial change.#asahi-re · 2026-07-21 06:50
yukaSo I figured out yesterday, with knowledge gained from binary RE, how to initialize the pcie on t8132/t6040. The main info needed is APCIE_PHY_CTRL_RESET BIT(7) => BIT(4).#asahi-re · 2026-07-21 06:36
yukafirst assumption should be that something is not yet initialized/enabled when getting an SError#asahi-re · 2026-07-21 06:36
yukabut in general, yes#asahi-re · 2026-07-21 06:35
yukait's not that unlikely that they also disable some of the cpu controls that way#asahi-re · 2026-07-21 06:35
yukaexactly :p#asahi-re · 2026-07-21 06:35
yukaexactly#asahi-re · 2026-07-21 06:34
yukaas if there's a list of disallowed regions somewhere#asahi-re · 2026-07-21 06:34
yukathat seems indeed like a """Filter""" for for mmio#asahi-re · 2026-07-21 06:34
yukawhile others work fine#asahi-re · 2026-07-21 06:34
yukathey just serror when you read them#asahi-re · 2026-07-21 06:34
yukaor some specific pinctrl gpios