From: Daniel Vetter <daniel@ffwll.ch>
To: Thierry Reding <treding@nvidia.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Clark <robdclark@gmail.com>, Dave Airlie <airlied@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Tom Gall <tom.gall@linaro.org>
Subject: Re: [RFC] How implement Secure Data Path ?
Date: Thu, 7 May 2015 15:52:12 +0200 [thread overview]
Message-ID: <20150507135212.GD30184@phenom.ffwll.local> (raw)
In-Reply-To: <20150507132218.GA24541@ulmo.nvidia.com>
On Thu, May 07, 2015 at 03:22:20PM +0200, Thierry Reding wrote:
> On Wed, May 06, 2015 at 03:15:32PM +0200, Daniel Vetter wrote:
> > Yes the idea would be a special-purpose allocater thing like ion. Might
> > even want that to be a syscall to do it properly.
>
> Would you care to elaborate why a syscall would be more proper? Not that
> I'm objecting to it, just for my education.
It seems to be the theme with someone proposing a global /dev node for a
few system wide ioctls, then reviewers ask to make a proper ioctl out of
it. E.g. kdbus, but I have vague memory of this happening a lot.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2015-05-07 13:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:39 [RFC] How implement Secure Data Path ? Benjamin Gaignard
2015-05-05 16:27 ` Christoph Hellwig
2015-05-06 0:50 ` Laurent Pinchart
2015-05-06 8:37 ` Daniel Vetter
2015-05-05 16:54 ` One Thousand Gnomes
2015-05-06 8:35 ` Daniel Vetter
2015-05-06 8:49 ` Hans Verkuil
2015-05-06 9:19 ` Thierry Reding
2015-05-06 13:15 ` Daniel Vetter
2015-05-07 13:22 ` Thierry Reding
2015-05-07 13:52 ` Daniel Vetter [this message]
2015-05-07 16:40 ` One Thousand Gnomes
2015-05-08 8:37 ` Daniel Vetter
2015-05-08 8:55 ` Enrico Weigelt, metux IT consult
2015-05-08 19:18 ` One Thousand Gnomes
2015-05-12 8:46 ` Benjamin Gaignard
2015-05-06 9:22 ` Benjamin Gaignard
2015-05-06 11:29 ` Rob Clark
2015-05-07 14:41 ` Thierry Reding
2015-05-06 8:46 ` Benjamin Gaignard
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=20150507135212.GD30184@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@redhat.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.org \
--cc=treding@nvidia.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