From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101691] gfx corruption on windowed 3d-apps running on dGPU Date: Wed, 18 Oct 2017 19:19:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1417960625==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 3D6506E0CC for ; Wed, 18 Oct 2017 19:19:56 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1417960625== Content-Type: multipart/alternative; boundary="15083543961.cA31E0.11941"; charset="UTF-8" --15083543961.cA31E0.11941 Date: Wed, 18 Oct 2017 19:19:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D101691 --- Comment #55 from Daniel Vetter --- So parts of the reasons I've reassigned to amdgpu is that apparently someone also seen these corruptions when everything is rendered on amdgpu, and i915 only displays. And the display engine is definitely only accessing memory directly, bypassing cpu caches. Changing stuff on the kernel on the i915 side didn't help (on import we tre= at buffers as uncached and assume they're fully flushed). But we kinda missed/didn't get around to testing the mesa caching mode overrides (which = seem to be wrong when texturing). So might need to move the bug to intel mesa (a= nd who knows what happened with the display issue, I guess we'll shrug that off until confirmed with a video). Aside: When exporting dma-buf from i915 we leave them in whatever caching m= ode is preferred by that gpu platform, which on recent big core is fully cached (i.e. requires snooping). We still might need to somehow teach dma-buf importers about whether they need to use snooping reads/writes (through a n= ew flag/function/whatever). --=20 You are receiving this mail because: You are the assignee for the bug.= --15083543961.cA31E0.11941 Date: Wed, 18 Oct 2017 19:19:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 55 on bug 10169= 1 from <= span class=3D"fn">Daniel Vetter
So parts of the reasons I've reassigned to amdgpu is that appa=
rently someone
also seen these corruptions when everything is rendered on amdgpu, and i915
only displays. And the display engine is definitely only accessing memory
directly, bypassing cpu caches.

Changing stuff on the kernel on the i915 side didn't help (on import we tre=
at
buffers as uncached and assume they're fully flushed). But we kinda
missed/didn't get around to testing the mesa caching mode overrides (which =
seem
to be wrong when texturing). So might need to move the bug to intel mesa (a=
nd
who knows what happened with the display issue, I guess we'll shrug that off
until confirmed with a video).

Aside: When exporting dma-buf from i915 we leave them in whatever caching m=
ode
is preferred by that gpu platform, which on recent big core is fully cached
(i.e. requires snooping). We still might need to somehow teach dma-buf
importers about whether they need to use snooping reads/writes (through a n=
ew
flag/function/whatever).


You are receiving this mail because:
  • You are the assignee for the bug.
= --15083543961.cA31E0.11941-- --===============1417960625== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1417960625==--