On Thu, Oct 22, 2015 at 10:56 AM, Erik Faye-Lund <kusmab...@gmail.com> wrote: > On Thu, Oct 22, 2015 at 10:54 AM, Marek Olšák <mar...@gmail.com> wrote: >> On Thu, Oct 22, 2015 at 10:22 AM, Erik Faye-Lund <kusmab...@gmail.com> wrote: >>> On Wed, Oct 21, 2015 at 10:34 PM, Marek Olšák <mar...@gmail.com> wrote: >>>> On Wed, Oct 21, 2015 at 12:28 PM, Axel Davy <axel.d...@ens.fr> wrote: >>>>> The PIPE_BIND_SHARED flag should be added whenever >>>>> the resource may be shared with another process. >>>>> >>>>> In particular if the resource is imported, or may >>>>> be exported, the flag should be used. >>>> >>>> This can't be enforced. EGL_MESA_image_dma_buf_export allows exporting >>>> any texture. Mesa can't know in advance if a texture will be exported. >>> >>> Could we not, at least in theory, crate a new texture and blit the old >>> one into it behind the scenes somehow when a texture gets exported? >> >> Sharing means textures are shared. There is no blitting allowed. Other >> users don't have to be notified that a shared texture has been >> rendered to. > > Maybe I wasn't clear enough: I meant to migrate the texture data over > to a new shared home, not to create a copy.
Ok, well, in that case it's easier to just share the texture as-is. Marek _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
