#
#asahi-gpu · 2023-06-15 14:53
alyssai'm putting wait_pix's in but that doesn't seem to be strong enough
#asahi-gpu · 2023-06-15 14:52
alyssadraw #1 writes to an image, draw #2 reads it
#asahi-gpu · 2023-06-15 14:52
alyssaok.. my blending is not working with multiple draws together
#asahi-gpu · 2023-06-15 13:44
alyssa(For development and CI, anholt's deqp-runner shards the CTS across all available CPUs, which scales almost linearly. But that's not valid for official CTS submissions.)
#asahi-gpu · 2023-06-15 13:43
alyssa(CTS is mostly CPU-bound. and the "real" CTS runs are basically single-threaded.)
#asahi-gpu · 2023-06-15 13:42
alyssayour M1 Max will not have that problem :-p
#asahi-gpu · 2023-06-15 13:42
alyssaGLES3.1 on Mali took ~12h if I remember
#asahi-gpu · 2023-06-15 13:42
alyssaThe most annoying part is that the CTS is slow
#asahi-gpu · 2023-06-15 13:37
alyssathere's a little bit more work to do the actual submission but that's on my end
#asahi-gpu · 2023-06-15 13:36
alyssaI mean the CTS is kinda annoying but. "git clone this repo, cmake build it, build mesa, run ./cts-runner, wait a zillion hours, zip up all the files produced and send me them"
#asahi-gpu · 2023-06-15 13:35
alyssaand no, not particularly complicated
#asahi-gpu · 2023-06-15 13:35
alyssa_jannau__: ooh, that might be helpful indeed instead of me doing 1 run and Lina doing 17000 :-p
#asahi-gpu · 2023-06-15 13:34
_jannau__are the complicated requirements for CTS runs? I could cover M1 Max, M1 Ultra and M2
#asahi-gpu · 2023-06-15 13:28
linaSee signal...
#asahi-gpu · 2023-06-15 13:27
linaBut I'm more worried about whether I'll be in a state to kick off CTS runs and fix the remaining M2 Pro/Max things...
#asahi-gpu · 2023-06-15 13:26
linaThe machines are not going in boxes ^^
#asahi-gpu · 2023-06-15 13:26
alyssaahead-of-schedule is a good thing, hey
#asahi-gpu · 2023-06-15 13:26
alyssanot sure if you'll be able to kick off CTS runs next week though if your machines are in random boxes ;)
#asahi-gpu · 2023-06-15 13:25
lina^^
#asahi-gpu · 2023-06-15 13:25
alyssaso... might have a branch passing CTS on Monday
#asahi-gpu · 2023-06-15 13:20
alyssaIt's growing on me like bacteria
#asahi-gpu · 2023-06-15 13:19
linaHey I know you enjoyed my mesa fault decoding code ^^
#asahi-gpu · 2023-06-15 13:18
linawwwwwwwww
#asahi-gpu · 2023-06-15 13:18
alyssasoft fault was the hummus in my macOS mesa debug PITA
#asahi-gpu · 2023-06-15 13:17
linaAnd yeah, fair ^^
#asahi-gpu · 2023-06-15 13:17
linaI suspect that setting only affects stuff fetched from shader cores (textures and device loads), so I think we'll still get hard faults for other brokenness like bad command streams or TVB problems
#asahi-gpu · 2023-06-15 13:16
alyssaWhat I mean is, even if literally every other user in existence has soft fault enabled, I want hard faults on my dev machines for my own use, and I don't want enabling faults to regress CTS lol
#asahi-gpu · 2023-06-15 13:16
alyssaYeah
#asahi-gpu · 2023-06-15 13:16
linaTBH I want to enable softfault by default, it's going to make things a lot more stable for people I bet, since hard faults can kill unrelated jobs and also trigger other existing bugs...
#asahi-gpu · 2023-06-15 13:15
alyssa(if only because it makes Mesa debugging massively easier)
#asahi-gpu · 2023-06-15 13:15
linaOK ^^
#asahi-gpu · 2023-06-15 13:15
alyssasince we need to support the !softfault case even if we end up shipping softfault
#asahi-gpu · 2023-06-15 13:14
alyssaThis isn't blocking CTS though
#asahi-gpu · 2023-06-15 13:14
alyssaMight be fun
#asahi-gpu · 2023-06-15 13:13
linaYou could try adding this to the kernel yourself, maybe try a bit of kernel rust~ ✨
#asahi-gpu · 2023-06-15 13:13
linaYeah
#asahi-gpu · 2023-06-15 13:13
alyssaif we add more bits later... ugly UAPI > breaking userspace
#asahi-gpu · 2023-06-15 13:12
alyssaYeah, ++
#asahi-gpu · 2023-06-15 13:12
linaSince we know that's the safe macOS behavior
#asahi-gpu · 2023-06-15 13:12
linaI guess if == 0xb then set the flag, otherwise don't set it, for now
#asahi-gpu · 2023-06-15 13:12
linaYeah, so then just a feature flag, only problem is once we do understand it we might want to split that into separate feature flags... but that's okay I guess
#asahi-gpu · 2023-06-15 13:12
alyssasince that's a ticking uapi given the fw randomly changes on uprevs
#asahi-gpu · 2023-06-15 13:11
alyssaIMO, do *not* pass through the value unparsed if it's not 100% hardware defined
#asahi-gpu · 2023-06-15 13:11
linaWell away from all the power management gunk
#asahi-gpu · 2023-06-15 13:11
linaThere are a few "interesting" clusters of flags in the giant initdata structures and that's one of them
#asahi-gpu · 2023-06-15 13:11
alyssa13:10 < lina> I'm not sure if we should just pass that to userspace as-is as an integer without understanding it though, it is parsed by the firmware as far as I know, not straight a hardware register.
#asahi-gpu · 2023-06-15 13:11
alyssasensible
#asahi-gpu · 2023-06-15 13:11
linaGuesswork...
#asahi-gpu · 2023-06-15 13:11
alyssaOk, how'd you fgure out that's fault control and that setting not-0xb is safe?
#asahi-gpu · 2023-06-15 13:11
linaAnd I guess 0 was disable/fault

plus ›