From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: "Zou, Nanhai" <nanhai.zou@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Anholt, Eric" <eric.anholt@intel.com>
Subject: Re: [PATCH 1/4] introduce intel_ring_buffer structure
Date: Wed, 19 May 2010 10:00:10 +0100 [thread overview]
Message-ID: <201005191000.11272.simon.farnsworth@onelan.com> (raw)
In-Reply-To: <41EFD7A46E18724CAB128DAD0073348006A65A1B45@shsmsx502.ccr.corp.intel.com>
On Wednesday 19 May 2010, "Zou, Nanhai" <nanhai.zou@intel.com> wrote:
> Currently we do not find any regression or slowness. We have been testing
> full HD video test along with regression tests for more than 1 month. The
> only slowness we find now is with playing 2 1080p H.264 video. That was
> caused by too much GPU memory usage which is not related to the interface.
>
And are you utterly confident that if anyone finds a way to use your new ioctl
to (e.g.) hang the GPU, stall rendering indefinitely waiting for media engine
events that will never happen, or perhaps bypass system security, you can fix
it without changing the ioctl interface to userspace? If not, you have a
problem, and need to redesign the ioctl.
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.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
next prev parent reply other threads:[~2010-05-19 9:00 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 [this message]
2010-05-19 16:54 ` Eric Anholt
2010-05-19 17:33 ` Simon Farnsworth
-- 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=201005191000.11272.simon.farnsworth@onelan.com \
--to=simon.farnsworth@onelan.com \
--cc=eric.anholt@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nanhai.zou@intel.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 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.