Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] vulkan: synchronize access to execution pool fences
Date: Thu, 8 Jun 2023 00:06:18 +0200 (CEST)
Message-ID: <NXMtMey--3-9@lynne.ee> (raw)
In-Reply-To: <20230607143117.5c68b3a2@fluffy>

Jun 7, 2023, 23:31 by philipl@overt.org:

> On Wed, 7 Jun 2023 01:59:55 +0200 (CEST)
> Lynne <dev@lynne.ee> wrote:
>
>> Jun 7, 2023, 01:45 by dev@lynne.ee:
>>
>> > Jun 7, 2023, 01:22 by dev@lynne.ee:
>> >
>> >> vkResetFences is specified as being user-synchronized
>> >> (yet vkWaitFences, is not).
>> >>
>> >> Patch attached.
>> >>
>> >
>> > Stray change in vulkan_decode.c removed locally.
>> >
>>
>> Also removed the vkWaitForFences call during
>> the _start function from the mutex lock, as
>> it's safe to do so, and added a comment.
>>
>
> Ah, you updated the diff.
>
> This one is LGTM.
>

Thanks, pushed.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-06-07 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 23:22 Lynne
     [not found] ` <NXI0BZl--3-9@lynne.ee-NXI0Fb7----9>
2023-06-06 23:23   ` [FFmpeg-devel] [PATCH 2/2] vulkan: discard dependencies when explicitly waiting for execution Lynne
2023-06-07 21:32     ` Philip Langdale
2023-06-07 22:06       ` Lynne
2023-06-06 23:45   ` [FFmpeg-devel] [PATCH 1/2] vulkan: synchronize access to execution pool fences Lynne
     [not found]   ` <NXI5POg--3-9@lynne.ee-NXI5TBx----9>
2023-06-06 23:59     ` Lynne
2023-06-07 21:31       ` Philip Langdale
2023-06-07 22:06         ` Lynne [this message]
2023-06-07 21:30 ` Philip Langdale

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=NXMtMey--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git