From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, kraxel@redhat.com, airlied@linux.ie,
corbet@lwn.net, z.liuxinliang@hisilicon.com,
zourongrong@gmail.com, kong.kongxinwei@hisilicon.com,
puck.chen@hisilicon.com, hdegoede@redhat.com, sam@ravnborg.org,
yc_chen@aspeedtech.com
Cc: virtualization@lists.linux-foundation.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org
Subject: [PATCH v2 0/4] Merge VRAM MM and GEM VRAM source files
Date: Wed, 11 Sep 2019 13:09:06 +0200 [thread overview]
Message-ID: <20190911110910.30698-1-tzimmermann@suse.de> (raw)
VRAM MM and GEM VRAM are only used with each other. This patch set
moves VRAM MM into GEM VRAM source files and cleans up the helper's
public interface.
Version 2 of the patch set doesn't contain functional changes. I'm
reposting due to the rebasing onto the debugfs patches.
v2:
* updated for debugfs support
* fixed typos in comments
Thomas Zimmermann (4):
drm/vram: Move VRAM memory manager to GEM VRAM implementation
drm/vram: Have VRAM MM call GEM VRAM functions directly
drm/vram: Unexport internal functions of VRAM MM
drm/vram: Unconditonally set BO call-back functions
Documentation/gpu/drm-mm.rst | 12 -
drivers/gpu/drm/Makefile | 3 +-
drivers/gpu/drm/ast/ast_drv.c | 1 -
drivers/gpu/drm/ast/ast_main.c | 1 -
drivers/gpu/drm/ast/ast_ttm.c | 3 +-
drivers/gpu/drm/bochs/bochs.h | 1 -
drivers/gpu/drm/bochs/bochs_mm.c | 3 +-
drivers/gpu/drm/drm_gem_vram_helper.c | 406 +++++++++++++++---
drivers/gpu/drm/drm_vram_helper_common.c | 8 +-
drivers/gpu/drm/drm_vram_mm_helper.c | 353 ---------------
.../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 1 -
drivers/gpu/drm/hisilicon/hibmc/hibmc_ttm.c | 3 +-
drivers/gpu/drm/mgag200/mgag200_drv.h | 1 -
drivers/gpu/drm/mgag200/mgag200_ttm.c | 3 +-
drivers/gpu/drm/vboxvideo/vbox_drv.h | 2 -
drivers/gpu/drm/vboxvideo/vbox_ttm.c | 3 +-
include/drm/drm_gem_vram_helper.h | 92 +++-
include/drm/drm_vram_mm_helper.h | 109 -----
18 files changed, 421 insertions(+), 584 deletions(-)
delete mode 100644 drivers/gpu/drm/drm_vram_mm_helper.c
delete mode 100644 include/drm/drm_vram_mm_helper.h
--
2.23.0
next reply other threads:[~2019-09-11 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 11:09 Thomas Zimmermann [this message]
2019-09-11 11:09 ` [PATCH v2 1/4] drm/vram: Move VRAM memory manager to GEM VRAM implementation Thomas Zimmermann
2019-09-11 11:09 ` [PATCH v2 2/4] drm/vram: Have VRAM MM call GEM VRAM functions directly Thomas Zimmermann
2019-09-11 11:09 ` [PATCH v2 3/4] drm/vram: Unexport internal functions of VRAM MM Thomas Zimmermann
2019-09-11 11:09 ` [PATCH v2 4/4] drm/vram: Unconditonally set BO call-back functions 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=20190911110910.30698-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=kraxel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=sam@ravnborg.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yc_chen@aspeedtech.com \
--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;
as well as URLs for NNTP newsgroup(s).