#
…

2026-07-09

00:07hdbngr has joined #asahi-dev
00:09nela has quit [Ping timeout: 480 seconds]
00:16hdbngr has quit [Ping timeout: 480 seconds]
00:16nela has joined #asahi-dev
00:20nela has quit []
00:21nela has joined #asahi-dev
01:42hdbngr has joined #asahi-dev
01:42StanfordAppliedCyber[m]one of the big things my hypervisor adds is i patch the xnu commpage to convince userspace it's in a vm
01:42StanfordAppliedCyber[m]i'm not sure how to do this in an upstream friendly way
01:43StanfordAppliedCyber[m]some of the values can be controlled via boot args
01:43StanfordAppliedCyber[m]but some of them are hardcoded + inlined straight into the kernelcache
01:43StanfordAppliedCyber[m]ie, there's no switch to turn them off
01:43StanfordAppliedCyber[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
01:44StanfordAppliedCyber[m]i'm inclined to say that option 2 is more upstream friendly? as a bonus i think you can just pull the PA of the commpage straight from the SPTM emulator (just look for the RETYPE call)
01:44StanfordAppliedCyber[m]but wanted to get upstream feedback on this problem
01:47StanfordAppliedCyber[m]in particular if there's a third option i missed
01:50hdbngr has quit [Ping timeout: 480 seconds]
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:00ciara has quit [Remote host closed the connection]
02:13pb17 has quit [Ping timeout: 480 seconds]
02:13nela has quit [Quit: Ping timeout (120 seconds)]
02:13ciara has joined #asahi-dev
02:13nela has joined #asahi-dev
02:16pb17 has joined #asahi-dev
02:42ralim8 has quit [Quit: The Lounge - https://thelounge.chat]
02:43ralim8 has joined #asahi-dev
02:57hdbngr has joined #asahi-dev
03:06hdbngr has quit [Ping timeout: 480 seconds]
03:54nora has joined #asahi-dev
03:55nora_ has quit [Ping timeout: 480 seconds]
04:00hdbngr has joined #asahi-dev
04:07nela has quit [Ping timeout: 480 seconds]
04:10hdbngr has quit [Ping timeout: 480 seconds]
04:12nela has joined #asahi-dev
04:29nela has quit [Ping timeout: 480 seconds]
04:32nela has joined #asahi-dev
04:58hdbngr has joined #asahi-dev
05:08hdbngr has quit [Ping timeout: 480 seconds]
05:11starcatmeow has joined #asahi-dev
05:14mattia013 has joined #asahi-dev
05:15yukaI got the SError on trying to access DISP_CPU on t8132 too
05:16yukaon the same version which didn't do this before
05:17hdbngr has joined #asahi-dev
05:26hdbngr has quit [Ping timeout: 480 seconds]
05:54starcatmeow has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
05:56hdbngr has joined #asahi-dev
06:08hdbngr has quit [Ping timeout: 480 seconds]
06:09hdbngr has joined #asahi-dev
06:10svenremember how i was happy to fix that cursed secondary bringup bug?
06:11svenmaybe it's not usb that's cursed, maybe _I_ am cursed :D
06:12JamesCalligeros[m]Looks like multiple things trying to dump to stdout at once :p
06:13kaazoo has joined #asahi-dev
06:14yukaI've seen that before
06:14yukathe garbled exception handlers output
06:14kaazoo has quit []
06:14yukaI'm getting headaches from the dockchannel device tree layout
06:15cy8aer has quit [Remote host closed the connection]
06:16yukaI have a dockchannel-uart driver which works for tx / direct register access (so what we need for earlycon). Currently it is independent and has its own regs (pointing to the same as adt dockchannel-uart[0]).
06:16yukaNow I'm trying to come up with a way to have this driver run on the proposed upstream device trees.
06:17yukaBut it feels wrong to follow the mailbox link, assume the mailbox is a dockchannel device and read its regs.
06:17hdbngr has quit [Ping timeout: 480 seconds]
06:21ddxtanx_ has joined #asahi-dev
06:21ddxtanx has quit [Read error: Connection reset by peer]
06:25yukaintegralpilot: do you have a suggestion for how to handle this?
06:27svenyeah, it looks like multiple cores faulting at the same time for some reason
06:27svenjust dunno why
06:28cy8aer has joined #asahi-dev
06:28svenadding printfs around the core that stops the core ofc makes the jug go away 🙃
06:28sven*code
06:28mattia013 has quit [Quit: mattia013]
06:31hdbngr has joined #asahi-dev
06:38nela has quit [Quit: Ping timeout (120 seconds)]
06:39nela has joined #asahi-dev
06:40hdbngr has quit [Ping timeout: 480 seconds]
06:42svenit almost looks like the cores end up at RVBAR somehow
06:42svenFirst line looks like „OKRVBAR“ interleaved from N cores
06:42yukaCan you make the exception handler quiet on all cotes except one?
06:43yuka*cores
06:43svenyeh, im also gonna try to make them use different stacks
06:43svenif they really all end up at rvbar maybe due to the set wfe mode thingy they’re gonna clobber each other’s stack very quickly
06:44svenfirst $work though
06:44hdbngr has joined #asahi-dev
06:45pjv has joined #asahi-dev
06:47jannauyuka: I'm not convinced that we want dockchannel-uart over mailbox
06:53hdbngr has quit [Ping timeout: 480 seconds]
06:54NickChan[m]I have seen cores ending up at rvbar in m1n1 multiple times before it looks exactly like that
06:55NickChan[m]could happen if irq/fiq is not disabled in CYC_OVRD
06:58hdbngr has joined #asahi-dev
07:01pb17 has quit [Ping timeout: 480 seconds]
07:08hdbngr has quit [Ping timeout: 480 seconds]
07:09sveni think this happens when set_smp_wfe_mode runs but uhhhh… why do I start hitting this now?
07:14NickChan[m]make sure bit 0 in CYC_OVRD is cleared
07:34hdbngr has joined #asahi-dev
07:39pb17 has joined #asahi-dev
07:51pjv has quit [Ping timeout: 481 seconds]
07:57jmck has quit [Quit: Lost terminal]
08:40donaldh has quit [Ping timeout: 480 seconds]
08:43ddxtanx has joined #asahi-dev
08:43ddxtanx_ has quit [Read error: Connection reset by peer]
08:49yukaI don't really care if we do dockchannel-uart over mailbox or not, but ideally the device tree should describe the hardware without making assumptions about the implementation, which is really difficult in this case
08:51JamesCalligeros[m]Is it even possible cleanly? Either the uart references the mbox phandle, is a node of the mbox, or is its own secret third thing with the same registers as the mbox (will this even probe or complain that the region is already in use by the mbox)
09:18ddxtanx has quit [Quit: Konversation terminated!]
09:21ddxtanx has joined #asahi-dev
09:28pb17 has quit [Ping timeout: 480 seconds]
09:34pb17 has joined #asahi-dev
09:45hdbngr has quit [Ping timeout: 480 seconds]
09:52hdbngr has joined #asahi-dev
10:01hdbngr has quit [Ping timeout: 480 seconds]
10:04ddxtanx has quit [Ping timeout: 480 seconds]
10:08hdbngr has joined #asahi-dev
10:08truita has quit [Ping timeout: 480 seconds]
10:17hdbngr has quit [Ping timeout: 480 seconds]
10:17hdbngr has joined #asahi-dev
10:27ddxtanx has joined #asahi-dev
10:31ddxtanx has quit []
10:31ddxtanx has joined #asahi-dev
10:37ddxtanx_ has joined #asahi-dev
10:37ddxtanx has quit [Read error: Connection reset by peer]
10:42donaldh has joined #asahi-dev
10:50millefy144 has joined #asahi-dev
10:56millefy14 has quit [Ping timeout: 480 seconds]
10:56millefy144 is now known as millefy14
13:04truita has joined #asahi-dev
13:28hdbngr has quit [Ping timeout: 480 seconds]
13:36hdbngr has joined #asahi-dev
13:41qyliss has quit [Quit: bye]
13:44qyliss has joined #asahi-dev
13:44hdbngr has quit [Ping timeout: 480 seconds]
13:45hdbngr has joined #asahi-dev
14:01hdbngr has quit [Ping timeout: 480 seconds]
14:05hdbngr has joined #asahi-dev
14:14hdbngr has quit [Ping timeout: 480 seconds]
14:16hdbngr has joined #asahi-dev
14:27lederstrumpf has joined #asahi-dev
14:50hdbngr has quit [Ping timeout: 480 seconds]
14:58hdbngr has joined #asahi-dev
15:02chaos_princessm3max mics work, the admac diff is p.write32(0x2a8980028, 0x200000); p.write32(0x2a898002c, 0x200000)
15:04fl0_id_afkchaos_princess nice
15:13hdbngr has quit [Ping timeout: 480 seconds]
15:18hdbngr has joined #asahi-dev
15:20yukacould not find the sd card detection pin with smc_watcher.py
15:21yukais smc-pmu something entirely different than the other smc gpios?
15:21yukado we know how to read it?
15:23chaos_princessbtw, why are you looking for it?
15:23yukapcie power management
15:24chaos_princessyou want to power down the pcie link when the sdcard is ejected?
15:24yukamarcan mentioned it as an example of what a good device tree /driver architecture should be able to do
15:25yukaThe pcie reader is enabled on boot, probed, then shut down until an sd card is inserted
15:25yukathis needs to coordinate the sd card reader, pcie and smc/gpio drivers
15:25yukaSo modeling it well is difficult
15:27yukaI don't know if it actually makes sense from a stability / power draw reduction point of view, but it's a good use case to think about when adding the pwren stuff
15:28hdbngr has quit [Ping timeout: 480 seconds]
15:31chaos_princessi am not sure if this is a correct way, but try putting a tracer on nub-spmi0
15:32hdbngr has joined #asahi-dev
15:37yukaoh, true
15:40mattia013 has joined #asahi-dev
15:43hdbngr has quit [Ping timeout: 480 seconds]
15:51svenhuh, that's with getting the stack via MPIDR instead of that global var in start.S
15:51svenso somehow that wfe makes the cpus reappear at RVBAR
15:52hdbngr has joined #asahi-dev
16:00svenhuh, the secondaries have CYC_OVRD_DISABLE_WFI_RET set so i guess that's enough to somehow make them sometimes reach RVBAR again?1
16:01hdbngr has quit [Ping timeout: 480 seconds]
16:02chaos_princessthats the bit that makes them lose pc after wfi
16:03hardy94 has joined #asahi-dev
16:04sveni don't think so
16:04svenlook at e.g. deep_wfi in utils.c
16:04svenwe don't touch that bit there
16:04svencpuidle-apple.c also just does this: "orr x0, x0, #(3L << 24)\n"
16:05hdbngr has joined #asahi-dev
16:05sventhat's cpu_sleep
16:05svenwhich is different from deep_wfi
16:07chaos_princessdeep_wfi also ends up at rvbar?
16:08sventhen a call to smp_set_wfe_mode results in that weird thing from above
16:08sveni.e. they all end up at RVBAR
16:09sveni think what happens is that if we bring the cores down we set that bit and it's still set when we bring them up the next time
16:09svenso start secondaries -> stop secondaries -> start again -> set wfe mode and it all explodes
16:09chaos_princessthat would make sense then
16:11svenyup, on first boot of the secondaries the bit is clear, then if i do stop -> start that bit is still set
16:11sveni'll just clear it in chickens.c
16:14hdbngr has quit [Ping timeout: 480 seconds]
16:15hardy94 has quit [Quit: hardy94]
16:24hdbngr has joined #asahi-dev
16:25svenyup, it's stable now
16:26svenphew... i expected this bug to be much worse :-)
16:32hdbngr has quit [Ping timeout: 480 seconds]
16:35yukaI took a stab at finding the gpio to bypass the usb hub on the NEo
16:36yukano luck so far
16:37yukaOne of the following to assumptions is wrong: 1. toggling the gpio is enough to bypass the usb, 2. the gpio is one of gP?? on the SMC
16:37yuka* by pass the usb hub
16:37hdbngr has joined #asahi-dev
16:37yukathe way I currently test is using a new INIT_USB proxy command which has 5 seconds of delay built in
16:38yukaI start out in debugusb mode, enable/disable the gpio(s) via smccli
16:38yukathen run the INIT_USB command and quickly re-plug the usb cable
16:38yukathis pulls the port out of debugusb mode (I confirmed that this works in principle on a device without usb hub)
16:40yukaI should probably add a more specialized proxy command which is small enough to run over the broken/slow uart, takes a gpio name and state and toggles that gpio before turning on usb
16:40yukathe uart is too slow for smccli
16:41yukaAnd then write an automated test
16:41yukaI don't know yet how to tell which smc keys are gpios
16:46hdbngr has quit [Ping timeout: 480 seconds]
16:52Guest12749 has quit [Quit: Bridge terminating on SIGTERM]
16:52rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:54hdbngr has joined #asahi-dev
16:57rhysmdnz has joined #asahi-dev
16:58Guest12985 has joined #asahi-dev
17:01yukait's very possible some setup of the usb repeater over i2c is necessary
17:08hdbngr has quit [Ping timeout: 480 seconds]
17:08ansg191 has quit [Remote host closed the connection]
17:13ansg191 has joined #asahi-dev
17:16hdbngr has joined #asahi-dev
17:16jannaudo you reset the usb2 repeater?
17:16yukaAh, no
17:16yukabut I think the usb2 repeater was always present on the i2c bus?
17:17yukaonly the hub needed resetting?
17:17yukaor was it the opposite?
17:17yukaand what was the way to reset it again?
17:17yukayes, only the hub has a "function-reset"
17:19jannauah, I thought the repeater had a function-reset as well
17:20jannauon normal devices the eusb repeater is reset via atc to make hotplug work
17:24hdbngr has quit [Ping timeout: 480 seconds]
17:32hdbngr has joined #asahi-dev
17:47hdbngr has quit [Ping timeout: 480 seconds]
17:47jsk has joined #asahi-dev
17:48pb17 has quit [Ping timeout: 480 seconds]
17:49pb17 has joined #asahi-dev
17:55hdbngr has joined #asahi-dev
17:56jannauhow does github determine what ubuntu-latest is? In my repo it's resolute but in https://github.com/AsahiLinux/avd-fw it's noble
17:59chaos_princessupstream is not running on latest
17:59chaos_princessthe version is pinned there
18:01jannauoh, I completely missed that there is already a workflow
18:04hdbngr has quit [Ping timeout: 480 seconds]
18:07hdbngr has joined #asahi-dev
18:17jannauasahi-wip refreshed. I've merged avd and t6031 isp. bits/001-devicetree-m3 is gone. commits moved to bits/000-devicetree. yuka's m4 devicetrees are merged as well
18:17chaos_princessbtw, which m3 devices do you have
18:18jannauj504, j514s, j514c
18:19chaos_princessmind running the isp tracer on j504 and j514s and sending the logs (it will most likely crash, that is expected).
18:19hardy94 has joined #asahi-dev
18:21hardy94 has quit []
18:21jannauI can try but I do not have much luck with hv / macos, especially with tracers
18:22chaos_princesson c, --cpus=4 helps a lot
18:23svenhuh, is the hv still unstable on m3?
18:23chaos_princessyes, when running on >1 cpu
18:24chaos_princessbut i haven't pulled in your cache maintenance patches yet
18:25sventhat should only matter during smp bringup
18:25svenonce they’re up everything should be fine
18:25chaos_princesswell, that is why i haven't done it yet, don't see how it might be relevant
18:28svenwonder if there's another weird issue like that hiding somewhere in the hv code. i really don't want to debug another one like that though ;)
18:31jannauchaos_princess: tracer fails on j504 because dart-isp isn't powered on
18:34chaos_princesscan you just delete the self.dart_tracer.start() call for now?
18:35sofusyay for avd :p
18:36chaos_princessactually, wait, why is it powered off, there is a call to turn it on in tracer
18:37hdbngr has quit [Ping timeout: 480 seconds]
18:38jannaudart-isp has no clock/power-gates
18:39jannauon j504 and j514s
18:39hdbngr has joined #asahi-dev
18:48hdbngr has quit [Ping timeout: 480 seconds]
18:48jannaudart works after turning ISP_SYS manually on
18:57hdbngr has joined #asahi-dev
18:59balrog_ has joined #asahi-dev
19:02balrog has quit [Ping timeout: 480 seconds]
19:05jannauno luck with HV :(
19:06chaos_princessno tracer output at all?
19:07svenhow is it unstable? still weird crashes in random places?
19:09jannaupmgr related panics or early hangs
19:11hdbngr has quit [Ping timeout: 480 seconds]
19:15jannauwith cpus={4,6} get "panic(cpu 0 caller 0xfffffe00159a2a0c): "ApplePMGR: virtual void ApplePMGR::enableCPUComplex(UInt32, bool):4331 REQUIRE failed: complex < _cpuComplexCount" @ApplePMGR.cpp:4331"
19:17ddxtanx has joined #asahi-dev
19:17ddxtanx_ has quit [Read error: Connection reset by peer]
19:18hdbngr has joined #asahi-dev
19:30ddxtanx has quit [Quit: Konversation terminated!]
19:30ddxtanx has joined #asahi-dev
19:31yukaOkay I have dockchannel-uart earlycon (direct mmio, tx-only) and console= / ttyDC0 (mailbox, tx/rx) working :-)
19:32yukaexcept when I enable both at once, the handover goes wrong
19:32hdbngr has quit [Ping timeout: 480 seconds]
19:32yukaI think the earlycon still writes things to the fifo after mailbox has been initialized
19:34yukaTo make this not completely horrible, I duplicated the fifo reg on the mailbox and the uart node. Both earlycon and the normal uart driver use to the same dt node, but look at different properties (regs vs mboxes)
19:34yukaSo the earlycon would still work if the mbox was entirely missing, and the normal uart driver would still work if the regs were missing
19:34yukaand I hope this implementation doesn't draw an extra 10W
19:37sven10W, wtf
19:39ddxtanx_ has joined #asahi-dev
19:39ddxtanx has quit [Read error: Connection reset by peer]
19:40hdbngr has joined #asahi-dev
19:40yukathe previous thing I tested was busy looping somewhere
19:41yukaWhen there was nothing to be sent
19:45yukaI wonder if the mailbox-uart/tty-including-console-support part could be so generic that it isn't even apple-dockchannel specific
19:45yukalike you write a mailbox driver and get a uart/tty-including-console-support for free
19:48yukaeverything is a file
19:48yukaor something
19:48svenimho stuff can always be made generic later, i usually prefer to just make it work for us for now
19:49svenunless this sounds like fun ofc ;)
19:50chaos_princessi found that making stuff that is generic straight out of the gate tends to invite extra scrutiny on ml
19:50ddxtanx has joined #asahi-dev
19:50svenyeah, that too
19:51ddxtanx_ has quit [Read error: Connection reset by peer]
19:52hdbngr has quit [Remote host closed the connection]
19:52hdbngr has joined #asahi-dev
19:58svenonly suspicious thing i found in the hv code
19:59sventhat, uh, might just make every hv_rendezvous unreliable i think
20:01chaos_princessdoes the fact that we now boot on core 4 make it worse?
20:02svendon't think so
20:02svenessentially hv_rendezvous will return the moment it caught the boot cpu unless i'm missing something
20:03hdbngr has quit [Ping timeout: 480 seconds]
20:03svenit's gonna send an IPI to each and every cpu anyway so we may just be very lucky on M1/M2
20:03svenif they exit quickly enough they still meet, it's just that if they're too slow... well
20:04svenuh... or maybe i'm confused
20:05svenah.. i thinnk hv_exc.c may just fix this on the first exception anyway
20:05hdbngr has joined #asahi-dev
20:06svenyeah, hv_exc.c fixes this. so once each core went through at least one exception that hit hv_exc_entry everything's fine
20:09nela has quit [Ping timeout: 480 seconds]
20:11nela has joined #asahi-dev
20:14hdbngr has quit [Ping timeout: 480 seconds]
20:15hdbngr has joined #asahi-dev
20:23hdbngr has quit [Ping timeout: 480 seconds]
20:26StanfordAppliedCyber[m]upstreamable hypervisor works!
20:26StanfordAppliedCyber[m]need to write some commit messages, add some comments, then it's PR time
20:31pb17 has quit [Ping timeout: 480 seconds]
20:31hdbngr has joined #asahi-dev
20:36amarioguy has quit [Ping timeout: 480 seconds]
20:41Sobek[m](Hmm, including the SPTM thing, or excluding the SPTM thing ?)
20:49hdbngr has quit [Ping timeout: 480 seconds]
20:58hdbngr has joined #asahi-dev
21:05StanfordAppliedCyber[m]so unfortunately not immediately usable by anyone who isnt me
21:06StanfordAppliedCyber[m]yuka previously said she can clean room the emulator, tbh it's really not that bad, the docs i'm writing are quite nice nd most of the custom code is isolated to a single table
21:06StanfordAppliedCyber[m]also can i solicit maintainer feedback on something else?
21:06StanfordAppliedCyber[m]tl;dr sme is causing issues
21:07StanfordAppliedCyber[m]there appear to be a set of registers related to SME that are used on thread context switch thar are not writable from el1
21:08StanfordAppliedCyber[m]by default, accessing the registers causes SIGILL and a trap to xnu's own sigill handler
21:08StanfordAppliedCyber[m]access from el2 works fine
21:09StanfordAppliedCyber[m]so the obvious example i thought was to just replay the access in el2, but because it hits xnu's own exception handler we don't have visibility into what's going on
21:09hdbngr has quit [Ping timeout: 480 seconds]
21:09chaos_princessis it trying to touch amx
21:09StanfordAppliedCyber[m]right now i'm literally just disabling sme by tossing bits in the arm architectural registers
21:09StanfordAppliedCyber[m]everything is fully supported
21:09StanfordAppliedCyber[m]it's just an el1 vs el2 issue
21:10chaos_princesscan you give an example of a reg
21:10pb17 has joined #asahi-dev
21:10chaos_princesstbh, just turn sme off, i don't think we care
21:11StanfordAppliedCyber[m]yeah that's what i do
21:11StanfordAppliedCyber[m]example reg is CAPCR_EL1
21:11ddxtanx has quit [Read error: Connection reset by peer]
21:11StanfordAppliedCyber[m]looking at these actually i think the context switch ones may work in el1
21:11ddxtanx has joined #asahi-dev
21:11StanfordAppliedCyber[m]the initial configuration definitely needs el2
21:11StanfordAppliedCyber[m]SMPRIMAP_EL2 is the register that first caused the problem to manifest
21:12StanfordAppliedCyber[m]the issue with just disabling sme though is you have to add a lot of other code, because xnu reads arm architectural registers
21:12chaos_princesswhats it writing to CPACR_EL1
21:12StanfordAppliedCyber[m]so you have to fake those register values, which is annoying because macos accesses them a LOT, so you have to move sysreg handling to C
21:12hdbngr has joined #asahi-dev
21:13StanfordAppliedCyber[m]i cant physically touch the mac rn (rdp session) but i can figure that out if it'd be helpful
21:13chaos_princessi am reading the arm arm and there are very obvious reasons listed out why this one might trap
21:21hdbngr has quit [Ping timeout: 480 seconds]
21:29hdbngr has joined #asahi-dev
21:32madmatt067 has quit [Quit: .]
21:36yurix has quit [Read error: Connection reset by peer]
21:36madmatt067 has joined #asahi-dev
21:36madmatt067 has quit []
21:38yurix has joined #asahi-dev
21:41hdbngr has quit [Ping timeout: 480 seconds]
21:42hdbngr has joined #asahi-dev
21:46hardy94 has joined #asahi-dev
21:51hdbngr has quit [Ping timeout: 480 seconds]
21:52ddxtanx has quit [Read error: Connection reset by peer]
21:52ddxtanx has joined #asahi-dev
21:58yurix has quit [Ping timeout: 480 seconds]
21:58hdbngr has joined #asahi-dev
21:59hardy94 has quit [Remote host closed the connection]
22:02chadmed has quit [Quit: Konversation terminated!]
22:03yurix has joined #asahi-dev
22:05revadam has joined #asahi-dev
22:06revadam has quit []
22:13hdbngr has quit [Ping timeout: 480 seconds]
22:17StanfordAppliedCyber[m]yeah i got regular trapping to work
22:20delinka has joined #asahi-dev
22:21hdbngr has joined #asahi-dev
22:23madmatt067 has joined #asahi-dev
22:24pb17 has quit [Ping timeout: 480 seconds]
22:32hdbngr has quit [Remote host closed the connection]
22:32hdbngr has joined #asahi-dev
22:34pb17 has joined #asahi-dev
22:37madmatt067 has quit [Quit: .]
22:40hdbngr has quit [Ping timeout: 480 seconds]
22:43hdbngr has joined #asahi-dev
22:46madmatt067 has joined #asahi-dev
22:48madmatt067 has quit []
22:50hdbngr has quit [Remote host closed the connection]
23:02gatallah has joined #asahi-dev
23:05gatallah has quit [Remote host closed the connection]
23:22StanfordAppliedCyber[m]initial PR is going to have hardcoded addresses for the commpage fixes
23:22StanfordAppliedCyber[m]we'll need to figure out the right shape for this
23:23maettu102 has quit [Quit: brb]
23:29maettu102 has joined #asahi-dev
23:49StanfordAppliedCyber[m]i'm surprised how reliable this is, unlike m3 i don't get any nondeterminism at all in the upstreamable branch. the old version had some problems (mostly timing related) but i haven't hit a single flake in the branch i'm upstreaming
23:52delinka has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
…