dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, daniel@ffwll.ch, kraxel@redhat.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	hdegoede@redhat.com, sean@poorly.run, sam@ravnborg.org,
	emil.l.velikov@gmail.com, lyude@redhat.com, noralf@tronnes.org,
	zou_wei@huawei.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [RFC][PATCH v2 0/4] Support GEM object mappings from I/O memory
Date: Thu,  6 Aug 2020 10:52:35 +0200	[thread overview]
Message-ID: <20200806085239.4606-1-tzimmermann@suse.de> (raw)

DRM's fbdev console uses regular load and store operations to update
framebuffer memory. The bochs driver on sparc64 requires the use of
I/O-specific load and store operations. We have a workaround, but need
a long-term solution to the problem. Previous attempts to resolve the
issue returned an extra is_iomem flag from vmap(), or added a separate
vmap_iomem() callback to GEM objects.

This patchset is yet another iteration with a different idea. Instead
of a raw pointer, vmap() interfaces now return a structure that contains
the buffer address in system or I/O memory, plus a flag that signals
which location the address is in.

Patch #1 updates the vboxvideo driver to match the latest VRAM helpers.
This simplifies the other patches and should be merged in any case.

Patch #2 adds struct drm_gem_membuf, which contains the pointer and flag,
and converts the generic GEM interfaces to use it.

Patch #3 converts vmap/vunmap in GEM object functions and updates most
GEM backends. A few drivers are still missing, but the patch should be
acceptable for an RFC.

Patch #4 changes fbdev helpers to access framebuffer memory either with
system or I/O memcpy functions.

Thomas Zimmermann (4):
  drm/vboxvideo: Use drm_gem_vram_vmap() interfaces
  drm/gem: Update client API to use struct drm_gem_membuf
  drm/gem: Use struct drm_gem_membuf in vmap op and convert GEM backends
  drm/fb_helper: Access framebuffer as I/O memory, if required

 drivers/gpu/drm/ast/ast_cursor.c       |  29 ++-
 drivers/gpu/drm/ast/ast_drv.h          |   2 +-
 drivers/gpu/drm/bochs/bochs_kms.c      |   1 -
 drivers/gpu/drm/drm_client.c           |  25 ++-
 drivers/gpu/drm/drm_fb_helper.c        | 246 ++++++++++++++++++++++---
 drivers/gpu/drm/drm_gem.c              |  28 +--
 drivers/gpu/drm/drm_gem_cma_helper.c   |  15 +-
 drivers/gpu/drm/drm_gem_shmem_helper.c |  31 ++--
 drivers/gpu/drm/drm_gem_vram_helper.c  | 142 +++++---------
 drivers/gpu/drm/drm_internal.h         |   5 +-
 drivers/gpu/drm/drm_prime.c            |  16 +-
 drivers/gpu/drm/mgag200/mgag200_mode.c |  11 +-
 drivers/gpu/drm/qxl/qxl_display.c      |  12 +-
 drivers/gpu/drm/qxl/qxl_draw.c         |  14 +-
 drivers/gpu/drm/qxl/qxl_drv.h          |   6 +-
 drivers/gpu/drm/qxl/qxl_object.c       |  19 +-
 drivers/gpu/drm/qxl/qxl_object.h       |   2 +-
 drivers/gpu/drm/qxl/qxl_prime.c        |  12 +-
 drivers/gpu/drm/tiny/cirrus.c          |  15 +-
 drivers/gpu/drm/tiny/gm12u320.c        |  12 +-
 drivers/gpu/drm/udl/udl_modeset.c      |  10 +-
 drivers/gpu/drm/vboxvideo/vbox_mode.c  |  17 +-
 include/drm/drm_client.h               |   7 +-
 include/drm/drm_device.h               |  26 +++
 include/drm/drm_gem.h                  |   5 +-
 include/drm/drm_gem_cma_helper.h       |   4 +-
 include/drm/drm_gem_shmem_helper.h     |   4 +-
 include/drm/drm_gem_vram_helper.h      |   9 +-
 include/drm/drm_mode_config.h          |  12 --
 29 files changed, 464 insertions(+), 273 deletions(-)

--
2.28.0

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-08-06 11:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  8:52 Thomas Zimmermann [this message]
2020-08-06  8:52 ` [PATCH v2 1/4] drm/vboxvideo: Use drm_gem_vram_vmap() interfaces Thomas Zimmermann
2020-08-06  8:52 ` [PATCH v2 2/4] drm/gem: Update client API to use struct drm_gem_membuf Thomas Zimmermann
2020-08-13 10:26   ` Daniel Vetter
2020-08-13 10:46     ` Thomas Zimmermann
2020-08-13 14:03       ` Daniel Vetter
2020-08-14  6:47     ` Thomas Zimmermann
2020-08-06  8:52 ` [PATCH v2 3/4] drm/gem: Use struct drm_gem_membuf in vmap op and convert GEM backends Thomas Zimmermann
2020-08-06  8:52 ` [PATCH v2 4/4] drm/fb_helper: Access framebuffer as I/O memory, if required Thomas Zimmermann
2020-08-14  6:51 ` [RFC][PATCH v2 0/4] Support GEM object mappings from I/O memory 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=20200806085239.4606-1-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=noralf@tronnes.org \
    --cc=sam@ravnborg.org \
    --cc=sean@poorly.run \
    --cc=zou_wei@huawei.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;
as well as URLs for NNTP newsgroup(s).