ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
shashanks_ has quit [Ping timeout: 480 seconds]
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
heat_ has joined #dri-devel
heat has quit [Remote host closed the connection]
heat_ has quit []
heat has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
heat has quit [Ping timeout: 480 seconds]
darkglow has joined #dri-devel
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
Company has quit [Remote host closed the connection]
kts has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
crabbedhaloablut has joined #dri-devel
Warr has joined #dri-devel
Warr has quit []
<neatversion>
I was stupid anyway, so gpio writes are conditional, they can not be treated without separate pass, if branching is already separate, so what to do is, have the globals memory stretched to twice the size in hash, just knowing the mask is at higher value, you can shrink the empty space by adding to that offset which needs to be the highest of them all, so in other words globals get dynamically appended, but their content is referencing
<neatversion>
the structures like register banks after elimination
<mupuf>
the radeonsi-gl jobs need to be trimmed down: they run in 20-25 minutes when things go well, at push on 45 when a retry is attempted. That's too high and almost got my MR on an otherwise-idle system to run over the 1h mark
<mupuf>
DavidHeidelberg: do you know who I should contact here?
CATS has quit [Read error: Connection reset by peer]
<mupuf>
Additionally, we probably should not be running radeonsi testing when modifying expectations for radv. That part should be easy to fix
CATS has joined #dri-devel
<mupuf>
and ci-fairy seem like it could do with more retries and shorter timeouts
flto has quit [Remote host closed the connection]
<neatversion>
Dynamic branches can be handled, I think I was tired to land such a contradictive sentence, branching is controlled by data dependence graph i.e incoming data path, however yes it can be done, Gini does it too but I try again to make it even shorter, and since all other code works, there's nothing than jackpot to left to be targeted anyways.
flto has joined #dri-devel
<neatversion>
Most interesting is that it really does not care as to when things get added in case you do some offset/index combination linear algebra, it just permutes things back in place at any time you eliminate correct values, but having globals or gpio at different sizes allows you to separate them to be loaded in from dma and written back from dma, that's the approach needed.
kts has joined #dri-devel
<neatversion>
Also ioctl concern was real, when malloc can be transformed to any local pool allocator, than ioctl can not be, it needs to make the same call
<neatversion>
And that has to be done on CPU, demangler can not achieve this on dma either, cause dma on CPU has no scratch access to registers
Duke`` has joined #dri-devel
sima has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
<neatversion>
Hence technically templeos writer, Sarah Sharp, and this systemd guy, are all correct, as much as or the more in userspace the better it is on modern computing. That would perform lot better, so to call me terry, his only flaw was fighting the linuxwall , nv35 driver did lots in userspace too, it really died out perhaps too, terry was very intelligent otherwise , he was very correct, but I ain't gonna put up a fight, it's just clear
<neatversion>
that women are whores and the particular monster was only gold digging at me and ordered by other dorks to finish me off, not much I fight there my people ban her all and her other humiliators, it's not a fight I just do not give any pennies to them.
kzd has quit [Quit: kzd]
<neatversion>
I actually assume that there are some projects that take Linux kernel and just make libraryos or realtime os libs out of them.
<neatversion>
Normally you'd be restricted to gpl there due to those, but anyhow solver based transformations really do not have any laws to cling to
kts has joined #dri-devel
fab has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
i-garrison has quit []
i-garrison has joined #dri-devel
neatversion was kicked from #dri-devel by ChanServ [You are not permitted on this channel]
pochu has quit [Ping timeout: 480 seconds]
itoral has joined #dri-devel
<dj-death>
people are aware of the trace problems on CI with "502 Bad Gateway" ?
<DavidHeidelberg>
dj-death: ".a618-traces" in "a618-traces-performance"
<dj-death>
I bet it's everywhere
rgallaispou has joined #dri-devel
vliaskov__ has joined #dri-devel
jkrzyszt has joined #dri-devel
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
tursulin has joined #dri-devel
mripard has joined #dri-devel
pcercuei has joined #dri-devel
<daniels>
well yeah, if we can’t access the s3 server, then everything which touches it needs to be killed
<DavidHeidelberg>
dj-death: bentiss fixed it, should be working
mripard has quit [Quit: mripard]
pekkari has quit [Quit: Konversation terminated!]
<dj-death>
DavidHeidelberg: nice, thanks
youmukonpaku1337 has quit [Remote host closed the connection]
vliaskov_ has joined #dri-devel
youmukonpaku1337 has joined #dri-devel
jfalempe has joined #dri-devel
vliaskov__ has quit [Ping timeout: 480 seconds]
sarahwalker has joined #dri-devel
apinheiro has joined #dri-devel
tyalie has quit [Ping timeout: 480 seconds]
sarahwalker has quit [Ping timeout: 480 seconds]
sarahwalker has joined #dri-devel
hansg has joined #dri-devel
tyalie has joined #dri-devel
JohnnyonFlame has joined #dri-devel
donaldrobson has joined #dri-devel
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
Haaninjo has joined #dri-devel
Danct12 has quit [Ping timeout: 480 seconds]
rasterman has joined #dri-devel
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
sauce has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
cmichael has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
Danct12 has joined #dri-devel
junaid has quit [Remote host closed the connection]
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #dri-devel
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
elongbug has joined #dri-devel
Company has joined #dri-devel
robmur01 has quit [Ping timeout: 480 seconds]
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
vliaskov has joined #dri-devel
vliaskov_ has quit [Ping timeout: 480 seconds]
hansg has quit [Ping timeout: 480 seconds]
youmukonpaku1337 has quit [Remote host closed the connection]
youmukonpaku1337 has joined #dri-devel
imre has quit [Ping timeout: 480 seconds]
hansg has joined #dri-devel
junaid has joined #dri-devel
rgallaispou has quit [Remote host closed the connection]
robmur01 has joined #dri-devel
<MrCooper>
is there a proper way to check a plane's current state without using drm_atomic_get_plane_state?
itoral has quit [Remote host closed the connection]
jdavies has joined #dri-devel
jdavies is now known as Guest1929
<linkmauve>
Hi, how do you trigger the various GPU errors that can happen on i915?
<linkmauve>
Ideally only for one process of my choice.
<linkmauve>
But a full GPU reset could also be useful to test against.
kts has joined #dri-devel
<mlankhorst>
Look at IGT?
<linkmauve>
intel_gpu_abrt?
cmichael has quit [Quit: Leaving]
<linkmauve>
Ah, it uses /sys/class/drm/card1/device/reset according to tests/device_reset.c
<linkmauve>
Also /sys/class/drm/card1/device/power
<linkmauve>
Thanks, this was helpful. :)
<linkmauve>
Is there a way to create a per-context or per-process fault instead of a global GPU reset?
konstantin_ is now known as konstantin
youmukonpaku1337 has quit [Ping timeout: 480 seconds]
<linkmauve>
Haha, writing to /sys/class/drm/card1/device/reset made my whole screen not display anything, and the wifi was disconnected as well, I guess it crashed more than what I actually wanted. ^^'
mszyprow has joined #dri-devel
jmondi has quit [Read error: Connection reset by peer]
<alyssa>
there's no CL API, no kernel stuff whatsoever, and no libclc (to keep you from shooting your feet)
<karolherbst>
yeah, fair
<alyssa>
mostly just that CL is the magic word to compile big exisitng C code (like genxml) to NIR libraries
<alyssa>
and CL C is massively closer to cpu C than glsl/hlsl/etc are
<karolherbst>
commenting on some of the `SPV_` extension stuff.. we kinda need a better way of letting all of mesa know what we support... but uhh.. whatever, you can read the comment once I post it
<alyssa>
that's probably copypasta from intel_clc
<karolherbst>
yeah
<alyssa>
(glsl doesn't even support enums.............)
<alyssa>
and glsl + bda is really ugly imho.. and mesa glsl doesn't support bda so it'd be glslang... so since we need CL anyway, might as well get real pointers out of the deal...
<karolherbst>
right... though without bda it's even worse
<alyssa>
ye
<alyssa>
aesthetically this seems much better than the glslang stuff radv does
<karolherbst>
rusticl on zink even requires bda, because without it, it's just pain
<karolherbst>
I should also wire up the atomic float stuff in rusticl, I think there are CL extensions for it...
<karolherbst>
also.. do we support all of SPV_INTEL_subgroups?
<karolherbst>
seems like we don't handle SubgroupImageBlockIOINTEL
<alyssa>
iunno
<HdkR>
How soon until clc supports C++? :>
<karolherbst>
uhhhh
<karolherbst>
pain
<karolherbst>
alyssa: btw, there is also this idea I have in regards to libclc pre compiling and moving it into the mesa build system, but that could be pain and could mean we might end up compiling spirv to cached nir per generation of GPU or something. But I'm not sure if that's even a good idea, because the few seconds on initial startup isn't that expensive
<karolherbst>
just on my raspberry pi 4 with libasan enabled it takes like 5 minutes :D
<alyssa>
karolherbst: sure
<alyssa>
mostly i looked at the use cases for driver clc and concluded if you hit libclc for anything you're holding it wrong
<alyssa>
so made a deliberate choice not to link libclc
<alyssa>
oh no. no gamma functions. what shall i do
<karolherbst>
yeah, that fair. It's just that with all the static code we compile at runtime, it might also make sense to move some into mesa compile time, I just don't think it's really worth it for now
<karolherbst>
I'm mostly wondering if we'll ever do that
rsalvaterra has quit []
rsalvaterra has joined #dri-devel
<karolherbst>
alyssa: one thing _some_ drivers might run into: fma. If the driver sets `lower_ffma32`, we'd call into the libclc ffma function
<karolherbst>
*fma instead of `nir_ffma`
<karolherbst>
might want to pass in `-cl-mad-enable` as well..
<karolherbst>
so fmad can be optimized to ffma
<kisak>
morning karolherbst, sorry, I don't have any influence in that direction. tjaalton would be one step closer to maybe knowing where to ask about that.
<karolherbst>
kisak: okay.. I'm mostly just getting tired teeling the 5th user to file a downstream bug and nothing happens except more users running into the exact same bug :(
<kchibisov>
I'm just not familiar with r300/r400, so not sure what to expect from them.
flto_ has joined #dri-devel
flto has quit [Read error: Connection reset by peer]
flto_ has quit []
flto has joined #dri-devel
anujp has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
heat has joined #dri-devel
<karolherbst>
tjaalton: I see
<karolherbst>
tjaalton: well.. all I can say is, that those firmware files are fixing real issues and should be rolled out asap
<FLHerne>
kchibisov: valid bug, best-efforts but people do care for them
<karolherbst>
it's the 5th bug report on this, and always caused by those files not being updated
<karolherbst>
anyway, not using the updated firmware files won't give you any upstream support, because it's just a waste of time from upstream pov
kts has joined #dri-devel
kts has quit []
<karolherbst>
tjaalton: anyway.. the linked deb file doesn't contain the upstream firmware files, so I guess you should just talk it out with that user and explain how to test a fixed build
<tjaalton>
yeah he hijacked another bug
<tjaalton>
and is asking for something else really
junaid has joined #dri-devel
<karolherbst>
mhh?
<karolherbst>
what bug do you mean?
<tjaalton>
2e92a49f90 fixed it for the original (ubuntu bug) submitter
<karolherbst>
ahh, I see
<karolherbst>
anyway, I hope you all be able to figure it out and how to get the fixes shipped to all users
<tjaalton>
as long as the original submitter would reply after ~2 weeks :)
<karolherbst>
well, I can tell you that there won't be upstream support without those updates
<tjaalton>
and not this nonsense pingpong with lassi :P
<tjaalton>
sure
<tjaalton>
I'm not asking for that
<karolherbst>
just ship them, it's wasting our time that users don't use them
<karolherbst>
or rather don't have them
<tjaalton>
we have policies for stable updates
<karolherbst>
yeah, I don't care
<karolherbst>
it's critical to have those files, I can't really phrase it any differently
<karolherbst>
I'm tired of having to tell users that they should tell their distribution (whatever debian/ubuntu version) that those files aren't backported
Duke`` has joined #dri-devel
<karolherbst>
leave a comment with "upstream says those files _must_ be backported" if that helps
<karolherbst>
just get those files to users
pekkari has joined #dri-devel
<kchibisov>
FLHerne: I guess I'll just forward this bug.
<FLHerne>
I had a quick look and couldn't spot any commit that looks obviously relevant, should be easily bisectable though
<kchibisov>
Yeah, but I don't think the person can bisect...
mocoo has joined #dri-devel
<emersion>
i feel like DRM shim would be easier to implement by overridding some of the libdrm functions, rather than libc
<emersion>
at least for some of the stuff in there
pochu has quit [Ping timeout: 480 seconds]
junaid has quit [Remote host closed the connection]
JohnnyonFlame has joined #dri-devel
An0num0us has joined #dri-devel
paulk has quit [Read error: Connection reset by peer]
<Wallbraker>
Hah, well it's Monado which is day job, so can't really avoid it. :p
junaid has joined #dri-devel
<zmike>
I'd be happy to give you a reference to a number of reputable software firms that are hiring if it means you'll close that ticket
<Wallbraker>
I'm pretty happy here, and in general races should be avoided. :p
junaid has quit [Remote host closed the connection]
pekkari has quit [Ping timeout: 480 seconds]
<zmike>
damn, looks like I'll have to try to fix it
<Wallbraker>
Hehe
<alyssa>
pendingchaos: nod
<Wallbraker>
So I tried with vkcube but it doesn't open on the correct screen for some reason. What I think happens is that whatever code we have in Monado causes the compositor to move the window between one monitor and the other, and the window is resized.
<Wallbraker>
Just reverting that commit on the 23.2 branch fixes the issue for me.
<zmike>
I don't understand how that commit could be causing your issue
mszyprow has quit [Ping timeout: 480 seconds]
<Wallbraker>
Me neither
<Wallbraker>
Might be a race
jkrzyszt has quit [Ping timeout: 480 seconds]
idr has joined #dri-devel
donaldrobson has joined #dri-devel
<Wallbraker>
Yeah it's a *fun* race, without the patch reverted if I do the geometry getting twice with a `sleep(1);` in between them I can get:
<Wallbraker>
zmike: I think I'm going to close the issue, the issue seems to be in my particular setup and that Monado only does one frame in that particular setup (waiting for clients). And it does that in just the wrong amount of time while `gnome-shell` is trying to work out on which screen the window is and has it sized wrong.
<zmike>
🙏
<zmike>
the ghost of ajax was with me today
<Wallbraker>
Haha
<Wallbraker>
But gosh was it a head scratcher that my window got corruption if I added specialisation to my vertex shader or not.
tobiasjakobi has joined #dri-devel
<zmike>
🤔
hansg has quit [Quit: Leaving]
<Wallbraker>
But I could reproduce it with adding a sleep in the same function, so yeah, a race. But if I make it produce more frames it corrects itself when it get a VK_SUBOPTIMAL_KHR from DRI3.
kxkamil has joined #dri-devel
mszyprow has joined #dri-devel
marathon has joined #dri-devel
marathon has quit []
swiftgeek has joined #dri-devel
tobiasjakobi has quit [Remote host closed the connection]
maratman has joined #dri-devel
orbea has quit [Quit: You defeated orbea! 2383232 XP gained!]
orbea has joined #dri-devel
tobiasjakobi has joined #dri-devel
crabbedhaloablut has quit []
An0num0us has quit [Ping timeout: 480 seconds]
mszyprow has quit [Ping timeout: 480 seconds]
pochu has joined #dri-devel
donaldrobson has quit [Ping timeout: 480 seconds]
tursulin has quit [Ping timeout: 480 seconds]
robert_mader has joined #dri-devel
donaldrobson has joined #dri-devel
<robert_mader>
Hi! I wanted to ask if there are any Intel kernel driver devs around here? There seems to be bug that currently breaks direct-scanout of certain YUV formats (specifically NV12 and P010) in certain cases and I wondered who could be a good person to talk to about this (or where a good place for filing issues for stuff like this is). More context: https://gitlab.gnome.org/GNOME/mutter/-/issues/3031
<airlied>
vsyrjala: ^
<mlankhorst>
robert_mader: I'm curious
halfline has joined #dri-devel
<robert_mader>
mlankhorst: As mentioned in the issue my current suspicion is that NV12/P010 (i.e. multi-plane formats) are broken on the primary plane for some reason.
<yrlf>
I guess the intel driver is somehow borking the initial modeset, but I don't know exactly what happens there, since I haven't worked with the kernel much yet
<yrlf>
after the "fix" with yeeting the CRTC, everything works fine, and future modesets work properly, even through suspend
mocoo has quit [Ping timeout: 480 seconds]
An0num0us has quit [Ping timeout: 480 seconds]
An0num0us has joined #dri-devel
Leopold_ has quit [Remote host closed the connection]
An0num0us has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
halfline has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
<FLHerne>
is there an equivalent of INTEL_NO_HW for r300g? I thought there was but can't find it
<anholt>
drm-shim would skip execution.
<FLHerne>
oh, right
mszyprow has quit [Ping timeout: 480 seconds]
Haaninjo has quit [Quit: Ex-Chat]
pcercuei has quit [Quit: dodo]
sima has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
nashpa has joined #dri-devel
dliviu has quit [Read error: Connection reset by peer]