From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Eric Anholt <eric.anholt@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] introduce intel_ring_buffer structure
Date: Wed, 19 May 2010 18:33:31 +0100 [thread overview]
Message-ID: <201005191833.31825.simon.farnsworth@onelan.com> (raw)
In-Reply-To: <87tyq3esrj.fsf@pollan.anholt.net>
On Wednesday 19 May 2010, Eric Anholt <eric.anholt@intel.com> wrote:
> On Wed, 19 May 2010 10:00:10 +0100, Simon Farnsworth
<simon.farnsworth@onelan.com> wrote:
> > Bear in mind that I don't have to use VAAPI to call your ioctl; I can
> > write evil code that calls it directly. On the other hand, you can't
> > remove the ioctl later - users will want to use older VAAPI versions
> > with new kernels, so that they can upgrade without too much fear of
> > regression.
>
> OK, now you're going over the top. The GPU can't schedule[1], is turing
> complete, and you hand it programs. You can hang it with or without his
> interface. If you don't want to be able to do that, then don't let
> non-root use the DRI.
>
Fair enough, and my apologies for going overboard - my intended point is that
just because VAAPI is the only planned user of this ioctl doesn't mean that
it's OK to get the userspace/kernel interface wrong.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
next prev parent reply other threads:[~2010-05-19 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 1:20 [PATCH 1/4] introduce intel_ring_buffer structure Zou Nan hai
2010-05-06 1:20 ` [PATCH 2/4] convert render engine to use intel_ring_buffer Zou Nan hai
2010-05-06 1:20 ` [PATCH 3/4] add BSD ring buffer support Zou Nan hai
2010-05-06 1:20 ` [PATCH 4/4] adapt intel_ring_buffer into gem Zou Nan hai
2010-05-07 21:34 ` [PATCH 1/4] introduce intel_ring_buffer structure Eric Anholt
2010-05-08 18:15 ` Thomas Bächler
2010-05-11 22:24 ` Daniel Vetter
2010-05-14 1:39 ` Zou, Nanhai
2010-05-14 9:51 ` Daniel Vetter
2010-05-14 15:03 ` Daniel Vetter
2010-05-17 1:59 ` Zou, Nanhai
2010-05-17 17:52 ` Daniel Vetter
2010-05-14 17:43 ` Owain Ainsworth
2010-05-17 1:43 ` Zou, Nanhai
2010-05-17 17:42 ` Daniel Vetter
2010-05-18 2:20 ` Zou, Nanhai
2010-05-18 16:19 ` Simon Farnsworth
2010-05-19 1:09 ` Zou, Nanhai
2010-05-19 9:00 ` Simon Farnsworth
2010-05-19 16:54 ` Eric Anholt
2010-05-19 17:33 ` Simon Farnsworth [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 3:17 Zou Nan hai
2010-05-05 18:23 ` Daniel Vetter
2010-05-06 2:25 ` Zou, Nanhai
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=201005191833.31825.simon.farnsworth@onelan.com \
--to=simon.farnsworth@onelan.com \
--cc=eric.anholt@intel.com \
--cc=intel-gfx@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 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.