From: Zack Rusin <zackr@vmware.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"gustavo@padovan.org" <gustavo@padovan.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
"ckoenig.leichtzumerken@gmail.com"
<ckoenig.leichtzumerken@gmail.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH 11/11] drm/vmwgfx: remove vmw_wait_dma_fence
Date: Mon, 24 Jan 2022 15:25:29 +0000 [thread overview]
Message-ID: <a77f69967468eb7e6540f93795d40ad8ca54a02a.camel@vmware.com> (raw)
In-Reply-To: <20220124130328.2376-12-christian.koenig@amd.com>
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
> Decomposing fence containers don't seem to make any sense here.
>
> So just remove the function entirely and call dma_fence_wait()
> directly.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Cc: VMware Graphics <linux-graphics-maintainer@vmware.com>
> Cc: Zack Rusin <zackr@vmware.com>
Looks good. That's a great cleanup.
Reviewed-by: Zack Rusin <zackr@vmware.com>
WARNING: multiple messages have this Message-ID (diff)
From: Zack Rusin <zackr@vmware.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"gustavo@padovan.org" <gustavo@padovan.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
"ckoenig.leichtzumerken@gmail.com"
<ckoenig.leichtzumerken@gmail.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH 11/11] drm/vmwgfx: remove vmw_wait_dma_fence
Date: Mon, 24 Jan 2022 15:25:29 +0000 [thread overview]
Message-ID: <a77f69967468eb7e6540f93795d40ad8ca54a02a.camel@vmware.com> (raw)
In-Reply-To: <20220124130328.2376-12-christian.koenig@amd.com>
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
> Decomposing fence containers don't seem to make any sense here.
>
> So just remove the function entirely and call dma_fence_wait()
> directly.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Cc: VMware Graphics <linux-graphics-maintainer@vmware.com>
> Cc: Zack Rusin <zackr@vmware.com>
Looks good. That's a great cleanup.
Reviewed-by: Zack Rusin <zackr@vmware.com>
next prev parent reply other threads:[~2022-01-24 15:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 13:03 Add WARN_ON nested dma_fence containers Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 01/11] drm/radeon: use ttm_resource_manager_debug Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 16:33 ` Thomas Hellström
2022-01-24 16:33 ` [Intel-gfx] " Thomas Hellström
2022-01-24 20:21 ` Christian König
2022-01-24 20:21 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 02/11] drm/amdgpu: " Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 03/11] dma-buf: consolidate dma_fence subclass checking Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 04/11] dma-buf: warn about dma_fence_array container rules v2 Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 16:32 ` Thomas Hellström
2022-01-24 16:32 ` [Intel-gfx] " Thomas Hellström
2022-01-24 13:03 ` [PATCH 05/11] dma-buf: Warn about dma_fence_chain " Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 06/11] dma-buf: warn about containers in dma_resv object Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 16:36 ` Thomas Hellström (Intel)
2022-01-24 20:22 ` Christian König
2022-01-24 13:03 ` [PATCH 07/11] dma-buf: Add dma_fence_array_for_each (v2) Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 08/11] dma-buf: add dma_fence_chain_contained helper Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 16:52 ` Thomas Hellström
2022-01-24 16:52 ` [Intel-gfx] " Thomas Hellström
2022-01-24 13:03 ` [PATCH 09/11] drm/amdgpu: use dma_fence_chain_contained Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 13:03 ` [PATCH 10/11] drm/i915: use dma_fence extractor functions Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-29 8:31 ` [drm/i915] 9366257fc0: igt.i915_pm_rc6_residency.rc6-idle.fail kernel test robot
2022-01-29 8:31 ` kernel test robot
2022-01-29 8:31 ` kernel test robot
2022-01-29 8:31 ` [Intel-gfx] " kernel test robot
2022-01-24 13:03 ` [PATCH 11/11] drm/vmwgfx: remove vmw_wait_dma_fence Christian König
2022-01-24 13:03 ` [Intel-gfx] " Christian König
2022-01-24 15:25 ` Zack Rusin [this message]
2022-01-24 15:25 ` Zack Rusin
2022-01-24 21:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] drm/radeon: use ttm_resource_manager_debug Patchwork
2022-01-24 21:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-24 22:14 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=a77f69967468eb7e6540f93795d40ad8ca54a02a.camel@vmware.com \
--to=zackr@vmware.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.