All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] [PATCH 13/33] drm/i915/gt: Protect context lifetime with RCU
Date: Fri, 13 Nov 2020 09:41:08 +0000	[thread overview]
Message-ID: <20201113094128.8740-13-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20201113094128.8740-1-chris@chris-wilson.co.uk>

Allow a brief period for continued access to a dead intel_context by
deferring the release of the struct until after an RCU grace period.
As we are using a dedicated slab cache for the contexts, we can defer
the release of the slab pages via RCU, with the caveat that individual
structs may be reused from the freelist within an RCU grace period. To
handle that, we have to avoid clearing members of the zombie struct.

This is required for a later patch to handle locking around virtual
requests in the signaler, as those requests may want to move between
engines and be destroyed while we are holding b->irq_lock on a physical
engine.

v2: Drop mutex_reinit(), if we never mark the mutex as destroyed we
don't need to reset the debug code, at the loss of having the mutex
debug code spot us attempting to destroy a locked mutex.
v3: As the intended use will remain strongly referenced counted, with
very little inflight access across reuse, drop the ctor.
v4: Drop the unrequired change to remove the temporary reference around
dropping the active context, and add back some more missing ctor
operations.
v5: The ctor is back. Tvrtko spotted that ce->signal_lock [introduced
later] maybe accessed under RCU and so needs special care not to be
reinitialised.
v6: Don't mix SLAB_TYPESAFE_BY_RCU and RCU list iteration.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/gt/intel_context.c       | 12 +++++++++---
 drivers/gpu/drm/i915/gt/intel_context_types.h | 11 ++++++++++-
 2 files changed, 19 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/gt/intel_context.c b/drivers/gpu/drm/i915/gt/intel_context.c
index 92a3f25c4006..d3a835212167 100644
--- a/drivers/gpu/drm/i915/gt/intel_context.c
+++ b/drivers/gpu/drm/i915/gt/intel_context.c
@@ -25,11 +25,18 @@ static struct intel_context *intel_context_alloc(void)
 	return kmem_cache_zalloc(global.slab_ce, GFP_KERNEL);
 }
 
-void intel_context_free(struct intel_context *ce)
+static void rcu_context_free(struct rcu_head *rcu)
 {
+	struct intel_context *ce = container_of(rcu, typeof(*ce), rcu);
+
 	kmem_cache_free(global.slab_ce, ce);
 }
 
+void intel_context_free(struct intel_context *ce)
+{
+	call_rcu(&ce->rcu, rcu_context_free);
+}
+
 struct intel_context *
 intel_context_create(struct intel_engine_cs *engine)
 {
@@ -356,8 +363,7 @@ static int __intel_context_active(struct i915_active *active)
 }
 
 void
-intel_context_init(struct intel_context *ce,
-		   struct intel_engine_cs *engine)
+intel_context_init(struct intel_context *ce, struct intel_engine_cs *engine)
 {
 	GEM_BUG_ON(!engine->cops);
 	GEM_BUG_ON(!engine->gt->vm);
diff --git a/drivers/gpu/drm/i915/gt/intel_context_types.h b/drivers/gpu/drm/i915/gt/intel_context_types.h
index 552cb57a2e8c..20cb5835d1c3 100644
--- a/drivers/gpu/drm/i915/gt/intel_context_types.h
+++ b/drivers/gpu/drm/i915/gt/intel_context_types.h
@@ -44,7 +44,16 @@ struct intel_context_ops {
 };
 
 struct intel_context {
-	struct kref ref;
+	/*
+	 * Note: Some fields may be accessed under RCU.
+	 *
+	 * Unless otherwise noted a field can safely be assumed to be protected
+	 * by strong reference counting.
+	 */
+	union {
+		struct kref ref; /* no kref_get_unless_zero()! */
+		struct rcu_head rcu;
+	};
 
 	struct intel_engine_cs *engine;
 	struct intel_engine_cs *inflight;
-- 
2.20.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-11-13  9:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:40 [Intel-gfx] [PATCH 01/33] drm/i915/gt: Include semaphore status in print_request() Chris Wilson
2020-11-13  9:40 ` [Intel-gfx] [PATCH 02/33] drm/i915: Lift i915_request_show() Chris Wilson
2020-11-13  9:40 ` [Intel-gfx] [PATCH 03/33] drm/i915/gt: Show all active timelines for debugging Chris Wilson
2020-11-13  9:40 ` [Intel-gfx] [PATCH 04/33] drm/i915: Lift waiter/signaler iterators Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 05/33] drm/i915: Show timeline dependencies for debug Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 06/33] drm/i915/selftests: Improve granularity for mocs reset checks Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 07/33] drm/i915/gem: Drop free_work for GEM contexts Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 08/33] drm/i915/gt: Ignore dt==0 for reporting underflows Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 09/33] drm/i915/gt: Defer enabling the breadcrumb interrupt to after submission Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 10/33] drm/i915/gt: Track signaled breadcrumbs outside of the breadcrumb spinlock Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 11/33] drm/i915/gt: Don't cancel the interrupt shadow too early Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 12/33] drm/i915/gt: Free stale request on destroying the virtual engine Chris Wilson
2020-11-13  9:41 ` Chris Wilson [this message]
2020-11-13  9:41 ` [Intel-gfx] [PATCH 14/33] drm/i915/gt: Split the breadcrumb spinlock between global and contexts Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 15/33] drm/i915/gt: Move the breadcrumb to the signaler if completed upon cancel Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 16/33] drm/i915/gt: Decouple completed requests on unwind Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 17/33] drm/i915/gt: Check for a completed last request once Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 18/33] drm/i915/gt: Replace direct submit with direct call to tasklet Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 19/33] drm/i915/gt: ce->inflight updates are now serialised Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 20/33] drm/i915/gt: Use virtual_engine during execlists_dequeue Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 21/33] drm/i915/gt: Decouple inflight virtual engines Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 22/33] drm/i915/gt: Defer schedule_out until after the next dequeue Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 23/33] drm/i915/gt: Remove virtual breadcrumb before transfer Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 24/33] drm/i915/gt: Shrink the critical section for irq signaling Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 25/33] drm/i915/gt: Resubmit the virtual engine on schedule-out Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 26/33] drm/i915/gt: Simplify virtual engine handling for execlists_hold() Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 27/33] drm/i915: Encode fence specific waitqueue behaviour into the wait.flags Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 28/33] drm/i915/gt: Wrap intel_timeline.has_initial_breadcrumb Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 29/33] drm/i915/gt: Track timeline GGTT offset separately from subpage offset Chris Wilson
2020-11-13  9:49   ` Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 30/33] drm/i915/gt: Add timeline "mode" Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 31/33] drm/i915/gt: Use indices for writing into relative timelines Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 32/33] drm/i915/selftests: Exercise relative timeline modes Chris Wilson
2020-11-13  9:41 ` [Intel-gfx] [PATCH 33/33] drm/i915/gt: Use ppHWSP for unshared non-semaphore related timelines Chris Wilson
2020-11-13 10:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/33] drm/i915/gt: Include semaphore status in print_request() Patchwork
2020-11-13 10:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-11-13 11:06 ` [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=20201113094128.8740-13-chris@chris-wilson.co.uk \
    --to=chris@chris-wilson.co.uk \
    --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.