Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(720)

Issue 1906253003: Ozone GBM: i915_gem_end_cpu_access causes crash.

Created:
4 years, 8 months ago by dshwang
Modified:
4 years, 7 months ago
CC:
chromium-reviews, kalyank, ozone-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Ozone GBM: i915_gem_end_cpu_access causes crash. Only Intel Atom architecture needs the synchronization logic, and we didn't enable GBMs on any Atom devices. So we can comment it out until it's fixed. BUG=611968, 612078

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -2 lines) Patch
M ui/ozone/platform/drm/common/client_native_pixmap_dmabuf.cc View 2 chunks +3 lines, -2 lines 0 comments Download

Messages

Total messages: 12 (6 generated)
dshwang
spang, tiago, could you review?
4 years, 8 months ago (2016-04-22 09:22:48 UTC) #3
dshwang
after more debugging, the crash might not be related to dma_buf sync. However, dma_buf sync ...
4 years, 8 months ago (2016-04-22 09:53:34 UTC) #4
dshwang
Close as WontFix as warning is fixed in https://chromium-review.googlesource.com/#/c/340480/
4 years, 8 months ago (2016-04-25 07:20:49 UTC) #5
dshwang
Reopen this CL as i915_gem_end_cpu_access actually causes crash. spang@, could you review?
4 years, 7 months ago (2016-05-17 11:46:50 UTC) #8
marcheu1
On 2016/05/17 11:46:50, dshwang wrote: > Reopen this CL as i915_gem_end_cpu_access actually causes crash. > ...
4 years, 7 months ago (2016-05-17 15:29:21 UTC) #11
dshwang
4 years, 7 months ago (2016-05-17 16:45:13 UTC) #12
On 2016/05/17 15:29:21, marcheu1 wrote:
> On 2016/05/17 11:46:50, dshwang wrote:
> > Reopen this CL as i915_gem_end_cpu_access actually causes crash.
> > 
> > spang@, could you review?
> 
> Isn't this going to break correctness on non-coherent platforms at least?

It can break correctness on non-coherent platforms. However, as we enable it on
only coherent platform (i.e. Haswell, Broadwell and Skylake), it's fine now.
However, we have to fix the root issue later.

Powered by Google App Engine
This is Rietveld 408576698