On 22/02/2021 21:18, Tom Seewald wrote: >> I feel that you underestimate the impact of the GPU driver issue >> >> If the GPU driver doesn't work, people can't even log in and get started > > I still do not understand why no one from the talos/ppc64le community is following up on that amdgpu regression[1] that was introduced with the 5.9 kernel. Surely the time and effort already taken recompiling kernels with 4k pages along with formulating and discussing this proposal for Fedora 35 has eclipsed spending part of an evening bisecting and replying to the amd developers? I have replied to the bug report to give some guidance on how to bisect kernel bugs as the reporter was not familiar with git. Hopefully some progress will be made in the coming days. Personally, I have an older GPU, RX 580 Polaris series, I will only spend dev time on the AMD Navi GPU issues after AMD makes the RX 6800 XT available in my region. I simply don't have that card and I'm not going to waste money buying the original Navi card, RX 5700, when the new card will arrive imminently. Ultimately, even if it isn't hard to bisect, it doesn't feel fair that AMD is validating their drivers work on x86 before a release but the ppc64le users have to check things after a buggy release. > >> If the GPU vendors don't test their code on ppc64le (and aarch64) then >> those platforms will always lag behind x86. Users will experience >> issues that have been fixed in the development phase for x86. > > Are there really pervasive issues with amdgpu and non-4k page sizes? If so, they are not being reported as there is only one bug open that mentions 64k pages in their bug tracker. I do not see sufficient evidence to suggest that it is not worthwhile to engage with upstream to fix real bugs. Being active participants with the upstream developers is a very good way to motivate them to care more about smaller platforms, and likewise not interacting with upstream is unfortunately a good way to decrease the mindshare of smaller desktop platforms. I'm all in favor of collaboration with the AMD and kernel developers Ultimately, the only way to ensure equality across different architectures is to have upstream developers using all of these architectures throughout their development cycle. How can we encourage greater use of ppc64le and aarch64 in those communities? While it may sound trivial, I made a post here last week about how we can help people choose the right workstation through the wiki: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/EKCQRGEDHBS43GAOKH6O4UMCNA3YX4E6/ I estimate spending one or two hours in my own comparison of the Raptor motherboards and I hope the table allows other developers to save the same amount of time. >> Personally, I'm not opposed to the 64k page size in principle: my >> concerns are about the practical issues. >> >> If both 4k and 64k can be supported, if users can choose between >> installers for either page size, then the severity of the issue is reduced >> >> Regards, >> >> Daniel > > [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1446 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
