From: Antonio Caggiano <antonio.caggiano@collabora.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com, vivek.kasireddy@intel.com
Subject: Re: virtio-gpu: Get FD for texture
Date: Wed, 29 Sep 2021 15:54:59 +0200 [thread overview]
Message-ID: <273005ec-fc49-b8ac-cd6e-9efdb8a8aab4@collabora.com> (raw)
In-Reply-To: <968fd181-3f7d-4639-3265-9e4b36a6de61@collabora.com>
I am starting to believe that the error is due to the fact that no
EGLContext is active on the current thread (the one running the Vulkan
application).
Trying to call eglMakeCurrent within this thread gives me an
EGL_BAD_ACCESS error as the EGLContext associated to the GL texture
belongs to a different thread.
Does that make sense?
Kind regards,
Antonio Caggiano
On 27/09/21 12:21, Antonio Caggiano wrote:
> Hi,
>
> I am trying to support a Vulkan application in the guest
> (GTKGlArea+VirGL+venus) which needs to import a GL texture from a GL
> context.
>
> Before doing that, I need to get a FD for that texture, therefore I
> tried with calling egl-helpers.h:egl_get_fd_for_texture() but I get an
> epoxy error:
>
> > No provider of eglCreateImageKHR found. Requires one of:
>
> > EGL_KHR_image
>
> > EGL_KHR_image_base
>
> This is a bit weird to me as I am sure I am running QEMU with iris and
> according to eglinfo both of these extensions are available.
>
> Do you think my approach makes sense or I am doing something wrong
> somewhere?
>
>
> Kind regards,
> Antonio Caggiano
next prev parent reply other threads:[~2021-09-29 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 10:21 virtio-gpu: Get FD for texture Antonio Caggiano
2021-09-29 13:54 ` Antonio Caggiano [this message]
2021-09-29 23:32 ` Kasireddy, Vivek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=273005ec-fc49-b8ac-cd6e-9efdb8a8aab4@collabora.com \
--to=antonio.caggiano@collabora.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vivek.kasireddy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).