From: Eugeni Dodonov <eugeni.dodonov@linux.intel.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4 v6] drm/i915: wait render timeout ioctl
Date: Fri, 11 May 2012 20:09:19 -0300 [thread overview]
Message-ID: <4FAD9C1F.5060303@linux.intel.com> (raw)
In-Reply-To: <1336769652-11740-3-git-send-email-ben@bwidawsk.net>
On 05/11/2012 05:54 PM, Ben Widawsky wrote:
> @@ -1800,6 +1800,7 @@ struct drm_ioctl_desc i915_ioctls[] = {
> DRM_IOCTL_DEF_DRV(I915_OVERLAY_ATTRS, intel_overlay_attrs, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED),
> DRM_IOCTL_DEF_DRV(I915_SET_SPRITE_COLORKEY, intel_sprite_set_colorkey, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED),
> DRM_IOCTL_DEF_DRV(I915_GET_SPRITE_COLORKEY, intel_sprite_get_colorkey, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED),
> + DRM_IOCTL_DEF_DRV(I915_GEM_WAIT, i915_gem_wait_ioctl, DRM_UNLOCKED),
> };
I was just wondering (not directly related to this patch, but more
thinking on the overall gem flow) - don't we want to use DRM_AUTH here?
next prev parent reply other threads:[~2012-05-11 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 20:54 [PATCH 1/4 v4] drm/i915: timeout parameter for seqno wait Ben Widawsky
2012-05-11 20:54 ` [PATCH 2/4 v3] drm/i915: improve i915_wait_request_begin trace Ben Widawsky
2012-05-11 20:54 ` [PATCH 3/4 v6] drm/i915: wait render timeout ioctl Ben Widawsky
2012-05-11 23:09 ` Eugeni Dodonov [this message]
2012-05-12 21:07 ` Ben Widawsky
2012-05-11 20:54 ` [PATCH 4/4] drm/i915: s/i915_wait_reqest/i915_wait_seqno/g Ben Widawsky
2012-05-11 22:56 ` Eugeni Dodonov
2012-05-12 21:20 ` Ben Widawsky
2012-05-11 20:54 ` [PATCH] intel: add a timed wait function Ben Widawsky
2012-05-11 20:54 ` [PATCH] tests/wait render timeout test Ben Widawsky
2012-05-11 23:09 ` [PATCH 1/4 v4] drm/i915: timeout parameter for seqno wait Eugeni Dodonov
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=4FAD9C1F.5060303@linux.intel.com \
--to=eugeni.dodonov@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=eugeni.dodonov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox