From: Matthew Brost <matthew.brost@intel.com>
To: Stuart Summers <stuart.summers@intel.com>
Cc: <niranjana.vishwanathapura@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Add ASID to range invalidation feature flag
Date: Thu, 1 May 2025 13:40:45 -0700 [thread overview]
Message-ID: <aBPcTbopzpPCd6Ly@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250501173626.64481-1-stuart.summers@intel.com>
On Thu, May 01, 2025 at 05:36:26PM +0000, Stuart Summers wrote:
> Make it explicit that the ASID is used to identify a VM
> when issuing a ranged-based TLB invalidation.
>
> /s/has_range_tlb_invalidation/has_range_tlb_invalidation_asid/
>
> Signed-off-by: Stuart Summers <stuart.summers@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device_types.h | 4 ++--
> drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 2 +-
> drivers/gpu/drm/xe/xe_pci.c | 6 +++---
> drivers/gpu/drm/xe/xe_pci_types.h | 2 +-
> 4 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
> index 06c65dace026..3e49b88a8a62 100644
> --- a/drivers/gpu/drm/xe/xe_device_types.h
> +++ b/drivers/gpu/drm/xe/xe_device_types.h
> @@ -327,8 +327,8 @@ struct xe_device {
> u8 has_llc:1;
> /** @info.has_pxp: Device has PXP support */
> u8 has_pxp:1;
> - /** @info.has_range_tlb_invalidation: Has range based TLB invalidations */
> - u8 has_range_tlb_invalidation:1;
> + /** @info.has_range_tlb_invalidation_asid: Has range based TLB invalidations */
> + u8 has_range_tlb_invalidation_asid:1;
> /** @info.has_sriov: Supports SR-IOV */
> u8 has_sriov:1;
> /** @info.has_usm: Device has unified shared memory support */
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> index 084cbdeba8ea..c68f7cc8e175 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> @@ -366,7 +366,7 @@ int xe_gt_tlb_invalidation_range(struct xe_gt *gt,
>
> action[len++] = XE_GUC_ACTION_TLB_INVALIDATION;
> action[len++] = 0; /* seqno, replaced in send_tlb_invalidation */
> - if (!xe->info.has_range_tlb_invalidation ||
> + if (!xe->info.has_range_tlb_invalidation_asid ||
> length > MAX_RANGE_TLB_INVALIDATION_LENGTH) {
> action[len++] = MAKE_INVAL_OP(XE_GUC_TLB_INVAL_FULL);
> } else {
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index a4caa6222b6f..cfafcfcbbbc6 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -91,7 +91,7 @@ static const struct xe_graphics_desc graphics_xelp = {
> };
>
> #define XE_HP_FEATURES \
> - .has_range_tlb_invalidation = true, \
> + .has_range_tlb_invalidation_asid = true, \
> .va_bits = 48, \
> .vm_max_level = 3
>
> @@ -140,7 +140,7 @@ static const struct xe_graphics_desc graphics_xelpg = {
> .has_atomic_enable_pte_bit = 1, \
> .has_flat_ccs = 1, \
> .has_indirect_ring_state = 1, \
> - .has_range_tlb_invalidation = 1, \
> + .has_range_tlb_invalidation_asid = 1, \
> .has_usm = 1, \
> .va_bits = 48, \
> .vm_max_level = 4, \
> @@ -680,7 +680,7 @@ static int xe_info_init(struct xe_device *xe,
> /* Runtime detection may change this later */
> xe->info.has_flat_ccs = graphics_desc->has_flat_ccs;
>
> - xe->info.has_range_tlb_invalidation = graphics_desc->has_range_tlb_invalidation;
> + xe->info.has_range_tlb_invalidation_asid = graphics_desc->has_range_tlb_invalidation_asid;
> xe->info.has_usm = graphics_desc->has_usm;
>
> for_each_remote_tile(tile, xe, id) {
> diff --git a/drivers/gpu/drm/xe/xe_pci_types.h b/drivers/gpu/drm/xe/xe_pci_types.h
> index e9b9bbc138d3..3d1c745de2ac 100644
> --- a/drivers/gpu/drm/xe/xe_pci_types.h
> +++ b/drivers/gpu/drm/xe/xe_pci_types.h
> @@ -19,7 +19,7 @@ struct xe_graphics_desc {
> u8 has_atomic_enable_pte_bit:1;
> u8 has_flat_ccs:1;
> u8 has_indirect_ring_state:1;
> - u8 has_range_tlb_invalidation:1;
> + u8 has_range_tlb_invalidation_asid:1;
> u8 has_usm:1;
> };
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-05-01 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 17:36 [PATCH] drm/xe: Add ASID to range invalidation feature flag Stuart Summers
2025-05-01 17:42 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-01 17:42 ` ✓ CI.checkpatch: " Patchwork
2025-05-01 17:44 ` ✓ CI.KUnit: " Patchwork
2025-05-01 17:52 ` ✓ CI.Build: " Patchwork
2025-05-01 17:54 ` ✓ CI.Hooks: " Patchwork
2025-05-01 17:56 ` ✓ CI.checksparse: " Patchwork
2025-05-01 20:40 ` Matthew Brost [this message]
2025-05-01 20:50 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-01 21:41 ` [PATCH] " Cavitt, Jonathan
2025-05-06 7:56 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-06-03 8:49 ` [PATCH] " Upadhyay, Tejas
2025-06-03 17:10 ` Summers, Stuart
2025-06-04 10:17 ` Upadhyay, Tejas
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=aBPcTbopzpPCd6Ly@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@intel.com \
--cc=stuart.summers@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 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.