Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Brost,  Matthew" <matthew.brost@intel.com>,
	"maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"Auld, Matthew" <matthew.auld@intel.com>
Subject: Re: [PATCH 4/4] drm/xe: Add xe_tlb_inval structure
Date: Tue, 15 Jul 2025 21:25:29 +0000	[thread overview]
Message-ID: <ed84bf7cdefd1cd8445f451b7ab66812ad012c43.camel@intel.com> (raw)
In-Reply-To: <20250715212125.337195-5-stuart.summers@intel.com>

On Tue, 2025-07-15 at 21:21 +0000, stuartsummers wrote:
> From: Matthew Brost <matthew.brost@intel.com>
> 
> Extract TLB invalidation state into a structure to decouple TLB
> invalidations from the GT, allowing the structure to be embedded
> anywhere in the driver.
> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Stuart Summers <stuart.summers@intel.com>

Also makes sense to me as an incremental move to the tlb inval specific
encapsulation.

Reviewed-by: Stuart Summers <stuart.summers@intel.com>

Thanks,
Stuart

> ---
>  drivers/gpu/drm/xe/xe_gt_tlb_inval_types.h | 30
> ++++++++++++++++++++++
>  drivers/gpu/drm/xe/xe_gt_types.h           | 29 ++------------------
> -
>  2 files changed, 32 insertions(+), 27 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_inval_types.h
> b/drivers/gpu/drm/xe/xe_gt_tlb_inval_types.h
> index 919430359103..b998276dd931 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_inval_types.h
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_inval_types.h
> @@ -6,10 +6,40 @@
>  #ifndef _XE_GT_TLB_INVAL_TYPES_H_
>  #define _XE_GT_TLB_INVAL_TYPES_H_
>  
> +#include <linux/workqueue.h>
>  #include <linux/dma-fence.h>
>  
>  struct xe_gt;
>  
> +/** struct xe_tlb_inval - TLB invalidation client */
> +struct xe_tlb_inval {
> +       /** @tlb_inval.seqno: TLB invalidation seqno, protected by CT
> lock */
> +#define TLB_INVALIDATION_SEQNO_MAX     0x100000
> +       int seqno;
> +       /**
> +        * @tlb_inval.seqno_recv: last received TLB invalidation
> seqno,
> +        * protected by CT lock
> +        */
> +       int seqno_recv;
> +       /**
> +        * @tlb_inval.pending_fences: list of pending fences waiting
> TLB
> +        * invaliations, protected by CT lock
> +        */
> +       struct list_head pending_fences;
> +       /**
> +        * @tlb_inval.pending_lock: protects
> @tlb_inval.pending_fences
> +        * and updating @tlb_inval.seqno_recv.
> +        */
> +       spinlock_t pending_lock;
> +       /**
> +        * @tlb_inval.fence_tdr: schedules a delayed call to
> +        * xe_gt_tlb_fence_timeout after the timeut interval is over.
> +        */
> +       struct delayed_work fence_tdr;
> +       /** @tlb_inval.lock: protects TLB invalidation fences */
> +       spinlock_t lock;
> +};
> +
>  /**
>   * struct xe_gt_tlb_inval_fence - XE GT TLB invalidation fence
>   *
> diff --git a/drivers/gpu/drm/xe/xe_gt_types.h
> b/drivers/gpu/drm/xe/xe_gt_types.h
> index b82795fc0070..ed21bd63b001 100644
> --- a/drivers/gpu/drm/xe/xe_gt_types.h
> +++ b/drivers/gpu/drm/xe/xe_gt_types.h
> @@ -12,6 +12,7 @@
>  #include "xe_gt_sriov_pf_types.h"
>  #include "xe_gt_sriov_vf_types.h"
>  #include "xe_gt_stats_types.h"
> +#include "xe_gt_tlb_inval_types.h"
>  #include "xe_hw_engine_types.h"
>  #include "xe_hw_fence_types.h"
>  #include "xe_oa_types.h"
> @@ -186,33 +187,7 @@ struct xe_gt {
>         } reset;
>  
>         /** @tlb_inval: TLB invalidation state */
> -       struct {
> -               /** @tlb_inval.seqno: TLB invalidation seqno,
> protected by CT lock */
> -#define TLB_INVALIDATION_SEQNO_MAX     0x100000
> -               int seqno;
> -               /**
> -                * @tlb_inval.seqno_recv: last received TLB
> invalidation seqno,
> -                * protected by CT lock
> -                */
> -               int seqno_recv;
> -               /**
> -                * @tlb_inval.pending_fences: list of pending fences
> waiting TLB
> -                * invaliations, protected by CT lock
> -                */
> -               struct list_head pending_fences;
> -               /**
> -                * @tlb_inval.pending_lock: protects
> @tlb_inval.pending_fences
> -                * and updating @tlb_inval.seqno_recv.
> -                */
> -               spinlock_t pending_lock;
> -               /**
> -                * @tlb_inval.fence_tdr: schedules a delayed call to
> -                * xe_gt_tlb_fence_timeout after the timeut interval
> is over.
> -                */
> -               struct delayed_work fence_tdr;
> -               /** @tlb_inval.lock: protects TLB invalidation fences
> */
> -               spinlock_t lock;
> -       } tlb_inval;
> +       struct xe_tlb_inval tlb_inval;
>  
>         /**
>          * @ccs_mode: Number of compute engines enabled.


  reply	other threads:[~2025-07-15 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 21:21 [PATCH 0/4] Basic TLB inval refactor stuartsummers
2025-07-15 21:21 ` [PATCH 1/4] drm/xe: Explicitly mark migration queues with flag stuartsummers
2025-07-15 21:21 ` [PATCH 2/4] drm/xe: Remove unused GT TLB invalidation trace points stuartsummers
2025-07-15 21:21 ` [PATCH 3/4] drm/xe: s/tlb_invalidation/tlb_inval stuartsummers
2025-07-15 21:24   ` Summers, Stuart
2025-07-15 21:21 ` [PATCH 4/4] drm/xe: Add xe_tlb_inval structure stuartsummers
2025-07-15 21:25   ` Summers, Stuart [this message]
2025-07-15 21:26 ` [PATCH 0/4] Basic TLB inval refactor Summers, Stuart
2025-07-15 21:51 ` ✗ CI.checkpatch: warning for " Patchwork
2025-07-15 21:52 ` ✓ CI.KUnit: success " Patchwork
2025-07-16 10:06 ` ✗ Xe.CI.Full: 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=ed84bf7cdefd1cd8445f451b7ab66812ad012c43.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@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