From: Thomas Hellstrom <thellstrom@vmware.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
airlied@gmail.com, airlied@redhat.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/gem: Warn on illegal use of the dumb buffer interface v2
Date: Fri, 21 Nov 2014 15:48:33 +0100 [thread overview]
Message-ID: <546F50C1.6070803@vmware.com> (raw)
In-Reply-To: <20141121141419.GU20532@nuc-i3427.alporthouse.com>
On 11/21/2014 03:14 PM, Chris Wilson wrote:
> On Thu, Nov 20, 2014 at 09:56:25AM +0100, Thomas Hellstrom wrote:
>> It happens on occasion that developers of generic user-space applications
>> abuse the dumb buffer API to get hold of drm buffers that they can both
>> mmap() and use for GPU acceleration, using the assumptions that dumb buffers
>> and buffers available for GPU are
>> a) The same type and can be aribtrarily type-casted.
>> b) fully coherent.
> Both (a) and (b) are true for intel and it turns out to be a requirement
> for smooth transitions from the boot splash screens into X, and relied
> upon by userspace.
> -Chris
>
So when you say relied upon by user-space, do you mean generic
user-space or driver-specific user-space?
With that, I mean what component is responsible for deciding that the
dumb buffer can be accelerated? The Intel xorg driver?
/Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-21 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 8:56 [PATCH] drm/gem: Warn on illegal use of the dumb buffer interface v2 Thomas Hellstrom
2014-11-21 14:14 ` Chris Wilson
2014-11-21 14:48 ` Thomas Hellstrom [this message]
2014-11-21 14:51 ` Chris Wilson
2014-11-21 14:59 ` Thomas Hellstrom
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=546F50C1.6070803@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@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