Kill the flushing list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Kill the flushing list
From: chris at chris-wilson.co.uk (Chris Wilson)
Date: Thu, 12 Jul 2012 16:13:33 +0100

So it appears I alone have been hitting the WARNs left inplace to flag
breakage from the initial prep work for the flushing list. Thanks to
this dubious honour, I've reviewed that work and decided to finish the
removal in order to kill the WARNs.

Please review, review, test, review.
-Chris

Follow-Ups:
- [PATCH 6/6] drm/i915: Split i915_gem_flush_ring() into seperate invalidate/flush funcs
  - From: Chris Wilson
- [PATCH 5/6] drm/i915: Remove the explicit flush of the GPU write domain
  - From: Chris Wilson
- [PATCH 4/6] drm/i915: Remove explicit flush from i915_gem_object_flush_fence()
  - From: Chris Wilson
- [PATCH 3/6] drm/i915: Remove the per-ring write list
  - From: Chris Wilson
- [PATCH 2/6] drm/i915: Remove the defunct flushing list
  - From: Chris Wilson
- [PATCH 1/6] drm/i915: Allow late allocation of request for i915_add_request()
  - From: Chris Wilson

Prev by Date: [PATCH 03/09] drm/i915: Move DP structs to shared location
Next by Date: [PATCH 1/6] drm/i915: Allow late allocation of request for i915_add_request()
Previous by thread: [PATCH 1/2] intel_dri: Fixed a buffer leak when enable glamor.
Next by thread: [PATCH 1/6] drm/i915: Allow late allocation of request for i915_add_request()
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux