From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/7] drm/radeon: implement unpin function
Date: Tue, 09 Apr 2013 16:26:56 +0200 [thread overview]
Message-ID: <51642530.8080907@canonical.com> (raw)
In-Reply-To: <CAH3drwZYJXAL=3Fd9QYAL5Q8Y+6HfsFtxatXgxBjErxLCYSF1Q@mail.gmail.com>
Op 09-04-13 16:16, Jerome Glisse schreef:
> On Tue, Apr 9, 2013 at 7:37 AM, Maarten Lankhorst
> <m.b.lankhorst@gmail.com>wrote:
>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
>>
> Can userspace pin directly ? If so then that sounds as a bad idea.
>
> Reviewed-by: Jerome Glisse <jglisse@redhat.com>
>
It's slightly better than before, it used to pin as soon as you export a buffer for as long as the buffer exists, with the series the pinning will only happen when importing to another device, until the device releases their reference.
~Maarten
next prev parent reply other threads:[~2013-04-09 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 11:37 [PATCH 1/7] drm: add unpin function to prime helpers Maarten Lankhorst
2013-04-09 11:37 ` [PATCH 2/7] drm: move pinning/unpinning to buffer attach Maarten Lankhorst
2013-04-09 11:37 ` [PATCH 3/7] drm/radeon: implement unpin function Maarten Lankhorst
2013-04-09 14:16 ` Jerome Glisse
2013-04-09 14:26 ` Maarten Lankhorst [this message]
2013-04-09 14:53 ` Daniel Vetter
2013-04-09 11:37 ` [PATCH 4/7] drm/nouveau: implement prime helper " Maarten Lankhorst
2013-04-09 11:37 ` [PATCH 5/7] drm/nouveau: unpin notify object in chan_fini Maarten Lankhorst
2013-04-09 11:37 ` [PATCH 6/7] drm/nouveau: fixup fbcon failure paths Maarten Lankhorst
2013-04-09 11:37 ` [PATCH 7/7] drm/nouveau: complain loudly if buffer is pinned during destruction Maarten Lankhorst
2013-04-09 13:01 ` [PATCH 1/7] drm: add unpin function to prime helpers Daniel Vetter
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=51642530.8080907@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.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.