#asahi-re · 2022-02-04 15:58
phireits' not valid#asahi-re · 2022-02-04 15:58
alyssawhat's at the pointer?#asahi-re · 2022-02-04 15:57
phireor pointers to some kind of task structure that has all the deatils#asahi-re · 2022-02-04 15:56
phiremy theory is that these are command buffer pointers#asahi-re · 2022-02-04 15:55
phireI see it following a pattern of writing what looks like a pointer (like 0x1506f90000), then a size (0x14000), then setting a flag (to signal work is ready)#asahi-re · 2022-02-04 15:46
phireI think the cpu only ever writes into gfx-handoff#asahi-re · 2022-02-04 15:43
alyssaCould be, yeah#asahi-re · 2022-02-04 15:42
phireI think it's data belonging to the firmware#asahi-re · 2022-02-04 15:41
phirehowever... the cpu didn't write into it#asahi-re · 2022-02-04 15:40
phirenope, it's clear at boot#asahi-re · 2022-02-04 15:39
alyssapossible#asahi-re · 2022-02-04 15:39
phireum, let me just check this isn't just stale data from iboot#asahi-re · 2022-02-04 15:39
alyssanod#asahi-re · 2022-02-04 15:36
phireimplies something has direct access to physical memory#asahi-re · 2022-02-04 15:35
phirethe fact that I'm seeing physical pointers in this gfx-shared-region is interesting#asahi-re · 2022-02-04 15:34
phirenot sure I want to go much beyond looking at strings RE wise#asahi-re · 2022-02-04 15:33
alyssagive getGartPhysicalBaseAddress a looksies#asahi-re · 2022-02-04 15:32
alyssamaybe it's time to pop open ghidra/ida#asahi-re · 2022-02-04 15:32
alyssaHm#asahi-re · 2022-02-04 15:32
phireand doesn't look virtual#asahi-re · 2022-02-04 15:32
phireit's outside of physical memory#asahi-re · 2022-02-04 15:30
alyssaIncidentally, strings implies that AVE uses a GART too#asahi-re · 2022-02-04 15:30
alyssa(0x4061e4440 or something)#asahi-re · 2022-02-04 15:29
alyssano chance any of those are tagged pointers?#asahi-re · 2022-02-04 15:24
phireit's only bits 16-23 that change#asahi-re · 2022-02-04 15:23
phirefew hundred 64bit values with slight increments between them#asahi-re · 2022-02-04 15:23
phiresecond points to a table with data like: 0x00600004061e0447, 0x00600004061e4447, 0x00600004061e8447...#asahi-re · 2022-02-04 15:21
alyssawomp womp#asahi-re · 2022-02-04 15:20
phirefirst pointer points to nulls#asahi-re · 2022-02-04 15:20
phirestuff that doesn't seem to be that interesting at a first glance#asahi-re · 2022-02-04 15:19
alyssa?#asahi-re · 2022-02-04 15:18
alyssaand what's pointed to at that address & ~0x3#asahi-re · 2022-02-04 15:18
svenin the DART PTEs the lowest two bits are used for that#asahi-re · 2022-02-04 15:18
alyssasure#asahi-re · 2022-02-04 15:17
svencould be kind of valid bit(s)#asahi-re · 2022-02-04 15:15
phireor 0x1#asahi-re · 2022-02-04 15:15
phireyeah, it's always 0x3#asahi-re · 2022-02-04 15:15
alyssaarm definitely does#asahi-re · 2022-02-04 15:15
alyssai don't remember if apple does that, i think they do#asahi-re · 2022-02-04 15:15
alyssaunaligned pointers can sometimes be aligned pointers with extra data shoved in the bottom (and sometimes top) bits#asahi-re · 2022-02-04 14:59
phirethey are also all unaligned#asahi-re · 2022-02-04 14:56
phireoh hang on, the pointers witten to gfx-shared-region-base actually point at real physical memory#asahi-re · 2022-02-04 14:51
phireThere is very little data sent via the ASC interface. It basically looks like little more than a keepalive#asahi-re · 2022-02-04 14:44
phireThat's where I'm getting these "pointers" that I don't know where they point to#asahi-re · 2022-02-04 14:43
phireyes#asahi-re · 2022-02-04 14:42
alyssaor how does that work#asahi-re · 2022-02-04 14:42
alyssaphire: are u tracing the *-region/handoff-base memory?#asahi-re · 2022-02-04 14:40
phireno, that only has the expected asc traffic #asahi-re · 2022-02-04 14:31
phiremaybe it's on the agx-asc node's registers#asahi-re · 2022-02-04 14:04
phireyeah, I think it does