[PATCH] Revert "Set DamageSetReportAfterOp to true for the damage extension" (#30260)

[Francisco Jerez]

Keith Packard <keithp at keithp.com> writes:

> On Thu, 21 Oct 2010 01:38:58 +0200, Francisco Jerez <currojerez at riseup.net> wrote:
>
>> Nouveau uses the hardware interchannel synchronization primitives on
>> demand (it kicks in when two channels have references to the same BO):
>> the nouveau DRM guarantees that two command buffers rendering to/from
>> the same BO will get executed in order as seen by the DRM.
>
> Would it make sense to have this only kick in when damage is reported to
> the compositing manager? That would limit the number of semaphores you
> stick in the command queue.

Not really, the decision is made by the kernel when it sees a reference
to an in-flight buffer from the wrong channel, if that happens we can be
sure we have to resort to some kind of synchronization before submitting
the next batch, except on rare occasions.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101021/edd0161a/attachment-0001.pgp>