From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Simplify i915_gem_obj_is_pinned() test for set-tiling
Date: Thu, 16 Apr 2015 16:08:05 +0200 [thread overview]
Message-ID: <20150416140805.GH5082@phenom.ffwll.local> (raw)
In-Reply-To: <20150416105004.GA16653@nuc-i3427.alporthouse.com>
On Thu, Apr 16, 2015 at 11:50:04AM +0100, Chris Wilson wrote:
> On Thu, Apr 16, 2015 at 11:03:20AM +0200, Daniel Vetter wrote:
> > On Wed, Apr 15, 2015 at 04:39:59PM +0100, Chris Wilson wrote:
> > > Since the removal of the user pin_ioctl, the only means for pinning an
> > > object is either through binding to the scanout or during execbuf
> > > reservation. As the later prevents a call to set-tiling, we need only
> > > check if the obj is pinned into the display plane to see if we need
> > > reject the set-tiling ioctl.
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Queued for -next, thanks for the patch.
>
> I was wondering if I could get away with framebuffer_references now that
> we do allocate fb for everything, but was too lazy to actually check.
>
> Gut feeling?
legacy overlay is still using plain buffers unfortunately :(
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-04-16 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:39 [PATCH] drm/i915: Simplify i915_gem_obj_is_pinned() test for set-tiling Chris Wilson
2015-04-16 4:55 ` shuang.he
2015-04-16 9:03 ` Daniel Vetter
2015-04-16 10:50 ` Chris Wilson
2015-04-16 14:08 ` Daniel Vetter [this message]
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=20150416140805.GH5082@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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