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
PhilippvK has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
pyropeter1 has joined #asahi-gpu
PyroPeter_ has quit [Ping timeout: 480 seconds]
boardwalk has quit [Quit: Ping timeout (120 seconds)]
boardwalk has joined #asahi-gpu
amarioguy has quit [Remote host closed the connection]
amarioguy has joined #asahi-gpu
<phire>
lina: so the firmware handles the partial rendering itself, but does it also handle the auto-buffer resize behavour that alyssa described? That would make more sense to be in the kernel.
<phire>
actually, IMO it would make even more sense to be handled by userspace, but we know it isn't
<lina>
phire: The kernel handles that, I already looked at it in the last stream
<lina>
It can add pages to the buffer manager and trigger a reconfigure
<lina>
I'm not sure how it decides to do it yet; it's not reading the obvious "number of partial draws" counters, but there's probably some other field elsewhere that tells it what it needs to know.
<phire>
potenitally the firmware decides when some threshold is met and sends an event telling the kernel to reconfigure?
<lina>
I was just talking with alyssa earlier about whether we should do it in the kernel or userspace (both are ugly in their own way...).
<lina>
I didn't see anything that looked like a special event
<phire>
my gut would be to put as many things in userspace as possible. since it's looking like it's going to be a pretty big kernel driver.
<phire>
but prehaps it's simpler to do it in kernel
<lina>
The buffer manager has to be in the kernel since that data structure is in kernel address space, but I was thinking the actual management should be done from userspace (making the decisions and donating pages of memory)
MajorBiscuit has joined #asahi-gpu
os9 has joined #asahi-gpu
os has quit [Read error: Connection reset by peer]
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-gpu
voliteon has joined #asahi-gpu
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-gpu
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-gpu
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-gpu
MajorBiscuit has quit [Ping timeout: 480 seconds]
kov has joined #asahi-gpu
MajorBiscuit has joined #asahi-gpu
alyssa has joined #asahi-gpu
<alyssa>
glmark2 Score: 60375
<alyssa>
vroom vroom
opticron has quit [Ping timeout: 480 seconds]
<_jannau_>
looks too good to be true for m1 with 8 gpu cores (glmark2 default benchmarks at 800x600)
<alyssa>
_jannau_: CPU only test, no GPU ;)
alyssa has quit [Quit: leaving]
<Dcow[m]>
alyssa: is means it passed all the tests now?
<Dcow[m]>
oh, sorry. missed the CPU note. why it's here then?)