Hi, Thanks for introducing yourself!
In the mesa bug tracker, if you filter with RADV and enhancement/performance labels, there are plenty of tickets that need some attention. That's probably a good start if you want to get familiar with the project.
If you can't assign issues to yourself, writing a comment saying that your investigating sounds good to me.
Thanks, Samuel. On 3/24/26 2:09 PM, Kingstom wrote:
Hi, Samuel suggested I introduce myself after I commented on issue #15137. I worked at AMD for three years building GPU benchmark and profiling tools for the graphics driver(UMD) team. Left a couple of years ago, still interested in the Linux graphics stack. I'd like to contribute to Mesa starting with RADV, since the driver-side debug and measurement paths are closest to what I know. I'm looking at the perf/debug tooling side of RADV as a contribution area. Is there ongoing work in that space I should be aware of, or areas that could use more hands? Also, I understand I should assign issues before investigating. I don't think my GitLab account has that permission yet — should I just comment on the issue for now? Thanks, Kingstom Chen
