41a55d0330
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. |
||
---|---|---|
.. | ||
drm_fourcc.h | ||
drm_mode.h | ||
drm.h | ||
etnaviv_drm.h | ||
i915_drm.h | ||
lima_drm.h | ||
msm_drm.h | ||
panfrost_drm.h | ||
README | ||
tegra_drm.h | ||
v3d_drm.h | ||
vc4_drm.h | ||
virtgpu_drm.h |
This directory contains a copy of the installed kernel headers required by several drivers to communicate with the kernel. Whenever one of those driver needs new definitions for new kernel APIs, these files should be updated. These files in master should only be updated once the changes have landed in the drm-next tree. You can copy files installed after running this from the kernel repository, at version the drivers require : $ make headers_install INSTALL_HDR_PATH=/path/to/install The last update was done at the following kernel commit : commit f1b4a9217efd61d0b84c6dc404596c8519ff6f59 Merge: 400e91347e1d f3a36d469621 Author: Dave Airlie <airlied@redhat.com> Date: Tue Oct 22 15:04:00 2019 +1000 Merge tag 'du-next-20191016' of git://linuxtv.org/pinchartl/media into drm-next