From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/3] intel_memory_region bits
Date: Tue, 8 Oct 2019 17:01:13 +0100 [thread overview]
Message-ID: <20191008160116.18379-1-matthew.auld@intel.com> (raw)
First block of patches from the 'LMEM basics' series.
Matthew Auld (3):
drm/i915: introduce intel_memory_region
drm/i915/region: support contiguous allocations
drm/i915/region: support volatile objects
drivers/gpu/drm/i915/Makefile | 2 +
drivers/gpu/drm/i915/gem/i915_gem_internal.c | 17 +-
drivers/gpu/drm/i915/gem/i915_gem_object.h | 18 ++
.../gpu/drm/i915/gem/i915_gem_object_types.h | 20 ++
drivers/gpu/drm/i915/gem/i915_gem_pages.c | 6 +
drivers/gpu/drm/i915/gem/i915_gem_region.c | 169 +++++++++++
drivers/gpu/drm/i915/gem/i915_gem_region.h | 29 ++
.../gpu/drm/i915/gem/selftests/huge_pages.c | 97 +++++-
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/intel_memory_region.c | 203 +++++++++++++
drivers/gpu/drm/i915/intel_memory_region.h | 90 ++++++
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 5 +-
.../drm/i915/selftests/i915_mock_selftests.h | 1 +
.../drm/i915/selftests/intel_memory_region.c | 280 ++++++++++++++++++
.../gpu/drm/i915/selftests/mock_gem_device.c | 1 +
drivers/gpu/drm/i915/selftests/mock_region.c | 59 ++++
drivers/gpu/drm/i915/selftests/mock_region.h | 16 +
17 files changed, 995 insertions(+), 19 deletions(-)
create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_region.c
create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_region.h
create mode 100644 drivers/gpu/drm/i915/intel_memory_region.c
create mode 100644 drivers/gpu/drm/i915/intel_memory_region.h
create mode 100644 drivers/gpu/drm/i915/selftests/intel_memory_region.c
create mode 100644 drivers/gpu/drm/i915/selftests/mock_region.c
create mode 100644 drivers/gpu/drm/i915/selftests/mock_region.h
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-10-08 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 16:01 Matthew Auld [this message]
2019-10-08 16:01 ` [PATCH 1/3] drm/i915: introduce intel_memory_region Matthew Auld
2019-10-08 16:06 ` Chris Wilson
2019-10-08 16:01 ` [PATCH 2/3] drm/i915/region: support contiguous allocations Matthew Auld
2019-10-08 16:07 ` Chris Wilson
2019-10-08 16:01 ` [PATCH 3/3] drm/i915/region: support volatile objects Matthew Auld
2019-10-08 17:29 ` ✗ Fi.CI.CHECKPATCH: warning for intel_memory_region bits Patchwork
2019-10-08 18:17 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-08 21:36 ` Chris Wilson
2019-10-09 0:04 ` ✓ Fi.CI.IGT: " Patchwork
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=20191008160116.18379-1-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-gfx@lists.freedesktop.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