diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2013-07-19 19:36:51 (GMT) |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2013-07-20 08:54:37 (GMT) |
commit | a7cd1b8fea2f341b626b255d9898a5ca5fabbf0a (patch) | |
tree | 22d2f3e832e7de62b81b5446a47598ac4932bb08 /kernel | |
parent | e85843bec6c2ea7c10ec61238396891cc2b753a9 (diff) | |
download | linux-fsl-qoriq-a7cd1b8fea2f341b626b255d9898a5ca5fabbf0a.tar.xz |
drm/i915: Serialize almost all register access
In theory, the different register blocks were meant to be only ever
touched when holding either the struct_mutex, mode_config.lock or even a
specific localised lock. This does not seem to be the case, and the
hardware reacts extremely badly if we attempt to concurrently access two
registers within the same cacheline.
The HSD suggests that we only need to do this workaround for display
range registers. However, upon review we need to serialize the multiple
stages in our register write functions - if only for preemption
protection.
Irrespective of the hardware requirements, the current io functions are
a little too loose with respect to the combination of pre- and
post-condition testing that we do in conjunction with the actual io. As
a result, we may be pre-empted and generate both false-postive and
false-negative errors.
Note well that this is a "90%" solution, there remains a few direct
users of ioread/iowrite which will be fixed up in the next few patches.
Since they are more invasive and that this simple change will prevent
almost all lockups on Haswell, we kept this patch simple to facilitate
backporting to stable.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=63914
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions