00:52anarsoul: imirkin: apparently there's only 2 settings for mipfilter, linear and nearest
00:52anarsoul: so when we get TEX_MIPFILTER_NONE we have to adjust max_lod
00:53anarsoul: as for min_lod/max_lod that's just artifact of old code... guess I need to set it to sampler->min_lod and sampler->max_lod
00:56anarsoul: ah, it won't work since we attach only levels starting from base.u.tex.first_level
00:56anarsoul: guess it needs to be fixed too
01:27okias[m]: Hello guys. Do these days have DRM_VGEM any impact under llvmpipe under ARM?
01:27okias[m]: I wonder if make sense compile this inside kernel to get increased llvmpipe performance under tegra device. kernel 5.5.0-rc5, mesa 19.3, but can use -git
01:28okias[m]: also it's wayland only
01:28airlied: okias[m]: nope
01:29okias[m]: thanks, so ...as used by Mesa's software renderer for enhanced performance.... is not valid in general anymore or only for my usecase?
01:30airlied: not sure it ever got written :)
01:31okias[m]: ok. Any idea what could help for better llvmpipe perf? any useful trick?
01:34airlied: okias[m]: nothing that doesn't involve profiling and coding
01:35airlied: okias[m]: not sure how good the LLVM code produced on aarm64 is etc
01:35okias[m]: airlied okey, I think then I'll hope someone picks up tegra gallium driver (stuck on GL 1.4, so not much useful :D )
01:35okias[m]: this is armv7, so not even 64
01:36airlied: oh then yeah a real gpu driver would be a much better investment
01:36okias[m]: it's sad that there is not much bored people with RE & GPU knowledge :) ... probably because it's damn hard
01:36airlied: old tegra is also a bit of a dead end
01:36airlied: since they used nvidia gpu cores in newe trones
01:37okias[m]: airlied well, I have pretty nice working tablet these days, with 5.5 kernel. Only real pain is missing 3D acceleration, since I'm using Purism Phoc/Phosh and gnome based stuff
01:38okias[m]: rest of tablet (for it's age - Nexus 7, 2012) is pretty alive
01:38okias[m]: general tegra support inside mainline kernels it's in very good shape
01:40okias[m]: I was suprised that even with llvmpipe (which ugly utilize cores) it works approximatelly similiar to Android 7. When considering, that it could have accelerated 3D, so cpu gets cycles to spend on their work, it could be pretty quick
01:43okias[m]: sorry for OT. Anyway thanks for info :) I'll at least try in next few days rebase tegra mesa tree against master. glxgears still spinning even when jumping to 19.3 branch with it,
08:22MrCooper: airlied: might have been worth clarifying that while libGL links against X libs, it can work without an X server with EGL
10:53tomeu: MrCooper: anholt_: are you ok with the changes in https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295 to the common CI scripts?
14:07siro__: Hi, I found a bug in the kernel's displayport MST code and would like to fix it, but I need the displayport 1.3/1.4 spec. Can you point me to a place where I can obtain it for free?
14:08imirkin_: afaik you have to be a member of VESA
14:08imirkin_: some stuff *has* become open recently though ... like CTA-861-G or so
14:09imirkin_: but i don't think the DP one is open at this point
15:58udovdh: fwiw: the crashes are perhaps no amdgpu issue: https://bugzilla.kernel.org/show_bug.cgi?id=206191
15:58udovdh: MrCooper, bnieuwenhuizen, Venemo
15:59Venemo: udovdh: interesting.
16:00MrCooper: can you capture the full output from the serial port? This is probably not going the be enough to diagnose the problem
16:10udovdh: the setup of the terminal was still in progress
16:10udovdh: I set it for one page of 144 lines but could not scroll back further
16:10udovdh: The call trace is identical to my linux-kernel post
16:10udovdh: the rest is new
16:11udovdh: so sometimes it can continue
16:11udovdh: and mostly it cant
16:30udovdh: I updated the setup and SAVED it this time... so that the scrollback will be in place after powerdown/up
16:30udovdh: one 144 line page and wordwrap enabled...
16:31udovdh: but I guess this is getting offtopic for the topic here
19:26seanpaul: ramaling: just noticed drm_setup_hdcp_srm(), it takes the sysfs class, but doesn't use it? seems like maybe a previous iteration used sysfs and it still has some remnants?
19:29seanpaul: ramaling: i'm also unsure why this is managed via a global... looks like the firmware file is read every time srm is checked
19:34mdnavare: vsyrjala: Looking at your comments on the adaptive sync limits patch, your comment suggest using if (!version_greater(...)), but if edid->version == 1 and edid->revision > 1 then it should be fine, so how did you suggest simplifying it?
19:37mdnavare: hwentlan: Could you have Nicholas take a look at this as well: https://patchwork.freedesktop.org/patch/347704/?series=68489&rev=2
19:38mdnavare: hwentlan: Wanted to know how this would be used insude amdgpu
19:40agd5f_: seanpaul, HDCP 2.x requires that the srm be updated by the driver
19:40agd5f_: in case there are new revocations
19:41agd5f_: there's not really a good kernel interface to manage this
19:41seanpaul: agd5f_: sure, but that doesn't require a global revocation list, right? can't you just read the firmware file in-place whenever you need it checked?
19:42agd5f_: you need a userspace helper to save and restore the srm in the case of suspend/resume or reboot
19:43seanpaul: am i missing some magic then? i'm specifically asking about: why srm_data needs to be a global var?
19:44seanpaul: instead of just doing the allocation in drm_hdcp_check_ksvs_revoked()
19:45seanpaul: seems like that would eliminate the need to have that init() function in sysfs_init() (i don't think it belongs there since there's nothing using sysfs in the srm code), and would also eliminate the need for that mutex (and serializing drm devices)
20:01agd5f_: seanpaul, oh, that I'm not sure about. I think the thinking was that everyone would use the same srm
20:03seanpaul: agd5f_: sorry for being vague at first. everyone using the same srm seems achieved by using the firmware file to distribute it
20:13hwentlan: mdnavare: i image we can just call drm_get_adaptive_sync_limits in amdgpu_dm_update_freesync_caps and then change any of the amdgpu_dm_connector->min/max_vfreq uses to go to drm_display_info instead
20:18hwentlan: agd5f_, seanpaul: i remember our psp guys didn't like the idea that every driver would use the same srm. not 100% sure why. maybe since content protection needs to be reviewed by a vendor throughout the stack and a possible interaction between two drivers might be undesirable.
20:18hwentlan: i'd prefer a non-global SRM... but then, we're not even doing SRM check in kernel
20:22seanpaul: hwentlan: i don't have strong feelings on whether srm should be per-device or subsystem-wide, but i am a bit concerned about that mutex allowing one drm device from blocking another from checking srm
20:23seanpaul: s/from blocking/to block/
20:24hwentlan: don't you need a mutex to synchronize the SRM if it's subsystem-wide?
20:24seanpaul: hwentlan: the information in srm_data isn't shared between devices, afaict, it's completely repopulated every time someone checks revocation
20:25seanpaul: so it'd be the same as just reading the fw file per-device
20:25seanpaul: 1 fw file == subsystem wide srm, but doesn't necessitate devices block each other while they read it
20:27seanpaul: worth noting that i'm just flying by, so there's probably some implementation detail i'm missing... i just saw the code and wondered if there was a reason for it
20:50jekstrand: daniels: panfrost CI is failing for me about 50% of the time. Marge is not happy. :-(
20:52Lyude: she looks fine to me https://en.wikipedia.org/wiki/Marge_Simpson#/media/File:Marge_Simpson.png
20:55daniels: jekstrand: links please?
20:56daniels: everything on https://gitlab.freedesktop.org/mesa/mesa/pipelines/ is currently happy
20:56jekstrand: daniels: https://gitlab.freedesktop.org/jekstrand/mesa/-/jobs/1342295
20:59daniels: jekstrand: thanks for letting me know. looks like 2 out of 3 of our Chromebooks have either a non-responsive power unit or a dead USB hub. chasing our admins to disable them now, and if that doesn't work out in a reasonable time I'll just push something to disable T860 for the meantime.
21:02daniels: jekstrand: right, bad devices are currently blacklisted. really not sure why LAVA didn't pick the failures up and schedule a health check. have asked our admins to figure out why that is. thanks for letting me know!
21:03jekstrand: daniels: yw
21:07kisak: daniels: might be worth giving !3347 ( https://gitlab.freedesktop.org/daniel-schuermann/mesa/pipelines/96676 ) a quick check too
21:08daniels: kisak: thanks!
21:21kallisti5: anyone have a few seconds to review https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3324 ?
21:21kallisti5: (it's a quick one... just build fixes) I can push but need a sign-off :-)
21:33karolherbst: anybody any idea how bootstraping the GPU (like loading firmware) can be skipped when the GPU gets runtime resumed while the process gets killed and the filesystem stuff is already teared down?
21:36Lyude: karolherbst: maybe keep a ref to the dentry for the firmware, and release it when the application closes?
21:37karolherbst: Lyude: well, the files get accessed while the application gets killed by the kernel
21:37karolherbst: the fs stuff is already cleaned up at that point
21:37Lyude: karolherbst: I mean ahead of time before the application is killed, so that you can go back to it later once the process is dying instead of trying (and failing) to look it up again
21:37karolherbst: the kernel wants to kill all kernel tasks, but we have some stale ones which might trigger the GPU to get woken up
21:37Lyude: although I'm not sure how the firmware helpers in the kernel work
21:38karolherbst: Lyude: the fs is gone, so all dentries should be stale, no?
21:39Lyude: karolherbst: dunno :S, didn't think a dentry could go stale
21:39karolherbst: Lyude: https://elixir.bootlin.com/linux/v5.5-rc6/source/kernel/exit.c#L802 is where the fun starts
21:39karolherbst: exit_files and exit_fs being called before kind of gives me the feeling you don't want to access any files anymore
21:39karolherbst: exit_mm a few lines above as well
21:40karolherbst: but that might be fine anyway
21:44daniels: jekstrand: i cancelled https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3366 as you're about to lose a race to https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3363
21:44daniels: (i assigned them both at the same time, but marge picked the latter first)
21:45daniels: (cancelled ... the CI pipeline of ...)
21:54jhli: Someone mind merging this getfb2 patch? https://patchwork.freedesktop.org/patch/345498/
21:54jhli: got reviewed, I just don't have commit access
22:06agd5f_: karolherbst, cache the fw in the driver?
22:06karolherbst: agd5f_: yeah.. that's probably the best idea, but I think we would just need to load all fw when the driver gets loaded and just use that
22:07karolherbst: but I really don't know how the firmware API works ..
22:18agd5f_: karolherbst, if you call request_fw(), IIRC, the kernel caches a copy for you
22:18karolherbst: yeah... I just found that
22:18karolherbst: but.. it seems like we don't do that
22:18agd5f_: you only need to call it again if you've called release_fw()
22:19karolherbst: yeah.. I think I need to read some code
22:22karolherbst: okay... found the problem
22:23karolherbst: we just call release_fw immediately after loading the firmware
22:26daniels: if anyone's wondering why CI throughput is so bad currently: four people pushed 6 new branches between them, nearly simultaneously. some were based on top of the just-merged MR to bump the ARM kernel version; rebuilding kernel/deqp/etc takes ages. there should be 3-5 Panfrost T860 devices but right now there's only one. and the kernel just merged a change which makes boot hard-hang, so there's a lot of waiting.
22:27imirkin_: aka "the perfect storm"?
22:28daniels: well, we haven't (yet) been gifted an inexplicably slow network route, so that's something
22:28imirkin_: something to look forward to tomorrow then
22:29daniels: (that being said, we are currently in an extended argument with our Cambridge ISP about why an inability to get more than 1.2MB/sec throughput from Google is very definitely their problem, as opposed to Google deciding based on a hash of the source IP to send them down a really really slow route, which is a novel contention)
22:31anarsoul: tomeu: btw thanks for updating kernel in lava lab, looks like it fixed gpu error recovery issues on lima
22:32anholt_:wishes lava lab could update rpi firmwares, would love to do vc4 testing.
22:38daniels: anholt_: assume that requires writing to an SD card?
22:38anholt_: unless you're using the firmware's netbooting support to load your firmware and u-boot
22:38daniels: tomeu: i've just realised that the lava container+build jobs are cross-compiling from x86. given that we can really easily add a fair bit more ARM build capacity, it would be good to try moving those back to aarch64-native and seeing what the performance is like.
22:38daniels: anholt_: ooh, yes please
22:39anholt_:did all the pi3 work cardless
22:41daniels: +++++ on fdno CI availability btw, they've been really quite responsive recently
22:42anholt_: daniels: we're working on getting even better! there's a big old rack full of a setup that we're going to use to hopefully do lava db410c, db820c, and more chezas than before (so we can start testing vulkan)
22:44daniels: \o/ \o/
22:44daniels: tbf it seems at this point like piglit is mostly the limiting factor for throughput anyway, based on unscientific eyeball sampling
22:44daniels: (apart from today where the limiting factor is everything all at once)
22:45anholt_: I keep hoping that gitlab will sort out their kubernetes, and I'll just turn on dedicated mesa x86 capacity again
22:46anholt_: also, I think nir-to-tgsi might cut our softpipe runs a bunch :)
22:47daniels: anything up your sleeve for piglit-quick_gl?
22:47daniels: somewhat of a misnomer that one
22:47daniels: (or does piglit run on softpipe rather than llvmpipe?)
22:47anholt_: I think we're running the piglit on llvmpipe only currently
22:48anholt_: haven't looked into perf there. we should probably have our piglit runs be doing a report at the end of the slowest subtests
22:48anholt_: so we can go fix or ban things
22:49daniels: there, looks like the bad performance bubble has passed
23:03daniels: yeah, <13min end to end (with piglit-quick_gl again the slowpoke) seems pretty reasonable
23:29mdnavare: hwentlan: yes we could call that in amdgpu_dm_update_freesync_caps but then j4ni was also suggesting making it static because it gets called from drm_add_edid_modes() where it will populate the adaptive sync info into the drm display info, is that something that gets called in amdgpu on conn_init() then we can avoid explicitly calling drm_get_adaptive_sync_limits from amdgpu_dm_update_freesync_caps
23:45daniels: anholt_: is wales on the other end of a 14.4k modem?