00:17 fdobridge: <a​irlied> so I think HOST reads the pushbufs from the BAR mapping so we can't just go around evicting stuff like nouveau does
00:29 fdobridge: <a​irlied> which seems strange, so must be something else like a dma or somethign
07:06 fdobridge: <a​irlied> @gfxstrand care to give https://paste.centos.org/view/c261b46e
07:07 fdobridge: <a​irlied> it's the first interesting thing I've found that might be an actual cause
07:22 airlied: dakr: https://lore.kernel.org/dri-devel/20240311072037.287905-1-airlied@gmail.com/T/#u can we get that into drm-misc-next-fixes asap (and once you review it)
08:50 fdobridge: <r​edsheep> Hmm. So I switched to the open nvidia driver for a bit for testing and when I switched back I have some bizarre results. My 4k120 DP monitor now loaded up at 120 hz. Maybe that's just due to updating to 6.8 proper if you guys have touched that, but it's weird
08:52 fdobridge: <r​edsheep> What's much much weirder though is that my HDMI 4k120 TV *also* now shows a 120hz mode. I can confirm in the OSD that it's getting a 4k120 signal, and I can see from the cursor on that display that it's just as smooth as I would expect, however aside from the cursor that screen is completely black
08:53 fdobridge: <r​edsheep> I am not sure how even that much is possible unless y'all secretly implemented support for HDMI FRL, or maybe my GSP firmware didn't completely reset and has it stuck toggled on? Makes no sense.
08:55 fdobridge: <r​edsheep> @karolherbst I know you mentioned that implementing FRL might be on your list, and I think the weirdness above probably confirms that it's very very close to working.
08:56 fdobridge: <k​arolherbst🐧🦀> nah... I'm sure it's still doing 2.0 but like... weird
08:56 fdobridge: <k​arolherbst🐧🦀> maybe
08:56 fdobridge: <k​arolherbst🐧🦀> though dunno
08:56 fdobridge: <k​arolherbst🐧🦀> I'm kinda planning to take a look later
08:56 fdobridge: <r​edsheep> I don't see how that would be possible, the OSD confirms the bit depth and framerate, and I can see the cursor is nice and sharp
08:58 fdobridge: <r​edsheep> And I don't think you can even do DSC with TDMS, even aside from whether that is possible with this display which from what I understand, it isn't.
08:58 fdobridge: <k​arolherbst🐧🦀> you can always drop the bpc
08:58 fdobridge: <r​edsheep> Right but the display tells it is 8bit as expected
08:58 fdobridge: <k​arolherbst🐧🦀> though I don't know if we do that for HDMI...
08:58 fdobridge: <r​edsheep> I have confirmed that field is accurate when using 10 bit on windows
08:59 fdobridge: <k​arolherbst🐧🦀> mhh
08:59 fdobridge: <r​edsheep> Let me see if I can get the debug info to show me more
08:59 fdobridge: <k​arolherbst🐧🦀> yeah...
08:59 fdobridge: <k​arolherbst🐧🦀> you should boot with drm.debug=.. uhhh...
08:59 fdobridge: <k​arolherbst🐧🦀> 0x4? 0x6? I have no idea 🙂
09:00 fdobridge: <k​arolherbst🐧🦀> actually you can change it at runtime
09:00 fdobridge: <r​edsheep> I mean that LG tvs can tell you debug info from their side, I am trying to find how
09:08 fdobridge: <r​edsheep> They moved it in recent firmware so I had to explore a little, if your TV is LG it is General > Channels > hover Channel Tuning and spam 1 on the remote. I am seeing it confirms I have 3840x2160P @ 120Hz RGB 8bit
09:08 fdobridge: <r​edsheep> It also shows me I have an FRL link where including the vsync and hsync I am at 4400x2250
09:08 fdobridge: <k​arolherbst🐧🦀> mhhhh
09:08 fdobridge: <k​arolherbst🐧🦀> interesting
09:08 fdobridge: <k​arolherbst🐧🦀> and that's on nouveua?
09:08 fdobridge: <k​arolherbst🐧🦀> *nouveau
09:09 fdobridge: <r​edsheep> Yep
09:09 fdobridge: <k​arolherbst🐧🦀> but only the cursor shows?
09:09 fdobridge: <k​arolherbst🐧🦀> but yeah.. this might be a trivial fix
09:10 fdobridge: <r​edsheep> Just confirmed in lspci, loaded module is nouveau
09:10 fdobridge: <r​edsheep> Yeah, just cursor
09:10 fdobridge: <k​arolherbst🐧🦀> I can imagine that we get bandwidth limits from GSP and just ack the modelines, but then don't actually handle allocating buffers correctly or put the GPU into the correct mode? I don't know 🙂
09:10 fdobridge: <k​arolherbst🐧🦀> @redsheep does this happen on a fresh boot?
09:11 fdobridge: <k​arolherbst🐧🦀> but maybe 6.8 landed some 2.1 stuff? I have no idea 🙂 but intel does support 2.1
09:11 fdobridge: <k​arolherbst🐧🦀> it just doesn't really appear on the kernel level
09:11 fdobridge: <r​edsheep> I will try shutting down cold so there's no chance the gsp lives, one sec
09:15 fdobridge: <r​edsheep> Oh weird, I didn't actually expect cold boot to work. Yeah I still have an FRL connection.
09:16 fdobridge: <r​edsheep> Aside from just being a cursor it just works
09:17 fdobridge: <r​edsheep> Maybe the Nvidia drivers left some config on my system that gets me further here but still this should mean this is really close to functional
09:19 fdobridge: <r​edsheep> Would any of the debug info from there still be helpful?
09:22 fdobridge: <r​edsheep> It even successfully switches modes down to 100 hz and the display picks it up. This is crazy close to working.
09:23 fdobridge: <k​arolherbst🐧🦀> so 100 hz works?
09:23 fdobridge: <k​arolherbst🐧🦀> or just it gets listed
09:23 fdobridge: <r​edsheep> Still black. Switching down to 60 doesn't get it to start rendering but does down to tdms
09:24 fdobridge: <k​arolherbst🐧🦀> so with 60 it's still broken? 😄
09:24 fdobridge: <k​arolherbst🐧🦀> mhhh
09:24 fdobridge: <k​arolherbst🐧🦀> I wonder if you just run into weirdo kernel bugs
09:25 fdobridge: <k​arolherbst🐧🦀> any errors in `dmesg` or so?
09:25 fdobridge: <r​edsheep> Oh. Yeah 60 works on the login screen but goes to black as soon as I'm in my session... Wtf?
09:25 fdobridge: <k​arolherbst🐧🦀> maybe you are running into a different bug? 😄
09:25 fdobridge: <k​arolherbst🐧🦀> and it already works
09:30 fdobridge: <k​arolherbst🐧🦀> I guess your gl driver is screwed up or something
09:31 fdobridge: <r​edsheep> I have no idea what's happening to my system now lol... I had been trying x11 and I thought I'd switch to see if it was just cursed x things but the Wayland session locked up my machine
09:31 fdobridge: <k​arolherbst🐧🦀> you might have to purge nvidia for real
09:31 fdobridge: <k​arolherbst🐧🦀> or check the kernel logs
09:32 fdobridge: <r​edsheep> I'll double check it's gone, and yeah I'll go back through logs and see if it mentions anything
09:36 fdobridge: <r​edsheep> ... I have no Nvidia packages, and yet on closer inspection lspci says kmd in use Nvidia but module nouveau 🤦
09:36 fdobridge: <r​edsheep> My package manager should have fixed this for me
09:38 fdobridge: <a​irlied> @gfxstrand seems to make it through a cts run here, so hopefully works for you
09:38 fdobridge: <r​edsheep> How did I even get this far on Nvidia's kernel but otherwise nouveau?
09:43 fdobridge: <r​edsheep> Ah, alright I fixed that loading and the faster modes are all gone again 😞
10:01 fdobridge: <k​arolherbst🐧🦀> @airlied have you seen GSP errors like those? https://gitlab.freedesktop.org/drm/nouveau/-/issues/321
10:02 fdobridge: <a​irlied> Ah yeah need to comment that our
10:02 fdobridge: <k​arolherbst🐧🦀> appears something to be wonky on AMD+Nvidia ssytems
10:02 fdobridge: <a​irlied> It's just display port auxch timeouts
10:02 fdobridge: <k​arolherbst🐧🦀> ohh.. it's just an error in the console and everything works?
10:02 fdobridge: <a​irlied> Should do with 0xffff ones
10:03 fdobridge: <k​arolherbst🐧🦀> okay
10:03 fdobridge: <k​arolherbst🐧🦀> yeah, then we should remove that message so users won't keep filing bugs for this 😄
10:20 fdobridge: <a​irlied> Yeah I'm pretty sure it's just pointless reporting, but I should play around a bit and maybe Lyude will have some ideas later, I should probably dump the auxch transactions
10:43 Sid127: god it's so weird
10:43 Sid127: physics counts from 1
10:43 Sid127: computers count from 0
10:43 Sid127: my head hurts
10:45 Sid127: doesn't help that I'm sick
10:46 fdobridge: <r​edsheep> Speaking of heads hurting, I decided to skim all of the code in nvidia's open driver for implementing FRL and uh... Yeah I hadn't quite seen some of the places that was being mentioned. There are actually 1330 references to it, and a few hundred lines of code it touches.
10:48 fdobridge: <r​edsheep> Though, their version is mostly so complicated because it's all wrapped up with supporting 10 and 12 bpc, DSC, gpu virtualization, and DP to HDMI FRL adapters that are both extremely rare and borderline useless given NVIDIA hasn't implemented DP 2.1 to offer high enough speed for those adapters to do much.
10:50 fdobridge: <r​edsheep> In reality there's only a few dozen bits being set on the hardware across all of that. Still, it would probably wouldn't make sense to bother without doing DSC and higher bpc modes at the same time.
10:53 fdobridge: <r​edsheep> You could probably do a really hacky implementation with only a few new lines in nouveau but doing it right involves probably about half the work involved in implementing an entirely new connector...
10:56 transmittingsense: https://github.com/lszeremeta/mizgra/tree/main?tab=MIT-1-ov-file#readme there are many others but this suites , license mentions nothing about derived works, and output of the generator may or may not be derived work, but it's not the software that generates it in any way, so they do not specify this, public domain oportunity in other words.
10:57 transmittingsense: opportunity, so we have the needed sw
11:11 transmittingsense: but i left the compressor and have another link translating to scala from rdf too, last not sure how they get from llvm in other means from javascript and rdf html, so scala is not that needed either. I have done little typescript and javascript before on electron engine, they have aot or jit and asar archives, java has similar archives, prolly scala too.
11:12 transmittingsense: so i actually expect that i already have every needed solution.
11:18 transmittingsense: even though those software could exist for passive incomes, i do not think anyone operates this way as giving others money, so i had done it before as well tbh. it was not serving me well , outcomes were not good , it's better when people get paid if they earned it by their genius activity instead.
11:29 transmittingsense: i also tried my luck on scam looking business that offered compute technology with bread price, and they delivered socks expectedly enough, but i got medium good hardware in my box in stacks that are very good, and in general technology is manufactured with very good prices even if not so low as at facebook scams they work at very high manufacturing throughputs and there is nothing wrong, i still get slightly older hw with very good
11:29 transmittingsense: prices and can collect some to buy more modern ones, which normally i am not interested in though.
11:30 transmittingsense: so me i have not seen problems for long as to why they terror me alike all should be very well done in world.
11:30 fdobridge:<S​id> is confused...
11:47 transmittingsense: having not graduated from local universities which are not at the highest ranks not even among 500first universities in the world in technical era is not anyways stopping me, since anyways all top ranked ones worth of something are located in america or central europe, Berkley Stanford and Massachusetts are first three incorrect order but it's because they maintained and started all the world wide web. It does not bother me they do so
11:47 transmittingsense: good work too tbh.
11:49 transmittingsense: they are not so arrogant at all, it's just they do not acredit such papers cause they do more.
12:01 transmittingsense: chicago and illinois are high ranks, there were criminal gangs fighting with legal forces too, so FBI and just beat those gangs, and they have lots of skills to tap people hence in addition to very high standards at their university camps.
12:03 fdobridge: <S​id> right....
12:08 juri_: this is just going to continue to be a problem.
12:09 karolherbst: yeah.. and I have no idea what to actually do about it.. maybe somebody has contact to the family? airlied?
12:09 karolherbst: I know that somebody did in the past
12:12 Sid127: the family?
12:12 karolherbst: yeah well.. they have relatives
12:12 karolherbst: I think somebody spoke with the sister once
12:12 Sid127: huh
12:13 karolherbst: I mean.. what do you think where they came from? out of thin air? :P
12:13 Sid127: ...I still think we should preemptively ban connections from TOR and VPNs, but I dunno the full story
12:13 karolherbst: person with a damaged brain
12:13 karolherbst: would be the tldr
12:13 Sid127: just G line and ask to reconnect without vpn
12:13 karolherbst: if we ban TOR and VPN they just create accounts and reconnect
12:13 Sid127: I see...
12:13 karolherbst: it's really pointless to block anything there unless we block like.. a lot
12:14 karolherbst: like.. VPN/TOR and entire countries
12:14 Sid127: abandon #nouveau, move to #nvk? :D
12:14 karolherbst: and then there might be VPNs we haven't blocked
12:14 karolherbst: they hop into other channels as well
12:14 karolherbst: like any drm/mesa related ones
12:15 Sid127: what about making a LiberaChat#nouveau
12:16 karolherbst: I mean.. they managed to move from freenode to oftc
12:16 Sid127: hmmm :\
12:17 Sid127: so it's just one person?
12:17 karolherbst: yeah
12:18 Sid127: ...impressive
12:18 karolherbst: well.. persons like that exists everywhere
12:19 Sid127: I guess
13:06 fdobridge: <k​arolherbst🐧🦀> @redsheep yeah.. I don't suspect I'll need more than a day to support FLR... ohh wait uhhh...
13:06 fdobridge: <k​arolherbst🐧🦀> uhhh...
13:06 fdobridge: <k​arolherbst🐧🦀> I don't have an nvidia GPU with HDMI 2.1...
13:06 fdobridge: <r​edsheep> You don't have an ampere or ada?
13:06 fdobridge: <k​arolherbst🐧🦀> I do have an ampere and an ada
13:07 fdobridge: <k​arolherbst🐧🦀> they are just DP only
13:07 fdobridge: <k​arolherbst🐧🦀> mhh actually...
13:07 fdobridge: <k​arolherbst🐧🦀> I might have to check the laptops I have here
13:07 fdobridge: <k​arolherbst🐧🦀> maybe one of them has HDMI on ampere+
13:11 fdobridge: <r​edsheep> Better hope the HDMI is wired to the nvidia gpu if so...
13:12 fdobridge: <k​arolherbst🐧🦀> yeah...
13:13 fdobridge: <r​edsheep> I would be happy to help test anything you have in progress if you don't have hardware. I have the next couple days off work so I could put some good time into it
13:13 prophetalike: karolherbst: you are not among the real individuals i mentioned, you have a talent of being rot in the brain and being always wrong. Not to mention that all the code you made was researched by me anyways, you are empty spot entirely in competitive sports too. Keep on eating your steroids .
13:15 fdobridge: <S​id> doesn't HDMI foundation disallow open source impls of HDMI 2.1
13:16 fdobridge: <r​edsheep> They don't want public disclosure of the spec, but all of that is stuffed in the GSP, else the open nvidia kernel driver wouldn't be possible.
13:16 fdobridge: <S​id> foundation/forum/whatever
13:16 fdobridge: <S​id> oh
13:16 fdobridge: <S​id> neat
13:16 fdobridge: <S​id> rare nouveau W over amdgpu?
13:16 fdobridge: <r​edsheep> Yeah
13:17 fdobridge: <k​arolherbst🐧🦀> Intel already supports it
13:17 fdobridge: <S​id> ~~though I know I'm not getting any more hdmi products~~
13:17 fdobridge: <k​arolherbst🐧🦀> but like...
13:17 fdobridge: <k​arolherbst🐧🦀> in the most cheating way
13:17 fdobridge: <S​id> how
13:17 fdobridge: <k​arolherbst🐧🦀> they have a physical converter
13:17 fdobridge: <k​arolherbst🐧🦀> to DisplayPort
13:19 fdobridge: <S​id> oh, right, that
13:29 fdobridge:<z​mike.> runs glcts with sparse changes and gets failures from literally every sparse test
13:30 fdobridge: <z​mike.> https://cdn.discordapp.com/attachments/1034184951790305330/1216739915711385722/image.png?ex=66017c59&is=65ef0759&hm=292949e8100e99ec6b517a5e3bc903d8a5d0ef7a89d0fdb19e7596c628c293e2&
13:34 fdobridge: <g​fxstrand> WTF? *sigh*
13:34 fdobridge: <g​fxstrand> Okay, I'll take a look.
13:36 fdobridge: <z​mike.> I'll leave it in your capable hands
13:42 fdobridge: <z​mike.> on the plus side you're down to only one hang
13:42 fdobridge: <z​mike.> nice work on the tess exception thing
13:42 fdobridge: <g​fxstrand> Thanks. Is it the piglit image tests that are still blowing up?
13:43 fdobridge: <g​fxstrand> Those tests are cruel
13:43 fdobridge: <z​mike.> I haven't tested piglit yet
13:43 fdobridge: <z​mike.> which ones are you referring to
13:43 fdobridge: <g​fxstrand> https://gitlab.freedesktop.org/mesa/mesa/-/issues/10759
13:43 fdobridge: <g​fxstrand> You filed the issue
13:43 fdobridge: <z​mike.> I file lots of issues
13:43 fdobridge: <z​mike.> let's see if it's fixed
13:44 fdobridge: <z​mike.> it is not fixed
13:44 fdobridge: <g​fxstrand> I didn't figure
13:45 fdobridge: <z​mike.> `KHR-GL46.direct_state_access.framebuffers_texture_layer_attachment` is the glcts hang I was referring to
13:45 fdobridge: <z​mike.> but yes, the piglit shader image tests are pretty miserable
13:45 fdobridge: <g​fxstrand> kk
13:46 fdobridge: <z​mike.> I think you are now (once all my pending MRs land) 2 non-sparse bugs away from glcts conformance
13:46 fdobridge: <z​mike.> fixing e.g., `dEQP-GLES31.functional.shaders.sample_variables.sample_mask_in.bit_count_per_two_samples.multisample_rbo_4` should get the other one
13:47 fdobridge: <z​mike.> (this is for all versions of glcts)
13:47 fdobridge: <z​mike.> though it's possible `dEQP-GLES31.functional.shaders.multisample_interpolation.interpolate_at_sample.non_multisample_buffer.sample_n_default_framebuffer` is a separate issue, I just guessed they'd be the same since they're both ms
13:48 fdobridge: <g​fxstrand> Getting 4.6 conformance sounds like a good project for this week.
13:48 fdobridge: <z​mike.> then you only have to fix the one hang
13:48 fdobridge: <z​mike.> though I guess since you have sparse advertised they need to be fixed too...
13:49 fdobridge: <g​fxstrand> I expect that's like one bug
13:49 fdobridge: <z​mike.> could be
13:49 fdobridge: <z​mike.> nvidia doesn't successfully pass a couple of those either; they've got one format where they fail to return data
13:54 fdobridge: <g​fxstrand> Ugh... I hate not having debug information without GSP...
13:55 fdobridge: <g​fxstrand> Ugh... I hate not having debug information with GSP... (edited)
13:55 fdobridge: <m​ohamexiety> should I look into it as well, or continue with the modifiers stuff?
13:55 fdobridge: <g​fxstrand> continue with modifiers
13:55 fdobridge: <m​ohamexiety> got it
13:59 fdobridge: <g​fxstrand> Oh, good. This test report contains... nothing.
14:01 fdobridge: <g​fxstrand> debug.push got to 203M before I killed the test. Maybe this just does too many draws
14:03 fdobridge: <g​fxstrand> Yeah, it's rendering to a max-size 3D image.
14:04 fdobridge: <g​fxstrand> Which on NVIDIA is 8192
14:04 fdobridge: <g​fxstrand> It's literally just timing out
14:05 fdobridge: <g​fxstrand> Excuse me 16384, rather.
14:06 fdobridge: <g​fxstrand> @zmike. IDK how you want to handle that. I think if we just artificially reduce a limit it should pass
14:06 fdobridge: <g​fxstrand> Let me try quick
14:06 fdobridge: <z​mike.> not sure what you mean "how I want to handle it"
14:06 fdobridge: <z​mike.> if you're exposing a limit it should be usable
14:06 fdobridge: <z​mike.> so if it isn't [going to be] usable then you need to reduce the limit
14:07 fdobridge: <g​fxstrand> Oh, it's usable
14:07 fdobridge: <g​fxstrand> But I can't control apps (the CTS via Zink in this case) that submit 3h of rendering work to the GPU.
14:08 fdobridge: <g​fxstrand> It's not my fault that they decide to create a max-size 3D surface and bind every single layer as a separate render pass and render to it.
14:08 fdobridge: <z​mike.> no, but the test passes without issue on every other driver
14:08 fdobridge: <z​mike.> including nvidia proprietary
14:09 fdobridge: <g​fxstrand> If it passes on NVIDIA that's because they don't have a GPU timeout
14:09 fdobridge: <z​mike.> `KHR-GL46.direct_state_access.framebuffers_texture_layer_attachment,Pass,7.014799`
14:09 fdobridge: <z​mike.> from my last run there
14:09 fdobridge: <z​mike.> if nvk is taking 3 hours for the same test then probably that's an issue
14:09 fdobridge: <g​fxstrand> 3h is an exageration
14:10 fdobridge: <z​mike.> 7 seconds is a lot shorter
14:11 fdobridge: <g​fxstrand> Hrm... 4096 fails but 4095 passes...
14:43 fdobridge: <g​fxstrand> @zmike. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28103
14:50 fdobridge: <k​arolherbst🐧🦀> oh wow... what kind of code works once the driver is all sane
14:50 fdobridge: <k​arolherbst🐧🦀> tried to do similar things in the GL driver, but this entire part is just entirely cursed
14:55 fdobridge: <g​fxstrand> Yeah, this kind of shit is why I wrote NIL the way I did
14:57 fdobridge: <z​mike.> @gfxstrand 💪💪💪
15:36 fdobridge: <g​fxstrand> I'm going to use this as an excuse to try out my new insane testing strategy
15:37 fdobridge: <g​fxstrand> Also, we're gonna murder @airlied's kernel patch
15:37 fdobridge: <g​fxstrand> It's gonna be fun.
15:41 fdobridge: <k​arolherbst🐧🦀> though I'm curious on how that works if you are tiled on the z axis, or is the hardware actually taking this all into account internally?
15:41 fdobridge: <g​fxstrand> Oh, it works for Z tiling, too!
15:41 fdobridge: <g​fxstrand> It offsets into the tile
15:41 fdobridge: <k​arolherbst🐧🦀> yeah..
15:41 fdobridge: <k​arolherbst🐧🦀> that's why I'm curious
15:41 fdobridge: <g​fxstrand> The only reason why that doesn't totally blow up is because, outside of GOBs, NVIDIA's tiling strategy is very straightforward.
15:42 fdobridge: <k​arolherbst🐧🦀> ahh
15:42 fdobridge: <k​arolherbst🐧🦀> so everything just aligns very well and it "just works"?
15:42 gloomineyes: juri_: there is no problems eventually such garbage as you all tend to be with karolherbst harassing and terror in others private territory get booted out from this life and planet, if you noticed you got shots of vaccines into butt cause of doing that, they end up sanctioning you trash.
15:42 fdobridge: <g​fxstrand> If you have a Z-tiled GOB (I guess that's a thing on Turing+?), we'll need to do Z gob offset using the base array layer
15:42 fdobridge: <k​arolherbst🐧🦀> right..
15:43 fdobridge: <g​fxstrand> I know that's a thing because there are two new HW bits in the texture header: `GOB3D` and `GOB_DEPTH_OFFSET` and I suspect the later is for exactly this case.
15:43 fdobridge: <k​arolherbst🐧🦀> yeah.. this would make sense
15:44 fdobridge: <g​fxstrand> For the render hardware, we'd just use the base layer
15:44 fdobridge: <k​arolherbst🐧🦀> and the copy path is also aware of the tiling, right?
15:44 fdobridge: <k​arolherbst🐧🦀> or is that done in a shader?
15:44 fdobridge: <g​fxstrand> Yeah but there's no problem there because the copy hardware can do as many Z slices as we want
15:45 fdobridge: <k​arolherbst🐧🦀> yeah, fair
15:45 fdobridge: <g​fxstrand> I'm kinda surprised the render hardware screws this up. It works up to 4095 even though the blob only advertises 2048
15:45 fdobridge: <g​fxstrand> Maybe they're just rounding down to a power of 2?
15:45 fdobridge: <k​arolherbst🐧🦀> and you don't operate on 2D views at this level anyway
15:46 fdobridge: <k​arolherbst🐧🦀> isn't that like the normal array limit?
15:46 fdobridge: <g​fxstrand> Yeah, that's the array limit
15:46 fdobridge: <g​fxstrand> So arrays are fine
15:46 fdobridge: <g​fxstrand> I switched arrays as well, though, just for consistency
15:46 fdobridge: <k​arolherbst🐧🦀> yeah.. I can imagine they didn't bother with 3D images there :ferrisUpsideDown:
15:46 fdobridge: <k​arolherbst🐧🦀> and just optimized enough for 2d arrays
15:46 fdobridge: <k​arolherbst🐧🦀> or so
15:46 fdobridge: <g​fxstrand> I suspect num layers is 12 bits internally and they just round down to a power of 2
15:47 fdobridge: <k​arolherbst🐧🦀> yeah..
15:47 fdobridge: <g​fxstrand> It's a little weird that you can create bigger 3D textures than array textures
15:47 fdobridge: <k​arolherbst🐧🦀> well... yeah, but also...
15:47 fdobridge: <g​fxstrand> But who am I to judge? I just write drivers.
15:47 fdobridge: <k​arolherbst🐧🦀> gl has lower limits for arrays, so I guess...
15:48 fdobridge: <k​arolherbst🐧🦀> but it's already kinda weird that there is more to 3d vs 2d arrays than just tiling
15:50 fdobridge: <g​fxstrand> Oh, they're fundamentally different
15:51 fdobridge: <g​fxstrand> Well, the difference is whether or not the miplevel applies to z
15:51 fdobridge: <k​arolherbst🐧🦀> right
15:51 fdobridge: <k​arolherbst🐧🦀> and the layer coord is always an int and stuff
15:51 fdobridge: <k​arolherbst🐧🦀> but besides those details, you could just treat them the same on the hw level
15:51 fdobridge: <k​arolherbst🐧🦀> and just configure it one or the other way
15:52 fdobridge: <k​arolherbst🐧🦀> but I guess that's just nvidia being nvidia
15:52 fdobridge: <m​arysaka> Do we happen to have any documentation about MME shadow RAM on any gen?
15:52 fdobridge: <k​arolherbst🐧🦀> nope
15:52 fdobridge: <k​arolherbst🐧🦀> the docs on MME are like.. well...
15:52 fdobridge: <k​arolherbst🐧🦀> we don't have much
15:53 fdobridge: <m​arysaka> NVIDIA seems to use that for conditional rendering compared to the traditional RENDER_ENABLE way
15:54 fdobridge: <z​mike.> @gfxstrand so what's next on the bug-smashing agenda now that you've finally defeated all the (cts) hangs
15:57 fdobridge: <g​fxstrand> No we don't. It's something I'd like to understand, though. That's the thing that I never did get figured out in my MME RE that's bugged me ever since.
15:58 fdobridge: <g​fxstrand> Once these tests run, I'll poke at sparse. I'd love it if we could submit GL 4.6
15:58 fdobridge: <g​fxstrand> Unfortunately, I have a feeling I'm going to end up learning how to run the GL CTS, aren't I?
15:58 fdobridge: <g​fxstrand> Or do you want to do the submissiosn?
15:58 fdobridge: <g​fxstrand> Or do you want to do the submissions? (edited)
15:58 fdobridge: <g​fxstrand> I have a feeling I have more hardware
16:00 fdobridge: <z​mike.> I have that feeling too
16:00 fdobridge: <z​mike.> great news though
16:00 fdobridge: <z​mike.> glcts submissions are pretty simple and you only need 64bit
16:01 fdobridge: <z​mike.> you just fire off `cts-runner` and you're basically done
16:03 fdobridge: <z​mike.> https://github.com/KhronosGroup/VK-GL-CTS/wiki/Creating-a-OpenGL-and-OpenGL-ES-Submission-Package is the authoritative documentation
16:06 fdobridge: <p​ac85> Ptsd
16:08 fdobridge: <g​fxstrand> Hopefully this will be the first and only time I ever submit GL conformance
16:09 fdobridge: <g​fxstrand> I'm enjoying my new insane testing strategy
16:09 fdobridge: <z​mike.> imo just wait until you can do ES too
16:09 fdobridge: <z​mike.> and then do both at once
16:09 fdobridge: <z​mike.> it's only one extra bug
16:11 fdobridge: <p​ac85> So zink on nvk is already known to pass all the tests?
16:11 fdobridge: <z​mike.> the baseline is in git
16:12 fdobridge: <g​fxstrand> I don't know what "baseline" means. Is it a results file in the ci subdir or something?
16:12 fdobridge: <z​mike.> yes
16:12 fdobridge: <g​fxstrand> There's a lot listed in zink-nvk-fails.txt
16:12 fdobridge: <g​fxstrand> Oh, those are piglits
16:12 fdobridge: <z​mike.> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/gallium/drivers/zink/ci/zink-nvk-fails.txt?ref_type=heads
16:12 fdobridge: <z​mike.> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/gallium/drivers/zink/ci/zink-nvk-skips.txt?ref_type=heads
16:13 fdobridge: <z​mike.> somehow you have a ton of ARB_uniform_buffer_object piglit fails
16:17 fdobridge: <g​fxstrand> If you've not run piglit in a while, those may be stale.
16:18 fdobridge: <z​mike.> I ran it friday?
16:18 fdobridge: <z​mike.> so probably not unless you fixed it over the weekend
16:18 fdobridge: <g​fxstrand> Oh, okay
16:18 fdobridge: <g​fxstrand> I'll have to look at some point
16:21 fdobridge: <z​mike.> I imagine it's something simple
16:25 fdobridge: <g​fxstrand> Probably
16:28 fdobridge: <m​arysaka> I will write a proper fix for conditional rendering for now (tldr; hw reads 64 bits and not 32 bits for the compare) and dig that a bit
16:44 fdobridge: <g​fxstrand> `Pass: 1596039, Fail: 5, Crash: 3, Skip: 2158502, Duration: 54:44, Remaining: 0`
16:44 fdobridge: <g​fxstrand> I like having sub-1h CTS run times again. 😁
16:45 fdobridge: <g​fxstrand> I had to re-type it on top of drm-misc-fixes but that just survived a 32-thread 2-GPU CTS run with nothing at all in dmesg.
16:45 fdobridge: <g​fxstrand> We'll see how it goes this week.
16:46 fdobridge: <g​fxstrand> I really should figure out why the dEQP-VK.compute.pipeline.device_group.dispatch_base tests randomly segfault...
16:46 fdobridge: <g​fxstrand> I really should figure out why the `dEQP-VK.compute.*.dispatch_base` tests randomly segfault... (edited)
16:49 fdobridge: <k​arolherbst🐧🦀> I kinda hope it fixes all those random issues :ferrisUpsideDown:
16:52 fdobridge: <g​fxstrand> @zmike. KHR-GL46.sparse_texture2_tests.StandardPageSizesTestCase is failing because it thinks Zink is returning (0,0,0) for the block size. Zink never calls into NVK to query it.
16:57 fdobridge: <z​mike.> what's the params for zink_get_sparse_texture_virtual_page_size?
16:57 fdobridge: <g​fxstrand> Looks like it's blowing up on `PIPE_FORMAT_B5G6R5_UNORM`
16:58 fdobridge: <z​mike.> I'm updating my proprietary baseline atm and can't test for a few
16:58 fdobridge: <m​arysaka> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28106
16:58 fdobridge: <z​mike.> I mean is it hitting that hook?
16:58 fdobridge: <z​mike.> or how is it failing to query nvk
17:10 fdobridge: <g​fxstrand> Well, there's multiple issues.
17:11 fdobridge: <g​fxstrand> One is that I wasn't advertising `PIPE_FORMAT_B5G6R5_UNORM`. That's fixed now. The second is that Zink is asking for storage image support which is just bonkers.
17:12 fdobridge: <z​mike.> hm?
17:16 fdobridge: <g​fxstrand> Top patch in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28107
17:17 fdobridge: <z​mike.> ah
17:17 fdobridge: <z​mike.> hm
17:17 fdobridge: <g​fxstrand> And now it's blowing up on MSAA storage:
17:17 fdobridge: <g​fxstrand> ```
17:17 fdobridge: <g​fxstrand> glcts: ../src/gallium/drivers/zink/zink_resource.c:410: get_image_usage_for_feats: Assertion `templ->nr_samples <= 1 || screen->info.feats.features.shaderStorageImageMultisample' failed.
17:17 fdobridge: <g​fxstrand> ```
17:18 fdobridge: <g​fxstrand> Back to you!
17:20 fdobridge: <z​mike.> yeah ok gimme a few, I gotta fix this last cts fail with proprietary before I forget how format selection works...
17:21 fdobridge: <g​fxstrand> I'm CTSing the 565 format patch on the off chance I screwed it up
17:32 fdobridge: <g​fxstrand> Okay, now for the GLES bug. I'm giving that one even odds
17:41 fdobridge: <g​fxstrand> This one is also arguably a Zink bug though it's kinda annoying.
17:42 fdobridge: <g​fxstrand> The test is using `interpolateAtSample(var, i)` where `i` is some rediculous sample index on the order of 150 but it's doing so without multisampling.
17:43 fdobridge: <g​fxstrand> The GLSL spec says:
17:43 fdobridge: <g​fxstrand> > Returns the value of the input *interpolant* variable at the location of *sample* number sample. If multisample buffers are not available, the input variable will be evaluated at the center of the pixel. If sample *sample* does not exist, the position used to interpolate the input variable is undefined.
17:43 fdobridge: <g​fxstrand> However, the SPIR-V spec says:
17:43 fdobridge: <g​fxstrand> > Result is the value of the input *interpolant* variable at the location of *sample* number sample. If sample *sample* does not exist, the position used to interpolate the input variable is undefined.
17:44 fdobridge: <g​fxstrand> Note that the bit about MSAA is missing from the SPIR-V spec.
17:44 fdobridge: <z​mike.> yeah...
17:44 fdobridge: <z​mike.> hm
17:44 fdobridge: <z​mike.> I wonder if that's intentional
17:44 fdobridge: <g​fxstrand> It requires a shader key bit on NVIDIA so it would break ESO...
17:44 fdobridge: <z​mike.> sample shading in general is not possible with shader objects
17:45 fdobridge: <g​fxstrand> MSAA works fine
17:45 fdobridge: <g​fxstrand> Just not the api-level `minSampleShading` thing
17:45 fdobridge: <z​mike.> right...
17:46 fdobridge: <g​fxstrand> Oh, you already have `samples` in your Zink shader key
17:47 fdobridge: <z​mike.> that's for deleting samplemask variables
17:47 fdobridge: <g​fxstrand> And now it can be for deleting `interpolateAtSample()` calls. 😛
17:47 fdobridge: <z​mike.> 🤔
18:02 fdobridge: <g​fxstrand> Pushed a Zink patch to my sparse fixes MR. Feel free to rewrite or nak or whatever.
18:02 fdobridge: <g​fxstrand> It passes the test
18:05 fdobridge: <z​mike.> hm it's close but not quite
18:05 fdobridge: <z​mike.> lemme sprinkle some seasoning on top
18:20 fdobridge: <z​mike.> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28113
18:22 fdobridge: <z​mike.> thanks for your contribution
18:22 fdobridge:<z​mike.> back to sparse
18:23 Lyude: btw dakr and airlied - I managed to get a modesetting device registered for rvkms over the weekend :)
18:24 Lyude: somehow something is leaking such that it doesn't seem we're releasing various dri sysfs paths on module unload, but I figure that I'll get that fixed at some point
18:28 fdobridge: <z​mike.> wip https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28115
18:39 fdobridge: <z​mike.> looks like the other fails...
18:39 fdobridge: <z​mike.> huh.
18:40 fdobridge: <z​mike.> you've got the same weirdness as proprietary where R8I returns no data
18:40 fdobridge: <z​mike.> that's `KHR-GL46.sparse_texture2_tests.SparseTexture2Commitment` and `KHR-GL46.sparse_texture2_tests.SparseTexture2Lookup`
18:41 fdobridge: <z​mike.> `KHR-GL46.sparse_texture_clamp_tests.SparseTextureClampLookupResidency` and `KHR-GL46.sparse_texture_clamp_tests.SparseTextureClampLookupColor` seems like the issue is you don't support Z16?
18:44 fdobridge: <z​mike.> ah wait
18:48 fdobridge: <z​mike.> alright that fixes the clamp tests...
19:02 fdobridge: <g​fxstrand> Yeah, NVIDIA depth is weird
19:03 fdobridge: <z​mike.> that's not the issue
19:04 fdobridge: <z​mike.> just testing latest change on nv blob before switching back to test this again...
19:10 fdobridge: <a​irlied> Is heaven still blue?
19:11 fdobridge: <g​fxstrand> AFAIK, yes.
19:11 fdobridge: <g​fxstrand> Yeah, that's really odd
19:12 fdobridge: <z​mike.> I think that's the issue with all the remaining tests
19:16 fdobridge: <g​fxstrand> I bet it's something going funky with 8-bit formats in general. I could believe that going that small breaks something.
19:16 fdobridge: <z​mike.> could be
19:16 fdobridge: <z​mike.> updated my sparse MR with all the fixes from my end
19:16 fdobridge: <z​mike.> there's 3 fails remaining, all with R8I broken
19:16 fdobridge: <z​mike.> and I think that's it
19:17 fdobridge: <z​mike.> nvidia GL blob can pass these tests
19:17 fdobridge: <z​mike.> so maybe there's something obvious they're doing that you can copy
19:21 fdobridge: <g​fxstrand> I added the 565 fix to !28103 so it'll go in when that one does
19:21 fdobridge: <z​mike.> nice
19:27 fdobridge: <a​irlied> Are they wierd sized 8-bit? Like odd width or height?
19:28 fdobridge: <z​mike.> example fail:
19:28 fdobridge: <z​mike.> > Testing uncommitted regions access for target: 37120, format: 33321 - Sparse Allocate [levels: 3] - Commit Region [level: 0] - Fill Texture [level: 0] - API Reads - Verify Texture [level: 0] - Shader Reads - Verify Texture [level: 0] - Error detected at 128,0,0 for sample 0: expected [255] got [0]
19:32 fdobridge: <g​fxstrand> 512x512
19:40 fdobridge: <g​fxstrand> I guess it's time for a game of "Who got the image tiling wrong?"
19:41 fdobridge: <g​fxstrand> But first I need to get this CTS test to run for only the one format
19:42 fdobridge: <t​om3026> you dont seem to be all out of line disabling exceptions if one assumes this comment applies for kepler and up https://github.com/NVIDIA/open-gpu-kernel-modules/blob/main/src/common/unix/nvidia-3d/src/nvidia-3d-kepler.c#L62
19:43 fdobridge: <g​fxstrand> heh
19:43 fdobridge: <g​fxstrand> What I'm doing is a little more granular than the big hammer but yes
19:45 fdobridge: <z​mike.> it's a shame that either we didn't get to this in a month or two or that mobica doesn't work faster, as they're currently in the process of splitting out all the glcts sparse tests into individual cases
19:46 fdobridge: <!​DodoNVK (she) 🇱🇹> So NVK is so accurate that it emulates the proprietary driver behavior?
19:47 fdobridge: <g​fxstrand> IDK if that's the way I'd put it or not
19:49 magic_rb: Whats the discord server that this is bridged through? If i could bridge through that it would make the whole experience nicer for me
19:49 fdobridge: <!​DodoNVK (she) 🇱🇹> magic_rb: https://discord.gg/CdZrXgTW97
19:50 magic_rb: Thanks, ill join it later when i get to a PC
22:05 fdobridge: <a​irlied> @gfxstrand so we should be able to expose the mappable VRAM on non-reBAR now?
22:20 fdobridge: <g​fxstrand> Maybe? I should swap in a Turing and give it a run. That or I might be able to disable ReBar in BIOS
22:22 fdobridge: <g​fxstrand> @airlied When I applied your new patch, I noticed that neither the map locking fix nor the `GETPARAM_VRAM_USED` fix have made it into drm-misc-fixes.
22:22 fdobridge: <g​fxstrand> Are my patches in another castle?
22:22 fdobridge: <a​irlied> yeah those are in Linus tree, drm-misc-fixes needs to backmerge more often
22:23 fdobridge: <a​irlied> 6.8 + that one fix should have everything
22:23 fdobridge: <g​fxstrand> Should I be running linus/master then?
22:23 fdobridge: <g​fxstrand> I swear, it's worse than playing mario
22:24 fdobridge: <a​irlied> right now 6.8 + one fix is likely the best
22:25 fdobridge: <a​irlied> not linus/master
22:25 fdobridge: <a​irlied> since I assume linus/master is now merge window happy
22:25 fdobridge: <g​fxstrand> So where does 6.8 live?
22:25 fdobridge: <a​irlied> v6.8 tag
22:26 fdobridge: <a​irlied> from Linus tree
22:30 fdobridge: <g​fxstrand> Okay. Building that combo now
22:30 fdobridge: <g​fxstrand> Do you want me to test without ReBar for maximum breakage potential?
22:31 fdobridge:<g​fxstrand> can't wait until she can just pull 6.8.1 from Fedora and stop mucking about with kernels.
22:32 fdobridge: <a​irlied> yeah I'd do non-rebar testing as well, though I tested on non-rebar with a hack to nvk to expose 256 mappable and it seemed to survive
22:32 fdobridge: <a​irlied> once you are running a fedora kernel, you'll just feature request something else
22:33 fdobridge: <a​irlied> exposing multiple queues 😛
22:36 fdobridge: <a​irlied> if you complain too much about building your own kernel, I'll just go and hire ickle 😛
22:41 fdobridge: <z​mike.> @gfxstrand I think I might have tractored your z slice MR with baseline updates
22:41 fdobridge: <z​mike.> My b
22:45 fdobridge: <g​fxstrand> tractored?
22:46 fdobridge: <g​fxstrand> One sec. I'll fix it.
22:49 fdobridge: <z​mike.> Tractored is... some slang I picked up somewhere and can't even remember, I guess
22:49 fdobridge: <z​mike.> i.e., I threw a tractor at your MR
22:50 fdobridge: <z​mike.> Tractored is... some slang I picked up somewhere and can't even remember where, I guess (edited)
23:29 fdobridge: <g​fxstrand> Looks like it's sparse textureGatherOffset that's not working
23:29 fdobridge: <g​fxstrand> That's at least really specific
23:32 fdobridge: <z​mike.> 🙏
23:34 fdobridge: <g​fxstrand> Maybe we can just tell nir to lower that one. 😅
23:35 fdobridge: <z​mike.> Reminds me of when ANV discovered txf was broken for mutable format image views because somehow there was no CTS for it
23:44 fdobridge: <g​fxstrand> @zmike. Is there a debug flag to make Zink dump out SPIR-V assembly?
23:46 fdobridge: <g​fxstrand> nvm, I got it out of spirv_to_nir
23:47 fdobridge: <z​mike.> ZINK_DEBUG=spirv
23:47 fdobridge: <z​mike.> All the debug flags are documented in docs/
23:51 fdobridge: <g​fxstrand> Hrm... IDK why I couldn't find the Zink ones.