#asahi-gpu · 2023-11-07 12:40
marcanwrong channel, also when it's done#asahi-gpu · 2023-09-03 13:38
marcanit's less broken at least :p#asahi-gpu · 2023-09-03 12:41
marcanpushed a fix#asahi-gpu · 2023-08-01 13:19
marcanthat could explain basically any random problem, including the canberra stuff#asahi-gpu · 2023-08-01 13:19
marcanoof, heh#asahi-gpu · 2023-08-01 13:07
marcanthat would be fun#asahi-gpu · 2023-08-01 13:06
marcanwait, you think that option triggered the Mesa UAF from the kernel?#asahi-gpu · 2023-08-01 11:08
marcanwell that and the canberra thing I guess#asahi-gpu · 2023-08-01 11:07
marcannobody's ever seen kernel lockups since the latest update right?#asahi-gpu · 2023-08-01 11:07
marcanso then we just have that rare Mesa UAF thing then#asahi-gpu · 2023-08-01 10:47
marcanhttps://lore.kernel.org/linux-mm/CAJuCfpH4HyAVO0fVYKGR9xhZJu19Ek_dTMEBiCCSbOjkDxXD=w@mail.gmail.com/T/#asahi-gpu · 2023-07-23 10:46
marcanhow negative are you getting?#asahi-gpu · 2023-07-23 10:44
marcanrosefromthedead: I wonder if there's just a slight offset with the GPU timer for some reason. I don't really know what the internal architecture is like. I know there's one master AIC timer which I think everything derives from, but not how all the downstream timers are synced from that#asahi-gpu · 2023-07-23 10:42
marcanno ECV then, so no second offset#asahi-gpu · 2023-07-23 10:41
marcanrosefromthedead: what machine?#asahi-gpu · 2023-07-23 10:36
marcanno other ARM64 CPU managed to hit it apparently#asahi-gpu · 2023-07-23 10:36
marcanfound a years-old Linux core workqueue code bug#asahi-gpu · 2023-07-23 10:36
marcanI've seen these damn things speculate through an IRQ enough to break some code missing a barrier, it's nuts#asahi-gpu · 2023-07-23 10:35
marcanyeah, otherwise it could in principle speculate through the actual work submission to the GPU and all that#asahi-gpu · 2023-07-23 02:47
marcanalso I assume you're not running this on the hypervisor, right? that *will* screw with timekeeping on purpose by default#asahi-gpu · 2023-07-23 02:46
marcanalso there could be an offset on the virtual counter for some reason#asahi-gpu · 2023-07-23 02:46
marcanrosefromthedead: you probably need an isb, those counters aren't synchronized#asahi-gpu · 2023-06-07 07:17
marcannobody reviews my kernel code and apparently I broke suspend in the latest release, sooooo :P#asahi-gpu · 2023-05-31 13:17
marcannp :)#asahi-gpu · 2023-05-31 12:58
marcaneric_engestrom: no, that's https://bugs.kde.org/show_bug.cgi?id=455526#asahi-gpu · 2023-05-12 13:34
marcanthat sounds like a bug in wlr (the perf and spamming, not the software cursor, though it might be related)#asahi-gpu · 2023-05-12 13:09
marcanI dunno what the policy is here, just an idea :p#asahi-gpu · 2023-05-12 13:08
marcanalyssa: speaking of overrides, maybe we should enable nofp16 for browsers? since there's always going to be broken WebGL stuff out there...#asahi-gpu · 2023-05-12 13:06
marcandefine "significantly". if the capture is like 3FPS, that's the writeback issue. if it's faster, that's something else.#asahi-gpu · 2023-05-12 12:51
marcanalyssa: from what I read the libwebrtc implementation should be doing modifiers properly, so it should be confined to the readback path once inside the browser and hopefully only needed for firefox/chromium#asahi-gpu · 2023-05-12 10:17
marcanalyssa, lina: hey, so libwebrtc (firefox/chromium) PipeWire screencasting is super slow (when it works, see fedi for another bug). I assume that's the write-through mapping issue. would be nice if you could look at it and see if it can be fixed with a logic change in mesa, or if it's blatantly a libwebrtc screwup.#asahi-gpu · 2023-05-02 06:48
marcandottedmag: HDR has nothing to do with the GPU, that's for jannau and DCP.#asahi-gpu · 2023-04-10 01:54
marcanpoints at the topic that says "no user support"#asahi-gpu · 2023-03-20 17:52
marcanI'm going to make a asahi-20230321 with just that one revert on top of the old one, to avoid adding more entropy (alyssa: I know you did push main since then)#asahi-gpu · 2023-03-20 17:50
marcanlet me fix that real quick..#asahi-gpu · 2023-03-20 17:50
marcan(breaks chromium)#asahi-gpu · 2023-03-20 17:50
marcan*that* was the thing I was forgetting.#asahi-gpu · 2023-03-20 17:50
marcanurgh I think I forgot to backport the dual source blending disable thing#asahi-gpu · 2023-03-20 13:40
marcanbut yes, we use actual packages#asahi-gpu · 2023-03-20 13:40
marcanI think eric_engestrom was thinking of package groups, not metapackages#asahi-gpu · 2023-03-20 12:58
marcan*use#asahi-gpu · 2023-03-20 12:58
marcanonce we bless the GPU driver as good enough to us by default (probably real soon now) it'll become a dependency and upstream can't break us any more anyway#asahi-gpu · 2023-03-20 12:57
marcaneric_engestrom: I mean the idea was that the whole thing is *opt-in* right now, that's why our users have upstream mesa in the first place#asahi-gpu · 2023-03-20 00:34
marcanassuming we keep the -edge system for more bleeding edge stuff, that would be just named `mesa-asahi` at that point#asahi-gpu · 2023-03-20 00:33
marcanwhat we'll do once this is shipped by default is make it a dependency of our desktop metapackage, at which point everyone will be forced to install it (unless they remove the metapackage, which is not supported)#asahi-gpu · 2023-03-20 00:33
marcaneric_engestrom: shadowing upstream packages is not super nice, it makes more sense to set up alternats that provide the original package name (which ours does)#asahi-gpu · 2023-03-14 15:12
marcanack#asahi-gpu · 2023-03-14 15:07
marcanin particular I want to know what happens with that test where you previously hit the mailbox queue limit#asahi-gpu · 2023-03-14 15:07
marcanalyssa: asahi-wip should have all of lina's recent changes plus the mailbox thing, please let me know how that goes#asahi-gpu · 2023-03-13 00:50
marcanmkurz: do not ask feature support questions. things will be supported and announced when they are. this is not a user support channel.