From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/5] drm/i915/gem: Parallel execbuf WIP.
Date: Fri, 6 Dec 2019 17:43:12 +0100 [thread overview]
Message-ID: <20191206164317.2489743-1-maarten.lankhorst@linux.intel.com> (raw)
Posting this as a RFC, to get some feedback hopefully.
Chris Wilson (2):
drm/i915: Drop inspection of execbuf flags during evict
drm/i915/gem: Extract transient execbuf flags from i915_vma
Maarten Lankhorst (2):
drm/i915: Add an implementation for i915_gem_ww_ctx locking.
drm/i915: Remove locking from i915_gem_object_prepare_read/write
drm/i915: Parallel execbuf wip
drivers/gpu/drm/i915/display/intel_display.c | 6 +-
drivers/gpu/drm/i915/display/intel_overlay.c | 2 +-
.../gpu/drm/i915/gem/i915_gem_client_blt.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_context.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c | 4 +-
drivers/gpu/drm/i915/gem/i915_gem_domain.c | 26 +-
.../gpu/drm/i915/gem/i915_gem_execbuffer.c | 543 ++++++++++--------
drivers/gpu/drm/i915/gem/i915_gem_object.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_object.h | 39 +-
.../gpu/drm/i915/gem/i915_gem_object_blt.c | 2 +-
.../gpu/drm/i915/gem/i915_gem_object_types.h | 9 +
drivers/gpu/drm/i915/gem/i915_gem_pm.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 2 +-
.../gpu/drm/i915/gem/selftests/huge_pages.c | 9 +-
.../i915/gem/selftests/i915_gem_client_blt.c | 2 +-
.../i915/gem/selftests/i915_gem_coherency.c | 24 +-
.../drm/i915/gem/selftests/i915_gem_context.c | 16 +-
.../drm/i915/gem/selftests/i915_gem_mman.c | 4 +-
.../i915/gem/selftests/i915_gem_object_blt.c | 4 +-
.../drm/i915/gem/selftests/i915_gem_phys.c | 2 +-
drivers/gpu/drm/i915/gt/intel_renderstate.c | 9 +-
.../gpu/drm/i915/gt/selftest_workarounds.c | 2 +-
drivers/gpu/drm/i915/gvt/cmd_parser.c | 11 +-
drivers/gpu/drm/i915/i915_cmd_parser.c | 1 +
drivers/gpu/drm/i915/i915_drv.h | 6 -
drivers/gpu/drm/i915/i915_gem.c | 54 +-
drivers/gpu/drm/i915/i915_gem.h | 11 +
drivers/gpu/drm/i915/i915_gem_evict.c | 15 +-
drivers/gpu/drm/i915/i915_vma.h | 11 -
drivers/gpu/drm/i915/selftests/i915_gem.c | 41 ++
drivers/gpu/drm/i915/selftests/i915_vma.c | 2 +-
.../drm/i915/selftests/intel_memory_region.c | 4 +-
32 files changed, 516 insertions(+), 353 deletions(-)
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-12-06 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 16:43 Maarten Lankhorst [this message]
2019-12-06 16:43 ` [Intel-gfx] [PATCH 1/5] drm/i915: Drop inspection of execbuf flags during evict Maarten Lankhorst
2019-12-06 16:43 ` [Intel-gfx] [PATCH 2/5] drm/i915/gem: Extract transient execbuf flags from i915_vma Maarten Lankhorst
2019-12-06 16:43 ` [Intel-gfx] [PATCH 3/5] drm/i915: Add an implementation for i915_gem_ww_ctx locking Maarten Lankhorst
2019-12-06 16:43 ` [Intel-gfx] [PATCH 4/5] drm/i915: Remove locking from i915_gem_object_prepare_read/write Maarten Lankhorst
2019-12-06 16:43 ` [Intel-gfx] [RFC PATCH 5/5] drm/i915: Parallel execbuf wip Maarten Lankhorst
2019-12-06 16:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: Parallel execbuf WIP Patchwork
2019-12-06 17:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=20191206164317.2489743-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.