diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2011-04-04 19:21:10 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2011-04-04 19:24:30 +0100 |
| commit | 6f104189bb9439ab0e05f04d4be020813eb04bf9 (patch) | |
| tree | c1c8040c6520dbc3a37c729a73a5619678d66057 /src/intel_driver.c | |
| parent | 314439860e595c473d168c0cafb2b5b49b7fef30 (diff) | |
Take advantage of the kernel flush for dirty bo in the busy ioctl
Rather than just creating and submitting a batch that simply contains a
flush in order to periodically ensure that rendering reaches the
scanout, we can simply ask the kernel whether the scanout is busy. The
kernel will then submit a flush on our behalf if it is dirty, which
takes advantage of the kernel's dirty state tracking.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'src/intel_driver.c')
| -rw-r--r-- | src/intel_driver.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/intel_driver.c b/src/intel_driver.c index 84497185..9e018367 100644 --- a/src/intel_driver.c +++ b/src/intel_driver.c @@ -758,7 +758,7 @@ intel_flush_callback(CallbackListPtr *list, { ScrnInfoPtr scrn = user_data; if (scrn->vtSema) - intel_batch_submit(scrn, FALSE); + intel_batch_submit(scrn); } #if HAVE_UDEV |