ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
cascardo_ has joined #dri-devel
MrCooper_ has joined #dri-devel
MrCooper has quit [Read error: Connection reset by peer]
cascardo has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
jannh has quit [Remote host closed the connection]
ity1 has joined #dri-devel
ity has quit [Ping timeout: 480 seconds]
guludo has quit [Ping timeout: 480 seconds]
xroumegue has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
MrCooper_ has quit [Read error: Connection reset by peer]
MrCooper has joined #dri-devel
<Fya>
Thanks jenatali. I found the llvmpipe json file name. (lvp_icd.x86_64.json) Which I looked up in pkgfile. The package I needed was "extra/vulkan-swrast".
<Fya>
Cheers.
vliaskov_ has quit [Ping timeout: 480 seconds]
jannh has joined #dri-devel
<kisak>
My understanding is that lavapipe was designed so that it could be backed by different implementations and coincidentially only has llvmpipe backing it right now, which is why it shows as llvmpipe when asked by tools.
heat has quit [Read error: Connection reset by peer]
heat has joined #dri-devel
ZLangJIT has joined #dri-devel
ZLangJIT is now known as androidui
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit [Remote host closed the connection]
kts has quit [Quit: Konversation terminated!]
lynxeye has joined #dri-devel
coldfeet has quit [Quit: Lost terminal]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
apinheiro has joined #dri-devel
heat is now known as Guest1909
Guest1909 has quit [Remote host closed the connection]
heat has joined #dri-devel
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
rgallaispou has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
jkrzyszt has quit [Ping timeout: 480 seconds]
feaneron has quit []
feaneron has joined #dri-devel
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
feaneron has quit [Quit: feaneron]
Calandracas has quit [Remote host closed the connection]
feaneron has joined #dri-devel
Calandracas has joined #dri-devel
feaneron has quit []
feaneron has joined #dri-devel
<tzimmermann>
jfalempe, i'd just leave it the parameter blank. once you commit to 'none' or any other string you cannot go back.
hansg has joined #dri-devel
<tzimmermann>
but your 'none' comment made me thought that we might want something like 'blank' at soem point. it would init and clear the display without further output
<tzimmermann>
that could easily be implemented as DRM client
<tzimmermann>
no idea if that is useful
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
heat is now known as Guest1916
heat has joined #dri-devel
dt9 has joined #dri-devel
Guest1916 has quit [Read error: Connection reset by peer]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
kaiwenjon has quit [Quit: WeeChat 3.8]
kaiwenjon has joined #dri-devel
feaneron has quit []
feaneron has joined #dri-devel
Company has joined #dri-devel
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
hansg has quit [Quit: Leaving]
mehdi-djait339 has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
siak has joined #dri-devel
mehdi-djait33 has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
<thellstrom>
tursulin: There appears to be a conflict in the drm-tip drm-intel-next merge that stops me from fixing the conflict in the drm-xe-next merge. Is that from your drm-intel-fixes picks?
<tursulin>
thellstrom: quite possibly, I left push-branch unattended and forgot about it
heat is now known as Guest1920
heat has joined #dri-devel
tejasupa_ has quit [Remote host closed the connection]
Guest1920 has quit [Read error: Connection reset by peer]
<thellstrom>
OK. I'll see if it's possible to temporarily use an override commit for drm-intel-fixes to resolve drm-xe-next.
kaiwenjon has quit [Remote host closed the connection]
kaiwenjon has joined #dri-devel
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
feaneron has quit [Quit: feaneron]
guludo has joined #dri-devel
feaneron has joined #dri-devel
guludo has quit []
guludo has joined #dri-devel
<tursulin>
thellstrom: I am compile testing the conflict resolution
<tursulin>
expect to be able to push it shortly
myhoner has joined #dri-devel
<thellstrom>
tursulin: I think rodrigo already pushed something there. Although I'm a bit afraid my xe conflict resolution might have resolved also the intel one in an incorrect way.
<thellstrom>
Let me see what happens when I run rebuild-tip.
<stsquad>
can anyone explain what the following means?
<stsquad>
# glxinfo -B -display :0
<stsquad>
name of display: :0
<stsquad>
Error: couldn't find RGB GLX visual or fbconfig
myhoner has quit []
<stsquad>
I'm trying to fix buildroot's Glxinfo test before writing one for vkmark - but it relies on an X session starting and then tickling it from the serial console
<stsquad>
I can see X is confused looking for swrast which is deprecated
<tursulin>
thellstrom: oh... my went through so lets hope there isn't a 3-way confusion now
* stsquad
also wonders how such a test might work with wayland/weston needing to be up to run vkmark
<tursulin>
rodrigovivi: you fixed the drm-tip conflict in intel_dsb.c before me?
<thellstrom>
rodrigovivi: tursulin: Now everything merges fine and the xe conflict is gone, so we just need to check the intel one is correctly resolved.
<thellstrom>
If not we probably need to revert my drm-rerere commit and I'll push a better one.
coldfeet has joined #dri-devel
<thellstrom>
rodrigovivi: tursulin: AFAICT everything looks ok.
<pq>
stsquad, weston can run with its headless-backend, for instance. Then it's completely self-standing, no need for DRM KMS or any parent window system, while still using GPU hw drivers or llvmpipe as needed.
Kayden has quit [Quit: Leaving]
Guest1903 has quit []
<pq>
stsquad, you could use weston/headless to run Xwayland in order to test X11 clients with hw accel or llvmpipe.
Kayden has joined #dri-devel
warpme has joined #dri-devel
<pq>
or rather let weston start Xwayland automatically as needed.
<stsquad>
pq: I don't suppose you can point at any example headless invocations?
Calandracas has quit [Ping timeout: 480 seconds]
warpme is now known as Guest1925
<pq>
hmm, weston's own test suite does that, but it's a bit tangled off-hand. I don't suppose Mesa had a test?
<stsquad>
I guess it would be something like: weston -B headless -- vkmark
<pq>
stsquad, the main things are --backend==headless --renderer=gl
<pq>
something like that, yeah
<pq>
oops, should be --backend=headless
coldfeet has quit [Quit: Lost terminal]
Guest1925 has quit [Ping timeout: 480 seconds]
<pq>
you may want --width= and --height= too for the resolution
<thellstrom>
rodrigovivi: tursulin: Looks like there is a compilation failure in intel_dsb.c, though.
<pq>
stsquad, and --refresh-rate=
<pq>
those are all in 'man weston'
nerdopolis has joined #dri-devel
<pq>
stsquad, the default shell is 'desktop'. If that causes inconvenience by its window management opinions, you can try if --shell=kiosk is better.
Calandracas has joined #dri-devel
<pq>
stsquad, most of these and more can be set in a weston.ini file, too.
<tursulin>
thellstrom: curious because I built it before to check and built it just now again
dsimic is now known as Guest1927
dsimic has joined #dri-devel
<daniels>
also you really want --idle-time=0 if you're on d-s
Guest1927 has quit [Ping timeout: 480 seconds]
<thellstrom>
tursulin: It might be there were more pushes since I rebuilt. Let me check.
<thellstrom>
tursulin: If I run dim -d rebuild-tip and then compile the resulting drm-tip, then I still see a compilation failure.
<tursulin>
thellstrom: oops I was building with the wrong .config :facepalm:
<tursulin>
I guess rerere is then bad
sguddati has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
<tursulin>
I am reverting Rodrigo's rerere commit and re-doing it, stay tuned
mehdi-djait339 has quit []
mehdi-djait339 has joined #dri-devel
sguddati has quit [Ping timeout: 480 seconds]
<tursulin>
thellstrom: should be fine now
YuGiOhJCJ has joined #dri-devel
kts has joined #dri-devel
<thellstrom>
tursulin: Yes, looks ok!
<stsquad>
looks like weston -B headless --renderer=gl --shell=kiosk -- vkmark does the trick
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
pcercuei has joined #dri-devel
_whitelogger has joined #dri-devel
airlied has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
warpme is now known as Guest1932
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
Daanct12 has quit [Quit: WeeChat 4.4.4]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
feaneron has quit []
feaneron has joined #dri-devel
mehdi-djait339 has quit []
mehdi-djait339 has joined #dri-devel
nerdopolis has quit [Read error: Connection reset by peer]
kts has quit [Quit: Konversation terminated!]
nerdopolis has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
hansg has joined #dri-devel
Kayden has quit [Quit: Leaving]
ickle has joined #dri-devel
Kayden has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
dolphin has quit [Quit: Leaving]
DodoGTA has quit [Quit: DodoGTA]
Caterpillar has quit [Quit: Konversation terminated!]
davispuh has joined #dri-devel
JLP has quit [Ping timeout: 480 seconds]
DodoGTA has joined #dri-devel
caitcatd- has joined #dri-devel
caitcatdev has quit [Ping timeout: 480 seconds]
Sid127 has quit [Ping timeout: 480 seconds]
epoch101 has joined #dri-devel
Sid127 has joined #dri-devel
JLP has joined #dri-devel
siak has quit []
rasterman has quit [Quit: Gettin' stinky!]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
bolson has joined #dri-devel
hexa- has quit [Quit: WeeChat 4.4.3]
kasper93_ has joined #dri-devel
hexa- has joined #dri-devel
kasper93 has quit [Ping timeout: 480 seconds]
gryffus has joined #dri-devel
feaneron has quit [Read error: Connection reset by peer]
feaneron has joined #dri-devel
jsa1 has quit [Ping timeout: 480 seconds]
<gryffus>
Hey guys, I tried to build the newest version of AMDVLK on my system (Mesa 24.3.0 and kernel 6.11.8), but I keep getting "terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib64/amdvlk64.so. Skipping this driver." error when trying to launch vulkaninfo with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd.x86_64.json. Anyone has a clue what could be wrong or where should I look for problems?
ity has quit [Remote host closed the connection]
<HdkR>
gryffus: Mesa doesn't cover amdvlk so you may not get much help here
<Company>
and -3 is VK_ERROR_INITIALIZATION_FAILED
<Company>
and that error is from libvulkan itself
<Company>
so you will have to make the AMD driver dispense more information somehow
<gryffus>
HdkR: I know, but I could get at least some hints, like Company did :))
<HdkR>
gryffus: Hopefully it is just the issue that amdvlk aggressively cuts out older GPU compatibility. So it only claims support for RX 5000/6000/7000 today.
<gryffus>
HdkR: I am running "[AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev d1)" which should be supported
<HdkR>
gryffus: AMD dropped polaris and vega support back in October of last year
<HdkR>
Would need radv instead of amdvlk
<gryffus>
Meh.... So I was googling outdated info :( Ok, thanks so much for clarification HdkR and sorry for wasted time :x :D
<HdkR>
At least Vega is Vulkan 1.4 conformant in radv
feaneron has quit [Quit: feaneron]
<gryffus>
Yeah I did not have any stability issues or such, I just wanted to benchmark my system and compare the two drivers, expecially on ray tracing (trying phoronix test suite)
feaneron has joined #dri-devel
<gryffus>
But yeah it makes total sense why the 2023 AMDVLK worked and recent did not :(
<gryffus>
Thanks for the help anyway... And RADV for the win! :)
gryffus has quit [Quit: Konversation terminated!]
ity has joined #dri-devel
karenw has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
feaneron has quit []
feaneron has joined #dri-devel
rgallaispou has left #dri-devel [#dri-devel]
<rodrigovivi>
tursulin: sorry for the mess and thanks for fixing it...
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
Guest1932 has quit []
vliaskov__ has quit [Ping timeout: 480 seconds]
vliaskov__ has joined #dri-devel
Duke`` has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
jkrzyszt has quit [Ping timeout: 480 seconds]
<robclark>
tursulin: idk if you often have kmemleak check enabled? I'm seeing job leaks due to what appears to be ->job_free() not getting called after job_run() returns for dynamically torn down schedulers/entities. Not sure if this rings a bell?
<tursulin>
robclark: I normally do but it doesn't ring a bell I'm afraid. The only reported leaks I vaguely remember seeing rather regularly are about drm connectors, I think. And that is with amdgpu.
<tursulin>
And if you think vaguely and regularly are a contradiction it is only because for the last few weeks I was in a phase where I had to turn of debugging aids.
<tursulin>
rodrigovivi: no worries, it was a silent conflict and I can totally understand not feeling the need to build test after fixing a comment :)
<robclark>
hmm, I kinda suspect that drm_sched_entity_flush() is maybe only flushing things as far as job_run() but not job_free()? I guess I'm going to have to actually look at how this works again
fab has quit [Ping timeout: 480 seconds]
sukuna has joined #dri-devel
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
<tursulin>
robclark: I think so, running jobs ("scheduled"/job_run() executed) will be freed asynchronously when fence callback schedules the free worker
<tursulin>
modulo any known (not to me) and unknown bugs
karenw has quit [Ping timeout: 480 seconds]
<robclark>
tursulin: in this case, it is for vm_bind queue some returned fence is NULL.. but that should be a pretty common pattern, so I'm a bit surprised that no one noticed this yet.
<tursulin>
robclark: which driver you are talking about?
foo_anon has joined #dri-devel
foo_anon has quit []
<robclark>
tursulin: msm (with not yet posted patches).. but I guess it should be similar with other drivers using gpuvm + sched based vm_bind queue
<tursulin>
I think Philipp Stanner was looking into the flush and fini "funs".. don't know his nick here
rasterman has joined #dri-devel
fab has joined #dri-devel
rsalvaterra_ has joined #dri-devel
rsalvaterra_ is now known as rsalvaterra
tzimmermann has quit [Quit: Leaving]
Ryback_ has quit [Remote host closed the connection]
Ryback_ has joined #dri-devel
lstrano has quit [Remote host closed the connection]
lstrano has joined #dri-devel
unerlige has quit [Ping timeout: 480 seconds]
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit []
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
zenmov has joined #dri-devel
lynxeye has quit [Quit: Leaving.]
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
rsalvaterra_ has joined #dri-devel
rsalvaterra_ is now known as rsalvaterra
rasterman has quit [Quit: Gettin' stinky!]
rsalvaterra has quit []
rsalvaterra has joined #dri-devel
cphealy has joined #dri-devel
<robclark>
tursulin: ok, so calling drm_sched_stop() before drm_sched_fini() seems to resolve it
<alyssa>
if the is_used_by_float has denorms preserved by the builder default flushes denorms, the rule is unsound. can that.. happen?
<alyssa>
the short answer is that "denorm preserve cannot change per-instruction, so it's fine"
<alyssa>
fair enough. I guess it's fine then
unerlige has joined #dri-devel
<glehmann>
yeah, denorm mode per instruction would be mildly insane
<alyssa>
tbf so is signed zero / nan per instruction
<alyssa>
like I know how we got here but still
vliaskov_ has joined #dri-devel
<glehmann>
I'd argue that those are useful per instruction
<glehmann>
and we should really everything but the per instruction flags from nir
<glehmann>
...something for next year me, I guess
epoch101 has quit [Ping timeout: 480 seconds]
airlied has joined #dri-devel
<alyssa>
Parsing error on line 2
vliaskov__ has quit [Ping timeout: 480 seconds]
<glehmann>
the missing verb is remove
<alyssa>
ah
zenmov_ has joined #dri-devel
zenmov has quit [Ping timeout: 480 seconds]
<glehmann>
and then I want to write a pass that removes flags if inputs/outputs can never be nan/inf or if signed zero doesn't matter, to allow more optimizations for dxvk/vkd3d-proton
feaneron has quit [Read error: Connection reset by peer]
feaneron has joined #dri-devel
pochu has quit [Quit: reboot]
pochu has joined #dri-devel
<alyssa>
ooh, yeah
haaninjo has joined #dri-devel
<alyssa>
dovetails nicely with nir_opt_varyings, I assume
karenw has joined #dri-devel
Fya has quit []
jsa1 has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
coldfeet has quit [Quit: Lost terminal]
hansg has quit [Quit: Leaving]
feaneron has quit [Read error: Connection reset by peer]
feaneron has joined #dri-devel
zenmov_ is now known as zenmov
feaneron has quit []
feaneron has joined #dri-devel
<dcbaker>
cwabbott: I've got "1b42bc76da ir3: Fix reload_live_out() in shared RA" nominated for 24.3, but there's been enough changes between the branchpoint and now it needs a backport to apply. Do you want to send a backport PR, or do you want me to drop it?
<dcbaker>
olv: ping regarding "d35002949 panvk: expand top-of-pipe and bottom-of-pipe"
<dcbaker>
hakzsam: I think I forgot to ping you about "08c9dca8db radv: fix skipping on-disk shaders cache when not useful", which is nominated for 24.3 and doesn't apply. Do you want to provide backport PR, or do you want me to drop it?
feaneron has quit [Quit: feaneron]
feaneron has joined #dri-devel
feaneron has quit []
feaneron has joined #dri-devel
<cwabbott>
dcbaker: it's a trivial backport, git just gets nervous that the line after the hunk I added was changed on main compared to 24.3 but it's fine
<alyssa>
"Unexpected exception in bot while handling this MR'
<alyssa>
*some* MRs are getting thru so it's not a total Marge outage
<alyssa>
uh.. -> #freedresktop i guess
zenmov has quit [Ping timeout: 480 seconds]
<dcbaker>
cwabbott: looks great, and its the right branch :) It looked like one of the functions had changed number of arguments? Thanks for doing the backport
<dcbaker>
olv: okay, I'll drop it then
<cwabbott>
dcbaker: the function called right after the hunk I added had changed the number of arguments
<cwabbott>
but that doesn't matter for what the change is doing
<dcbaker>
ahhh, for some reason that looked like it was part of the change when I looked at the diff