From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: maxime.ripard@bootlin.com, sam@ravnborg.org,
dri-devel@lists.freedesktop.org, airlied@redhat.com,
sean@poorly.run
Subject: Re: [PATCH v3 0/9] Remove explicit locking and kmap arguments from GEM VRAM interface
Date: Thu, 13 Jun 2019 11:44:04 +0200 [thread overview]
Message-ID: <20190613094404.2bk2g7a5pr5uhcvv@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190613073041.29350-1-tzimmermann@suse.de>
On Thu, Jun 13, 2019 at 09:30:32AM +0200, Thomas Zimmermann wrote:
> Drivers should not have to care about internal locking of GEM VRAM objects
> and their memory-mapping structures. This patch set removes both from the
> GEM VRAM interface.
>
> This affects the ast and mgag200 drivers. In places where GEM objects are
> being locked by the driver, the patch converts the lock operation to a pin
> operation. The locking prevented the memory manager from moving the object,
> so pinning is more appropriate.
>
> For the memory mappings, all book-keeping is done by the implementation
> of GEM VRAM. Explicit kmap objects are removed from the module's public
> interfaces. This change mostly affects the cursor handling in ast and
> mgag200, which is being simplified by this patch set.
>
> Future directions: with these patches in place, more code in mode setting
> and fbdev emulation can be shared between ast and mgag200.
>
> The patches have been tested on ast and mgag200 hardware.
>
> v3:
> * document PRIME pin flags
> * pin cursor BOs at current location
> v2:
> * support pinning BOs at current location
> * pin PRIME buffers to current locationA
series:
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-06-13 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 7:30 [PATCH v3 0/9] Remove explicit locking and kmap arguments from GEM VRAM interface Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 1/9] drm/gem-vram: Support pinning buffers to current location Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 2/9] drm/ast: Unpin cursor BO during cleanup Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 3/9] drm/ast: Remove obsolete or unused cursor state Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 4/9] drm/ast: Pin and map cursor source BO during update Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 5/9] drm/ast: Pin framebuffer BO during dirty update Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 6/9] drm/mgag200: " Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 7/9] drm/mgag200: Rewrite cursor handling Thomas Zimmermann
2019-06-13 7:30 ` [PATCH v3 8/9] drm: Remove lock interfaces from GEM VRAM helpers Thomas Zimmermann
2019-06-13 16:34 ` Daniel Vetter
2019-06-13 7:30 ` [PATCH v3 9/9] drm: Remove functions with kmap-object argument " Thomas Zimmermann
2019-06-13 9:44 ` Gerd Hoffmann [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=20190613094404.2bk2g7a5pr5uhcvv@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
--cc=tzimmermann@suse.de \
/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.