From: "Kim, Dongwon" <dongwon.kim@intel.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: <qemu-devel@nongnu.org>
Subject: Re: [PATCH v3 0/2] Consolidate create-sync and create-fence
Date: Wed, 24 Jul 2024 12:18:15 -0700 [thread overview]
Message-ID: <cc8bbebd-5f86-47ed-9c11-fdaa792518b6@intel.com> (raw)
In-Reply-To: <CAJ+F1C+kk4ZBjf8bq2haA4WgzEoSrN2GBYoC5Lc-r17VmRNA6g@mail.gmail.com>
Hey Marc-André,
On 7/24/2024 3:37 AM, Marc-André Lureau wrote:
> Hi
>
> On Wed, Jul 24, 2024 at 2:05 AM <dongwon.kim@intel.com
> <mailto:dongwon.kim@intel.com>> wrote:
>
> From: Dongwon Kim <dongwon.kim@intel.com <mailto:dongwon.kim@intel.com>>
>
> Sync object itself is never used as is so can be removed
> from QemuDmaBuf struct. So now sync is only temporarily needed
> when creating fence for the object which means what was done in
> egl_dmabuf_create_sync can now be a part of egl_dmabuf_create_fence
> function. And egl_dmabuf_create_fence returns fence_fd so the
> better function name will be egl_dmabuf_create_fence_fd.
>
> v3: create fence only if current QemuDmaBuf->fence_fd = -1
> to make sure there is no fence currently bound to the
> QemuDmaBuf
>
>
> Why not check it from egl_dmabuf_create_fence_fd() ? calling the
> function twice can still potentially leak.
It is called from only two locations in gtk-egl.c and gtk-gl-draw.c
and dmabuf->fence_fd == -1 is checked beforehand so I thought it's
not needed but I think your point is the completeness of the function
itself. Do you think we can do assert 'dmabuf->fence_fd >= 0'?
>
> Also, please gather the v1/v2/v3/... summary on the cover letter.
Sure
>
> thanks
>
>
> Dongwon Kim (2):
> ui/egl-helpers: Consolidates create-sync and create-fence
> ui/dmabuf: Remove 'sync' from QemuDmaBuf struct
>
> include/ui/dmabuf.h | 2 --
> include/ui/egl-helpers.h | 3 +--
> ui/dmabuf.c | 14 --------------
> ui/egl-helpers.c | 24 +++++++++---------------
> ui/gtk-egl.c | 17 ++++-------------
> ui/gtk-gl-area.c | 12 +++---------
> 6 files changed, 17 insertions(+), 55 deletions(-)
>
> --
> 2.43.0
>
>
>
>
> --
> Marc-André Lureau
prev parent reply other threads:[~2024-07-24 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 22:02 [PATCH v3 0/2] Consolidate create-sync and create-fence dongwon.kim
2024-07-23 22:02 ` [PATCH v3 1/2] ui/egl-helpers: Consolidates " dongwon.kim
2024-07-23 22:02 ` [PATCH v3 2/2] ui/dmabuf: Remove 'sync' from QemuDmaBuf struct dongwon.kim
2024-07-24 10:37 ` [PATCH v3 0/2] Consolidate create-sync and create-fence Marc-André Lureau
2024-07-24 19:18 ` Kim, Dongwon [this message]
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=cc8bbebd-5f86-47ed-9c11-fdaa792518b6@intel.com \
--to=dongwon.kim@intel.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).