From: John Harrison <john.c.harrison@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: janusz.krzysztofik@intel.com, andi.shyti@intel.com,
matthew.d.roper@intel.com, saurabhg.gupta@intel.com,
chris.p.wilson@linux.intel.com, nirmoy.das@intel.com
Subject: Re: [Intel-gfx] [PATCH v13 4/7] drm/i915: No TLB invalidation on suspended GT
Date: Thu, 12 Oct 2023 18:08:11 -0700 [thread overview]
Message-ID: <fe011bb2-3377-4d96-a256-5434ff9319f0@intel.com> (raw)
In-Reply-To: <20231012223826.2556700-5-jonathan.cavitt@intel.com>
On 10/12/2023 15:38, Jonathan Cavitt wrote:
> In case of GT is suspended, don't allow submission of new TLB invalidation
> request and cancel all pending requests. The TLB entries will be
> invalidated either during GuC reload or on system resume.
>
> Signed-off-by: Fei Yang <fei.yang@intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> CC: John Harrison <john.c.harrison@intel.com>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> Acked-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Acked-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc.h | 1 +
> .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 22 ++++++++++++-------
> drivers/gpu/drm/i915/gt/uc/intel_uc.c | 7 ++++++
> 3 files changed, 22 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc.h b/drivers/gpu/drm/i915/gt/uc/intel_guc.h
> index 0949628d69f8b..2b6dfe62c8f2a 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc.h
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc.h
> @@ -537,4 +537,5 @@ int intel_guc_invalidate_tlb_engines(struct intel_guc *guc);
> int intel_guc_invalidate_tlb_guc(struct intel_guc *guc);
> int intel_guc_tlb_invalidation_done(struct intel_guc *guc,
> const u32 *payload, u32 len);
> +void wake_up_all_tlb_invalidate(struct intel_guc *guc);
> #endif
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 1377398afcdfa..3a0d20064878a 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -1796,13 +1796,24 @@ static void __guc_reset_context(struct intel_context *ce, intel_engine_mask_t st
> intel_context_put(parent);
> }
>
> -void intel_guc_submission_reset(struct intel_guc *guc, intel_engine_mask_t stalled)
> +void wake_up_all_tlb_invalidate(struct intel_guc *guc)
> {
> struct intel_guc_tlb_wait *wait;
> + unsigned long i;
> +
> + if (HAS_GUC_TLB_INVALIDATION(guc_to_gt(guc)->i915)) {
Why the change from 'if(!is_available) return' to 'if(HAS_) {doStuff}'?
John.
> + xa_lock_irq(&guc->tlb_lookup);
> + xa_for_each(&guc->tlb_lookup, i, wait)
> + wake_up(&wait->wq);
> + xa_unlock_irq(&guc->tlb_lookup);
> + }
> +}
> +
> +void intel_guc_submission_reset(struct intel_guc *guc, intel_engine_mask_t stalled)
> +{
> struct intel_context *ce;
> unsigned long index;
> unsigned long flags;
> - unsigned long i;
>
> if (unlikely(!guc_submission_initialized(guc))) {
> /* Reset called during driver load? GuC not yet initialised! */
> @@ -1833,12 +1844,7 @@ void intel_guc_submission_reset(struct intel_guc *guc, intel_engine_mask_t stall
> * The full GT reset will have cleared the TLB caches and flushed the
> * G2H message queue; we can release all the blocked waiters.
> */
> - if (HAS_GUC_TLB_INVALIDATION(guc_to_gt(guc)->i915)) {
> - xa_lock_irq(&guc->tlb_lookup);
> - xa_for_each(&guc->tlb_lookup, i, wait)
> - wake_up(&wait->wq);
> - xa_unlock_irq(&guc->tlb_lookup);
> - }
> + wake_up_all_tlb_invalidate(guc);
> }
>
> static void guc_cancel_context_requests(struct intel_context *ce)
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc.c b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> index 98b103375b7ab..27f6561dd7319 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> @@ -688,6 +688,8 @@ void intel_uc_suspend(struct intel_uc *uc)
> /* flush the GSC worker */
> intel_gsc_uc_flush_work(&uc->gsc);
>
> + wake_up_all_tlb_invalidate(guc);
> +
> if (!intel_guc_is_ready(guc)) {
> guc->interrupts.enabled = false;
> return;
> @@ -736,6 +738,11 @@ static int __uc_resume(struct intel_uc *uc, bool enable_communication)
>
> intel_gsc_uc_resume(&uc->gsc);
>
> + if (intel_guc_tlb_invalidation_is_available(guc)) {
> + intel_guc_invalidate_tlb_engines(guc);
> + intel_guc_invalidate_tlb_guc(guc);
> + }
> +
> return 0;
> }
>
next prev parent reply other threads:[~2023-10-13 1:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 22:38 [Intel-gfx] [PATCH v13 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 1/7] drm/i915: Add GuC TLB Invalidation device info flags Jonathan Cavitt
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 2/7] drm/i915/guc: Add CT size delay helper Jonathan Cavitt
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 3/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-13 1:10 ` John Harrison
2023-10-13 10:37 ` Andi Shyti
2023-10-13 14:52 ` Cavitt, Jonathan
2023-10-13 19:05 ` John Harrison
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 4/7] drm/i915: No TLB invalidation on suspended GT Jonathan Cavitt
2023-10-13 1:08 ` John Harrison [this message]
2023-10-13 10:49 ` Andi Shyti
2023-10-13 14:42 ` Cavitt, Jonathan
2023-10-13 19:12 ` John Harrison
2023-10-13 19:14 ` John Harrison
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 5/7] drm/i915: No TLB invalidation on wedged GT Jonathan Cavitt
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 6/7] drm/i915/gt: Increase sleep in gt_tlb selftest sanitycheck Jonathan Cavitt
2023-10-12 22:38 ` [Intel-gfx] [PATCH v13 7/7] drm/i915: Enable GuC TLB invalidations for MTL Jonathan Cavitt
2023-10-13 8:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines Patchwork
2023-10-13 8:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-13 8:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-14 8:51 ` [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=fe011bb2-3377-4d96-a256-5434ff9319f0@intel.com \
--to=john.c.harrison@intel.com \
--cc=andi.shyti@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nirmoy.das@intel.com \
--cc=saurabhg.gupta@intel.com \
/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