From: Jason Ekstrand <jason@jlekstrand.net>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Jason Ekstrand <jason@jlekstrand.net>
Subject: [PATCH 0/8] drm/i915: Migrate memory to SMEM when imported cross-device (v8)
Date: Fri, 23 Jul 2021 12:21:34 -0500 [thread overview]
Message-ID: <20210723172142.3273510-1-jason@jlekstrand.net> (raw)
This patch series fixes an issue with discrete graphics on Intel where we
allowed dma-buf import while leaving the object in local memory. This
breaks down pretty badly if the import happened on a different physical
device.
v7:
- Drop "drm/i915/gem/ttm: Place new BOs in the requested region"
- Add a new "drm/i915/gem: Call i915_gem_flush_free_objects() in i915_gem_dumb_create()"
- Misc. review feedback from Matthew Auld
v8:
- Misc. review feedback from Matthew Auld
v9:
- Replace the i915/ttm patch with two that are hopefully more correct
Jason Ekstrand (6):
drm/i915/gem: Check object_can_migrate from object_migrate
drm/i915/gem: Refactor placement setup for i915_gem_object_create*
(v2)
drm/i915/gem: Call i915_gem_flush_free_objects() in
i915_gem_dumb_create()
drm/i915/gem: Unify user object creation (v3)
drm/i915/gem/ttm: Only call __i915_gem_object_set_pages if needed
drm/i915/gem: Always call obj->ops->migrate unless can_migrate fails
Thomas Hellström (2):
drm/i915/gem: Correct the locking and pin pattern for dma-buf (v8)
drm/i915/gem: Migrate to system at dma-buf attach time (v7)
drivers/gpu/drm/i915/gem/i915_gem_create.c | 177 ++++++++--------
drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c | 58 ++++--
drivers/gpu/drm/i915/gem/i915_gem_object.c | 20 +-
drivers/gpu/drm/i915/gem/i915_gem_object.h | 4 +
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 13 +-
.../drm/i915/gem/selftests/i915_gem_dmabuf.c | 190 +++++++++++++++++-
.../drm/i915/gem/selftests/i915_gem_migrate.c | 15 --
7 files changed, 341 insertions(+), 136 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-23 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 17:21 Jason Ekstrand [this message]
2021-07-23 17:21 ` [PATCH 1/8] drm/i915/gem: Check object_can_migrate from object_migrate Jason Ekstrand
2021-07-23 17:21 ` [PATCH 2/8] drm/i915/gem: Refactor placement setup for i915_gem_object_create* (v2) Jason Ekstrand
2021-07-23 17:21 ` [PATCH 3/8] drm/i915/gem: Call i915_gem_flush_free_objects() in i915_gem_dumb_create() Jason Ekstrand
2021-07-23 17:21 ` [PATCH 4/8] drm/i915/gem: Unify user object creation (v3) Jason Ekstrand
2021-07-23 17:21 ` [PATCH 5/8] drm/i915/gem/ttm: Only call __i915_gem_object_set_pages if needed Jason Ekstrand
2021-07-26 8:08 ` [Intel-gfx] " Matthew Auld
2021-07-23 17:21 ` [PATCH 6/8] drm/i915/gem: Always call obj->ops->migrate unless can_migrate fails Jason Ekstrand
2021-07-26 8:10 ` [Intel-gfx] " Matthew Auld
2021-07-23 17:21 ` [PATCH 7/8] drm/i915/gem: Correct the locking and pin pattern for dma-buf (v8) Jason Ekstrand
2021-09-01 10:18 ` [Intel-gfx] " Thomas Hellström (Intel)
2021-07-23 17:21 ` [PATCH 8/8] drm/i915/gem: Migrate to system at dma-buf attach time (v7) Jason Ekstrand
2021-07-26 8:12 ` [Intel-gfx] [PATCH 0/8] drm/i915: Migrate memory to SMEM when imported cross-device (v8) Matthew Auld
2021-07-26 15:11 ` Jason Ekstrand
2021-07-26 15:28 ` Matthew Auld
2021-07-26 15:32 ` Jason Ekstrand
2021-07-26 15:56 ` Matthew Auld
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=20210723172142.3273510-1-jason@jlekstrand.net \
--to=jason@jlekstrand.net \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).