From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts Date: Sat, 25 May 2019 20:07:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0371626290==" 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 61E8F89FED for ; Sat, 25 May 2019 20:07:38 +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 --===============0371626290== Content-Type: multipart/alternative; boundary="15588148580.C0e3C444c.10693" Content-Transfer-Encoding: 7bit --15588148580.C0e3C444c.10693 Date: Sat, 25 May 2019 20:07:38 +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=3D106302 --- Comment #2 from seb@vestigecounty.com --- Pierre-Eric, in my interpretation of OpenGL(R) ES Version 3.0.5 (November 3, 2016) Specification, Appendix 4: Shared Objects and Multiple Contexts, D.3. Propagating Changes to Objects, Rule 4:... ---- If the contents of an object T are changed in a context other than the curr= ent context, T must be attached or re-attached to at least one binding point in= the current context, or at least one attachment point of a currently bound container object C, in order to guarantee that the new contents of T are visible in the current context. Example: If a texture image is bound to multiple texture bind points and the texture is changed in another context, re-binding the texture at any one of= the texture bind points is sufficient to cause the changes to be visible at all texture bind points. ---- ...Finish or Fence are not required, since I am re-binding the texture on t= he secondary thread where I expect changes to be seen. --=20 You are receiving this mail because: You are the assignee for the bug.= --15588148580.C0e3C444c.10693 Date: Sat, 25 May 2019 20:07:38 +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

Commen= t # 2 on bug 10630= 2 from seb@vest= igecounty.com
Pierre-Eric, in my interpretation of OpenGL(R) ES Version 3.0.=
5 (November 3,
2016) Specification, Appendix 4: Shared Objects and Multiple Contexts, D.3.
Propagating Changes to Objects, Rule 4:...

----
If the contents of an object T are changed in a context other than the curr=
ent
context, T must be attached or re-attached to at least one binding point in=
 the
current context, or at least one attachment point of a currently bound
container object C, in order to guarantee that the new contents of T are
visible in the current context.

Example: If a texture image is bound to multiple texture bind points and the
texture is changed in another context, re-binding the texture at any one of=
 the
texture bind points is sufficient to cause the changes to be visible at all
texture bind points.
----

...Finish or Fence are not required, since I am re-binding the texture on t=
he
secondary thread where I expect changes to be seen.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15588148580.C0e3C444c.10693-- --===============0371626290== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0371626290==--