ChanServ changed the topic of #asahi-gpu to: Asahi Linux: porting Linux to Apple Silicon macs | GPU / 3D graphics stack black-box RE and development (NO binary reversing) | Keep things on topic | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-gpu
anuejn has joined #asahi-gpu
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-gpu
yuyichao has quit [Ping timeout: 480 seconds]
kylealanhale has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-gpu
robinp has quit [Ping timeout: 480 seconds]
m6wiq has joined #asahi-gpu
chadmed has quit [Remote host closed the connection]
jakebot has quit [Read error: Connection reset by peer]
jakebot has joined #asahi-gpu
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-gpu
Ph03n1ks has quit [Remote host closed the connection]
alyssa has joined #asahi-gpu
<alyssa>
I think I want to tackle the context switching issues today
<alyssa>
Not streaming, too much pressure
<alyssa>
I just want this bug fixed because it's been killing my motivation to work on this driver
<Sobek[m]>
What’s that issue exactly ? Well best luck (and I wouldn’t be able to stream my daily dev, so I won’t be offended at all if you keep your dev to yourself).
<alyssa>
Sometimes -- depending on the GPU time elapsed and the GPU workload elsewhere on the system -- the system (macOS kernel or AGX firmware) decides to context switch the GPU.
<alyssa>
Preempting our rendering and restoring it later
<alyssa>
This mechanism is broken with Metal -- it never restores (or maybe never saves state when preempted)
<alyssa>
I don't know why, and it means that the driver randomly stops working
m6wiq has quit []
<Sobek[m]>
So normal processes end up detecting that they’ve been context switched and re-set up their pipeline ? Is it possible to observe the way the apple driver handles it ?
<Sobek[m]>
(I could see a few solutions / explanations as someone with no clue about the system 1. Normal Apple driver detects switch out and re-set up, 2. Some callbacks are involved and not implemented by your driver 3. Some special set up (like a buffer for context switched out data) is required and missing in your driver, but reminder that I am curious and clue less)
<Sobek[m]>
(And urgh random bugs are the worse :/)
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-gpu
<alyssa>
Yes.
<alyssa>
#3 is the most likely, given the overheads involved in #1 and #2
m5zs7k has joined #asahi-gpu
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-gpu
jtmcx has quit [Quit: k byeeee]
jtmcx has joined #asahi-gpu
bisko has quit [Remote host closed the connection]
bisko has joined #asahi-gpu
<alyssa>
Think I will stream after all
* alyssa
gets OBS up
<Tramtrist>
just made it into japan a few hours ago.. wouldnt mind having something to fill my jet lagged time with