dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
Cc: "Christian König" <christian.koenig@amd.com>,
	"DRI Development" <dri-devel@lists.freedesktop.org>
Subject: Re: Fence wait in mmu_interval_notifier_ops::invalidate
Date: Wed, 9 Dec 2020 12:37:31 -0400	[thread overview]
Message-ID: <20201209163731.GU552508@nvidia.com> (raw)
In-Reply-To: <912c29f1-4e17-8b66-419b-1854d03845fd@shipmail.org>

On Wed, Dec 09, 2020 at 05:36:16PM +0100, Thomas Hellström (Intel) wrote:
> Jason, Christian
> 
> In most implementations of the callback mentioned in the subject there's a
> fence wait.
> What exactly is it needed for?

Invalidate must stop DMA before returning, so presumably drivers using
a dma fence are relying on a dma fence mechanism to stop DMA.

Jason
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-12-10  8:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 16:36 Fence wait in mmu_interval_notifier_ops::invalidate Thomas Hellström (Intel)
2020-12-09 16:37 ` Jason Gunthorpe [this message]
2020-12-09 16:46   ` Thomas Hellström (Intel)
2020-12-10 10:53     ` Christian König
2020-12-11  7:50       ` Thomas Hellström (Intel)
2020-12-11  8:57         ` Christian König
2020-12-11  9:37           ` Thomas Hellström (Intel)
2020-12-11 12:46         ` Jason Gunthorpe
2020-12-13 15:09           ` Thomas Hellström (Intel)
2020-12-14  9:52             ` Daniel Vetter
2020-12-14 10:21               ` Christian König

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=20201209163731.GU552508@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thomas_os@shipmail.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