From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Cc: Maciej Patelczyk <maciej.patelczyk@intel.com>,
Chris Wilson <chris.p.wilson@linux.intel.com>,
Andi Shyti <andi.shyti@kernel.org>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 1/5] drm/i915: Throttle for ringspace prior to taking the timeline mutex
Date: Tue, 11 Apr 2023 10:58:53 +0200 [thread overview]
Message-ID: <3e306d18-de86-8903-2116-6443c26672ab@intel.com> (raw)
In-Reply-To: <20230308094106.203686-2-andi.shyti@linux.intel.com>
On 08.03.2023 10:41, Andi Shyti wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> Before taking exclusive ownership of the ring for emitting the request,
> wait for space in the ring to become available. This allows others to
> take the timeline->mutex to make forward progresses while userspace is
> blocked.
>
> In particular, this allows regular clients to issue requests on the
> kernel context, potentially filling the ring, but allow the higher
> priority heartbeats and pulses to still be submitted without being
> blocked by the less critical work.
>
> Signed-off-by: Chris Wilson <chris.p.wilson@linux.intel.com>
> Cc: Maciej Patelczyk <maciej.patelczyk@intel.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Regards
Andrzej
> ---
> drivers/gpu/drm/i915/gt/intel_context.c | 41 +++++++++++++++++++++++++
> drivers/gpu/drm/i915/gt/intel_context.h | 2 ++
> drivers/gpu/drm/i915/i915_request.c | 3 ++
> 3 files changed, 46 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_context.c b/drivers/gpu/drm/i915/gt/intel_context.c
> index 2aa63ec521b89..59cd612a23561 100644
> --- a/drivers/gpu/drm/i915/gt/intel_context.c
> +++ b/drivers/gpu/drm/i915/gt/intel_context.c
> @@ -626,6 +626,47 @@ bool intel_context_revoke(struct intel_context *ce)
> return ret;
> }
>
> +int intel_context_throttle(const struct intel_context *ce)
> +{
> + const struct intel_ring *ring = ce->ring;
> + const struct intel_timeline *tl = ce->timeline;
> + struct i915_request *rq;
> + int err = 0;
> +
> + if (READ_ONCE(ring->space) >= SZ_1K)
> + return 0;
> +
> + rcu_read_lock();
> + list_for_each_entry_reverse(rq, &tl->requests, link) {
> + if (__i915_request_is_complete(rq))
> + break;
> +
> + if (rq->ring != ring)
> + continue;
> +
> + /* Wait until there will be enough space following that rq */
> + if (__intel_ring_space(rq->postfix,
> + ring->emit,
> + ring->size) < ring->size / 2) {
> + if (i915_request_get_rcu(rq)) {
> + rcu_read_unlock();
> +
> + if (i915_request_wait(rq,
> + I915_WAIT_INTERRUPTIBLE,
> + MAX_SCHEDULE_TIMEOUT) < 0)
> + err = -EINTR;
> +
> + rcu_read_lock();
> + i915_request_put(rq);
> + }
> + break;
> + }
> + }
> + rcu_read_unlock();
> +
> + return err;
> +}
> +
> #if IS_ENABLED(CONFIG_DRM_I915_SELFTEST)
> #include "selftest_context.c"
> #endif
> diff --git a/drivers/gpu/drm/i915/gt/intel_context.h b/drivers/gpu/drm/i915/gt/intel_context.h
> index 0a8d553da3f43..f919a66cebf5b 100644
> --- a/drivers/gpu/drm/i915/gt/intel_context.h
> +++ b/drivers/gpu/drm/i915/gt/intel_context.h
> @@ -226,6 +226,8 @@ static inline void intel_context_exit(struct intel_context *ce)
> ce->ops->exit(ce);
> }
>
> +int intel_context_throttle(const struct intel_context *ce);
> +
> static inline struct intel_context *intel_context_get(struct intel_context *ce)
> {
> kref_get(&ce->ref);
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 630a732aaecca..72aed544f8714 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -1034,6 +1034,9 @@ i915_request_create(struct intel_context *ce)
> struct i915_request *rq;
> struct intel_timeline *tl;
>
> + if (intel_context_throttle(ce))
> + return ERR_PTR(-EINTR);
> +
> tl = intel_context_timeline_lock(ce);
> if (IS_ERR(tl))
> return ERR_CAST(tl);
next prev parent reply other threads:[~2023-04-11 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 9:41 [Intel-gfx] [PATCH v4 0/5] Fix error propagation amongst request Andi Shyti
2023-03-08 9:41 ` [Intel-gfx] [PATCH v4 1/5] drm/i915: Throttle for ringspace prior to taking the timeline mutex Andi Shyti
2023-04-11 8:58 ` Andrzej Hajda [this message]
2023-03-08 9:41 ` [Intel-gfx] [PATCH v4 2/5] drm/i915/gt: Add intel_context_timeline_is_locked helper Andi Shyti
2023-04-11 6:30 ` Das, Nirmoy
2023-03-08 9:41 ` [Intel-gfx] [PATCH v4 3/5] drm/i915: Create the locked version of the request create Andi Shyti
2023-04-11 6:30 ` Das, Nirmoy
2023-03-08 9:41 ` [Intel-gfx] [PATCH v4 4/5] drm/i915: Create the locked version of the request add Andi Shyti
2023-03-08 9:41 ` [Intel-gfx] [PATCH v4 5/5] drm/i915/gt: Make sure that errors are propagated through request chains Andi Shyti
2023-03-10 10:03 ` Matthew Auld
2023-04-11 6:39 ` Das, Nirmoy
2023-04-11 14:35 ` Rodrigo Vivi
2023-04-12 10:56 ` Andi Shyti
2023-04-12 13:10 ` Rodrigo Vivi
2023-04-13 11:25 ` Tvrtko Ursulin
2023-03-08 11:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Fix error propagation amongst request (rev2) 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=3e306d18-de86-8903-2116-6443c26672ab@intel.com \
--to=andrzej.hajda@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maciej.patelczyk@intel.com \
--cc=matthew.auld@intel.com \
--cc=stable@vger.kernel.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