From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: Gerd Hoffmann <kraxel@redhat.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
virtualization@lists.linux-foundation.org (open list:VIRTIO GPU
DRIVER), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 2/3] drm/virtio: implement prime pin/unpin
Date: Wed, 27 Feb 2019 15:44:40 +0100 [thread overview]
Message-ID: <20190227144441.6755-3-kraxel@redhat.com> (raw)
In-Reply-To: <20190227144441.6755-1-kraxel@redhat.com>
virtio-gpu objects never move around, so effectively they are pinned
all the time. This makes the the implementation pretty easy ;)
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
drivers/gpu/drm/virtio/virtgpu_prime.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_prime.c b/drivers/gpu/drm/virtio/virtgpu_prime.c
index b4c9199349e7..0fcae0e46abd 100644
--- a/drivers/gpu/drm/virtio/virtgpu_prime.c
+++ b/drivers/gpu/drm/virtio/virtgpu_prime.c
@@ -30,13 +30,13 @@
int virtgpu_gem_prime_pin(struct drm_gem_object *obj)
{
- WARN_ONCE(1, "not implemented");
- return -ENODEV;
+ /* nothing: all virtio-gpu objects are pinned all the time */
+ return 0;
}
void virtgpu_gem_prime_unpin(struct drm_gem_object *obj)
{
- WARN_ONCE(1, "not implemented");
+ /* nothing */
}
void *virtgpu_gem_prime_vmap(struct drm_gem_object *obj)
--
2.9.3
next prev parent reply other threads:[~2019-02-27 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190227144441.6755-1-kraxel@redhat.com>
2019-02-27 14:44 ` [PATCH 1/3] drm/virtio: implement prime mmap Gerd Hoffmann
2019-02-27 17:11 ` Noralf Trønnes
2019-02-27 14:44 ` Gerd Hoffmann [this message]
2019-02-27 17:07 ` [PATCH 2/3] drm/virtio: implement prime pin/unpin Noralf Trønnes
2019-02-27 14:44 ` [PATCH 3/3] drm/virtio: implement prime export Gerd Hoffmann
2019-02-27 17:11 ` Noralf Trønnes
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=20190227144441.6755-3-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).