ui: ozone: drm: synchronize mapped dmabuf with read&write

ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons

Committed: https://crrev.com/9d43e6183bb0bcfb28d1e1af1fb51210a717e251
Cr-Commit-Position: refs/heads/master@{#417585}

[llandwerlin-old, 2016-09-01 17:44:01]

lionel.g.landwerlin@intel.com changed reviewers:
+ dongseong.hwang@intel.com

[llandwerlin-old, 2016-09-01 17:44:02]

DS: PTAL, thanks!

[llandwerlin-old, 2016-09-05 11:05:31]

Description was changed from

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we see tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons
==========

to

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons
==========

[dshwang, 2016-09-09 12:51:34]

On 2016/09/01 17:44:02, llandwerlin wrote:
> DS: PTAL, thanks!

lgtm

It fixs Braswell artifact and slightly speed up. The code makes sense also.

[llandwerlin-old, 2016-09-09 13:03:47]

lionel.g.landwerlin@intel.com changed reviewers:
+ dnicoara@chromium.org

[llandwerlin-old, 2016-09-09 13:03:48]

dnicoara@chromium.org: PTAL (checked with @dshwang first), thanks!

[dnicoara, 2016-09-09 14:13:25]

lgtm

[llandwerlin-old, 2016-09-09 14:14:05]

The CQ bit was checked by lionel.g.landwerlin@intel.com

[commit-bot: I haz the power, 2016-09-09 14:14:18]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-09 15:00:51]

Description was changed from

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons
==========

to

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons
==========

[commit-bot: I haz the power, 2016-09-09 15:00:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-09 15:03:54]

Description was changed from

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons
==========

to

==========
ui: ozone: drm: synchronize mapped dmabuf with read&write

We're currently starting the synchronization of memory mapped dmabufs only
for reading, which means the driver will not flush the CPU cache on
DMA_BUF_SYNC_END. As a result we tend to see cache lines on platforms
where we don't have an additional cache level like Atom platforms.

BUG=475633
TEST=run chrome on chromeos with --enable-native-gpu-memory-buffers and
     verify we don't have image corruptions when hovering the close/minimize
     buttons

Committed: https://crrev.com/9d43e6183bb0bcfb28d1e1af1fb51210a717e251
Cr-Commit-Position: refs/heads/master@{#417585}
==========

[commit-bot: I haz the power, 2016-09-09 15:03:55]

Patchset 1 (id:??) landed as
https://crrev.com/9d43e6183bb0bcfb28d1e1af1fb51210a717e251
Cr-Commit-Position: refs/heads/master@{#417585}