From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [Intel-gfx] [PATCH v3 0/8] remove rcu support from i915_address_space
Date: Thu, 5 Aug 2021 12:39:08 +0200 [thread overview]
Message-ID: <20210805103916.860853-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
My seemingly trivial but totally not cleanup patch at the end now leaks,
so clearly the fixup in v2 did improve things but I still don't understand
that. Anyway that was fairly orthogonal, so I dropped it for later.
v1: https://lore.kernel.org/dri-devel/20210802154806.3710472-1-daniel.vetter@ffwll.ch/
v2: https://lore.kernel.org/dri-devel/20210804142522.4113021-1-daniel.vetter@ffwll.ch/
Cheers, Daniel
Daniel Vetter (8):
drm/i915: Drop code to handle set-vm races from execbuf
drm/i915: Rename i915_gem_context_get_vm_rcu to
i915_gem_context_get_eb_vm
drm/i915: Use i915_gem_context_get_eb_vm in ctx_getparam
drm/i915: Add i915_gem_context_is_full_ppgtt
drm/i915: Use i915_gem_context_get_eb_vm in intel_context_set_gem
drm/i915: Drop __rcu from gem_context->vm
drm/i915: use xa_lock/unlock for fpriv->vm_xa lookups
drm/i915: Stop rcu support for i915_address_space
drivers/gpu/drm/i915/gem/i915_gem_context.c | 78 ++++---------------
drivers/gpu/drm/i915/gem/i915_gem_context.h | 13 ++--
.../gpu/drm/i915/gem/i915_gem_context_types.h | 2 +-
.../gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +-
.../gpu/drm/i915/gem/selftests/huge_pages.c | 8 +-
.../drm/i915/gem/selftests/i915_gem_context.c | 34 ++++----
drivers/gpu/drm/i915/gt/intel_ggtt.c | 1 -
drivers/gpu/drm/i915/gt/intel_gtt.c | 6 +-
drivers/gpu/drm/i915/gt/intel_gtt.h | 2 +-
drivers/gpu/drm/i915/gt/selftest_execlists.c | 2 +-
drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 4 +-
drivers/gpu/drm/i915/i915_trace.h | 2 +-
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 4 +-
drivers/gpu/drm/i915/selftests/i915_vma.c | 4 +-
15 files changed, 52 insertions(+), 118 deletions(-)
--
2.32.0
next reply other threads:[~2021-08-05 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 10:39 Daniel Vetter [this message]
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 1/8] drm/i915: Drop code to handle set-vm races from execbuf Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 2/8] drm/i915: Rename i915_gem_context_get_vm_rcu to i915_gem_context_get_eb_vm Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 3/8] drm/i915: Use i915_gem_context_get_eb_vm in ctx_getparam Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 4/8] drm/i915: Add i915_gem_context_is_full_ppgtt Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 5/8] drm/i915: Use i915_gem_context_get_eb_vm in intel_context_set_gem Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 6/8] drm/i915: Drop __rcu from gem_context->vm Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 7/8] drm/i915: use xa_lock/unlock for fpriv->vm_xa lookups Daniel Vetter
2021-08-05 10:39 ` [Intel-gfx] [PATCH v3 8/8] drm/i915: Stop rcu support for i915_address_space Daniel Vetter
2021-08-05 12:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for remove rcu support from i915_address_space (rev4) Patchwork
2021-08-05 12:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-05 13:07 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-05 18:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for remove rcu support from i915_address_space (rev5) Patchwork
2021-08-05 18:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-05 19:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-06 20:12 ` [Intel-gfx] ✗ 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=20210805103916.860853-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--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).