From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org
Subject: Re: Start fixing the shared to exclusive fence dependencies.
Date: Sat, 3 Jul 2021 01:53:57 +0200 [thread overview]
Message-ID: <YN+nFePPaClmZAQy@phenom.ffwll.local> (raw)
In-Reply-To: <20210702111642.17259-1-christian.koenig@amd.com>
On Fri, Jul 02, 2021 at 01:16:38PM +0200, Christian König wrote:
> Hey Daniel,
>
> even when you are not 100% done with the driver audit I think we should
> push that patch set here to drm-misc-next now so that it can end up in
> 5.15.
So I think I got them all, just need to type up some good docs all over
the place next week and send it out.
-Daniel
>
> Not having any dependency between the exclusive and the shared fence
> signaling order is just way more defensive than the current model.
>
> As discussed I'm holding back any amdgpu and TTM workarounds which could
> be removed for now.
>
> Thoughts?
>
> Thanks,
> Christian.
>
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2021-07-02 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 11:16 Start fixing the shared to exclusive fence dependencies Christian König
2021-07-02 11:16 ` [PATCH 1/4] dma-buf: add some more kerneldoc to dma_resv_add_shared_fence Christian König
2021-07-02 22:16 ` Daniel Vetter
2021-07-02 11:16 ` [PATCH 2/4] dma-buf: fix dma_resv_test_signaled test_all handling v2 Christian König
2021-07-02 22:33 ` Daniel Vetter
2021-07-02 11:16 ` [PATCH 3/4] drm/nouveau: always wait for the exclusive fence Christian König
2021-07-02 23:00 ` Daniel Vetter
2021-07-02 11:16 ` [PATCH 4/4] drm/msm: " Christian König
2021-07-02 23:01 ` Daniel Vetter
2021-07-08 12:52 ` Christian König
2021-07-02 23:53 ` Daniel Vetter [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=YN+nFePPaClmZAQy@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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).