Files
android_kernel_xiaomi_sm8450/drivers/gpu/drm
Daniel Vetter 11c9b6c628 drm/i915: Tighting frontbuffer tracking around flips
So I think I've spotted a small gap in the frontbuffer tracking
while discussing the logic with Paulo on irc:

1. Userspace schedules gpu rendering to the current frontbuffer.
This gets tracked in dev_priv->fb_tracking.busy_bits.

2. We pageflip a fully rendered buffer before the frontbuffer
rendering completes.

3. The request retiring will never clear busy_bits (since at retire
time the old frontbuffer won't have obj->frontbuffer_bits set), so
these bits now are stuck until someone again does a bit of frontbuffer
tracking.

If we clear stale busy_bits in flip_prepare this gap is closed.

Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2014-10-01 10:52:56 +02:00
..
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-15 11:55:47 +03:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-12 11:19:47 +02:00
2014-09-24 11:43:41 +10:00
2014-09-24 11:43:41 +10:00
2014-09-12 11:19:47 +02:00
2014-08-14 21:24:17 +02:00
2014-09-10 17:43:10 +10:00
2014-09-24 11:43:41 +10:00
2014-09-10 17:43:27 +10:00
2014-09-10 17:43:27 +10:00

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.freedesktop.org/                          *
************************************************************

The Direct Rendering Manager (drm) is a device-independent kernel-level
device driver that provides support for the XFree86 Direct Rendering
Infrastructure (DRI).

The DRM supports the Direct Rendering Infrastructure (DRI) in four major
ways:

    1. The DRM provides synchronized access to the graphics hardware via
       the use of an optimized two-tiered lock.

    2. The DRM enforces the DRI security policy for access to the graphics
       hardware by only allowing authenticated X11 clients access to
       restricted regions of memory.

    3. The DRM provides a generic DMA engine, complete with multiple
       queues and the ability to detect the need for an OpenGL context
       switch.

    4. The DRM is extensible via the use of small device-specific modules
       that rely extensively on the API exported by the DRM module.


Documentation on the DRI is available from:
    http://dri.freedesktop.org/wiki/Documentation
    http://sourceforge.net/project/showfiles.php?group_id=387
    http://dri.sourceforge.net/doc/

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://dri.sourceforge.net/doc/drm_low_level.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/hardware_locking_low_level.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/security_low_level.html