Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In drm from linux >= 5.9 renoir no longer uses the gpu info firmware and
some reported hardware information changes.
'drm/amdgpu: use IP discovery table for renoir'
c1cf79ca5ced46ea6a7843cbe98836e4d51c6c52
Remove warning which is known to be harmless
https://gitlab.freedesktop.org/drm/amd/-/issues/1332
and was removed with mesa 20.2 in
'radeonsi/gfx10: implement most performance counters'
38a4b861459b02401d3ff71670218506e7acf019
|
|
From Rhys Perry
bcb0038c8399f7050eb49cfdb227d3d91c1e8804 in mainline Mesa
|
|
From Roland Scheidegger
51a82ec3e437d1d2dc4c688578640d25b3e7f0a2 in mainline Mesa
|
|
From Marek Olsak
8dc5e174c7b96b6d4b5a6923068410f298167a39 in mainline Mesa
|
|
|
|
From Marek Olsak
63a5051ea6bf4d72a02594d21a3351e44bd70da7 in mainline Mesa
|
|
From Marek Olsak
56cc10bd27b24d513de88bf7fa94a6c8f43e348f in mainline Mesa
|
|
From Jan Zielinski
52aa730d07618513d6c055618069b2f4680974cc in mainline Mesa
Encountered by naddy@ when doing a clang 11 build. This commit
suggested by patrick@
|
|
|
|
|
|
|
|
From Jan Beich
46c368907fcf333a19881d28c46e997845d00faf in mainline Mesa
We had a related local patch in 19.2 which wasn't needed when 20.1 was
imported as the above commit was backported to the upstream 20.1 branch.
When Mesa 20.0 was imported after issues with 20.1 on Haswell the
changes to use futexes for simple_mtx.h and u_queue.h were lost.
Noticed by otto@ and kettenis@ when looking for memory leaks.
|
|
From Vinson Lee
ff8daa013621019f1606dc0c188b16f1ce34fea7 in mainline Mesa
fixes clang 11 build
mortimer@ had almost the same diff
|
|
|
|
From Kristian Hoegsberg
e3dfa8f4d694e7d64a6401752af1f973b0852aab in mainline Mesa
reduces clang warnings
|
|
From Kristian Hoegsberg
b40281d8306367e68dde6b723d2114d9cb5fca5a in mainline Mesa
|
|
|
|
|
|
With Mesa 20.1 even after the kernel change to do wbinvd on all cpus
sthen@ reported that hard hangs still occurred on his Haswell system
with inteldrm.
Mark Kane also reported seeing hangs on Ivy Bridge on bugs@.
Some systems/workloads seem to be more prone to triggering this than
others as I have not seen any hangs on Ivy Bridge and the only hangs
I saw on Haswell when running piglit went away with the wbinvd change.
It seems something is wrong with drm memory attributes or coherency in
the kernel and newer Mesa versions expect behaviour we don't have.
|
|
|
|
haswell hangs still occurred just less frequently with the 1.10 revert of
'intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages'
The recent kernel change to do wbinvd across all cpus instead of just one
is a better approach and avoids hangs seen with piglit on haswell.
|
|
|
|
intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages
d23bbc8c28b6a5cd7f4d3d03c74d8319da5d47d5 on 20.1 branch
4985e380dd776ac65c4ae5627138211f9d9f03ce on mainline
thanks to gnezdo@ sthen@ and espie@ for reports and testing
|
|
|
|
|
|
|
|
|