From: Daniel Vetter <daniel@ffwll.ch>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
airlied@linux.ie, puck.chen@hisilicon.com,
dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
z.liuxinliang@hisilicon.com, hdegoede@redhat.com,
kong.kongxinwei@hisilicon.com, ray.huang@amd.com,
zourongrong@gmail.com, sam@ravnborg.org,
christian.koenig@amd.com
Subject: Re: [PATCH v4 00/19] Share TTM code among DRM framebuffer drivers
Date: Mon, 6 May 2019 17:23:20 +0200 [thread overview]
Message-ID: <20190506152320.GJ17751@phenom.ffwll.local> (raw)
In-Reply-To: <20190506142034.kb3lfvw25xbkrkyq@sirius.home.kraxel.org>
On Mon, May 06, 2019 at 04:20:34PM +0200, Gerd Hoffmann wrote:
> On Mon, May 06, 2019 at 03:09:20PM +0200, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 06.05.19 um 14:22 schrieb Gerd Hoffmann:
> > >> GEM VRAM could implement PRIME helpers, which would allow for using
> > >> the generic fbcon.
> > >
> > > bochs_gem_prime_*() functions with this series applied look like you can
> > > just rename them & move over to vram helpers.
> > >
> > > It's not a full prime implementation, specifically actual export/import
> > > isn't there. But pin+vmap (needed by generic fbcon) is implemented.
> >
> > I did have a patch to do this, but then I read that prime requires DMA
> > for buffer sharing and bochs works only because it's emulated.
>
> For actual buffer sharing with other drivers yes because dma-bufs
> typically are a bunch of pages (struct page**) and live in RAM.
>
> Not sure whenever it is possible or useful to place the vram in
> ZONE_DEVICE to get page structs for it, then export buffers located
> in vram that way without copying them over to main memory. I suspect
> most importers would fail to properly setup PCI-PCI dma in that case.
Christian König is working on p2p dma-buf sharing. Not sure that's worth
it for virtual devices, but could be fun to wire up I guess.
-Daniel
>
> > If bochs' implementation is complete enough to be useful for other
> > drivers, I'll add it to the patch set.
>
> It's good enough for generic fbcon.
>
> cheers,
> Gerd
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-06 15:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 8:26 [PATCH v4 00/19] Share TTM code among DRM framebuffer drivers Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 01/19] drm: Add |struct drm_gem_vram_object| and helpers Thomas Zimmermann
2019-05-06 12:31 ` Gerd Hoffmann
2019-05-06 12:58 ` Thomas Zimmermann
2019-05-06 13:17 ` Gerd Hoffmann
2019-05-06 13:53 ` Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 02/19] drm: Add |struct drm_gem_vram_object| callbacks for |struct ttm_bo_driver| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 03/19] drm: Add |struct drm_gem_vram_object| callbacks for |struct drm_driver| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 04/19] drm: Add drm_gem_vram_fill_create_dumb() to create dumb buffers Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 05/19] drm: Add VRAM MM, a simple memory manager for dedicated VRAM Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 06/19] drm: Add default instance for VRAM MM callback functions Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 07/19] drm: Integrate VRAM MM into struct drm_device Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 08/19] drm/ast: Convert AST driver to |struct drm_gem_vram_object| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 09/19] drm/ast: Convert AST driver to VRAM MM Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 10/19] drm/ast: Replace mapping code with drm_gem_vram_{kmap/kunmap}() Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 11/19] drm/bochs: Convert bochs driver to |struct drm_gem_vram_object| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 12/19] drm/bochs: Convert bochs driver to VRAM MM Thomas Zimmermann
2019-05-06 12:40 ` Gerd Hoffmann
2019-05-06 13:15 ` Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 13/19] drm/mgag200: Convert mgag200 driver to |struct drm_gem_vram_object| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 14/19] drm/mgag200: Convert mgag200 driver to VRAM MM Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 15/19] drm/mgag200: Replace mapping code with drm_gem_vram_{kmap/kunmap}() Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 16/19] drm/vboxvideo: Convert vboxvideo driver to |struct drm_gem_vram_object| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 17/19] drm/vboxvideo: Convert vboxvideo driver to VRAM MM Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 18/19] drm/hisilicon: Convert hibmc-drm driver to |struct drm_gem_vram_object| Thomas Zimmermann
2019-05-06 8:26 ` [PATCH v4 19/19] drm/hisilicon: Convert hibmc-drm driver to VRAM MM Thomas Zimmermann
2019-05-06 12:22 ` [PATCH v4 00/19] Share TTM code among DRM framebuffer drivers Gerd Hoffmann
2019-05-06 13:09 ` Thomas Zimmermann
2019-05-06 14:20 ` Gerd Hoffmann
2019-05-06 15:23 ` Daniel Vetter [this message]
2019-05-06 12:43 ` Gerd Hoffmann
2019-05-06 13:05 ` Thomas Zimmermann
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=20190506152320.GJ17751@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=kraxel@redhat.com \
--cc=puck.chen@hisilicon.com \
--cc=ray.huang@amd.com \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=z.liuxinliang@hisilicon.com \
--cc=zourongrong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox