From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: Rob Clark <robdclark@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fence: Use smp_mb__before_atomic()
Date: Thu, 5 Jun 2014 08:52:00 -0700 [thread overview]
Message-ID: <20140605155200.GC23993@kroah.com> (raw)
In-Reply-To: <53905BD0.9080002@canonical.com>
On Thu, Jun 05, 2014 at 02:00:16PM +0200, Maarten Lankhorst wrote:
> >I don't think the question about whether we need something like fence
> >to augment dma-buf is really in doubt. Maybe it should live somewhere
> >else, I'm not sure. But it makes sense for it to live wherever
> >dma-buf does, as they are intended to work together.
> >
> Additionally we already have a user for this in the kernel: the GPU
> drivers that use TTM.
What about the sync code in the android directory? I thought that was
supposed to be what GPU drivers were going to use for this type of
thing.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-05 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 14:26 [PATCH] fence: Use smp_mb__before_atomic() Thierry Reding
2014-05-28 20:16 ` Maarten Lankhorst
2014-05-28 20:51 ` Greg Kroah-Hartman
2014-05-30 8:15 ` Thierry Reding
2014-05-30 16:08 ` Greg Kroah-Hartman
2014-06-04 11:27 ` Sumit Semwal
2014-06-04 13:28 ` Thierry Reding
2014-06-04 17:49 ` Greg Kroah-Hartman
2014-06-05 11:51 ` Rob Clark
2014-06-05 12:00 ` Maarten Lankhorst
2014-06-05 15:52 ` Greg Kroah-Hartman [this message]
2014-06-05 12:26 ` Sumit Semwal
2014-06-05 15:51 ` Greg Kroah-Hartman
2014-06-05 15:48 ` Greg Kroah-Hartman
2014-06-05 16:39 ` Sumit Semwal
2014-06-05 17:49 ` Greg Kroah-Hartman
2014-06-05 21:56 ` Rob Clark
2014-06-04 17:48 ` Greg Kroah-Hartman
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=20140605155200.GC23993@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox