Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [Intel-xe] [PATCH v6 1/5] drm/xe/pat: trim the xelp PAT table
Date: Thu, 28 Sep 2023 11:05:39 +0100	[thread overview]
Message-ID: <20230928100537.392675-8-matthew.auld@intel.com> (raw)
In-Reply-To: <20230928100537.392675-7-matthew.auld@intel.com>

We don't seem to use the 4-7 pat indexes, even though they are defined
by the HW. In the next patch userspace will be able to directly set the
pat_index as part of vm_bind and we don't want to allow setting 4-7.
Simplest is to just ignore them here.

Suggested-by: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Pallavi Mishra <pallavi.mishra@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
---
 drivers/gpu/drm/xe/xe_pat.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_pat.c b/drivers/gpu/drm/xe/xe_pat.c
index 869aee64641f..36b79d675e54 100644
--- a/drivers/gpu/drm/xe/xe_pat.c
+++ b/drivers/gpu/drm/xe/xe_pat.c
@@ -42,10 +42,6 @@ static const u32 xelp_pat_table[] = {
 	[1] = XELP_PAT_WC,
 	[2] = XELP_PAT_WT,
 	[3] = XELP_PAT_UC,
-	[4] = XELP_PAT_WB,
-	[5] = XELP_PAT_WB,
-	[6] = XELP_PAT_WB,
-	[7] = XELP_PAT_WB,
 };
 
 static const u32 xehpc_pat_table[] = {
-- 
2.41.0


  reply	other threads:[~2023-09-28 10:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 10:05 [Intel-xe] [PATCH v6 0/5] PAT and cache coherency support Matthew Auld
2023-09-28 10:05 ` Matthew Auld [this message]
2023-09-28 13:04   ` [Intel-xe] [PATCH v6 1/5] drm/xe/pat: trim the xelp PAT table Lucas De Marchi
2023-09-28 16:38     ` Matt Roper
2023-09-28 16:41       ` Lucas De Marchi
2023-09-28 10:05 ` [Intel-xe] [PATCH v6 2/5] drm/xe: directly use pat_index for pte_encode Matthew Auld
2023-09-28 13:15   ` Lucas De Marchi
2023-09-29  7:41     ` Matthew Auld
2023-09-28 19:13   ` Matt Roper
2023-10-01 15:36   ` Mishra, Pallavi
2023-09-28 10:05 ` [Intel-xe] [PATCH v6 3/5] drm/xe/uapi: Add support for cache and coherency mode Matthew Auld
2023-09-28 19:32   ` Souza, Jose
2023-09-29  7:28     ` Matthew Auld
2023-09-29 14:00       ` Souza, Jose
2023-09-28 10:05 ` [Intel-xe] [PATCH v6 4/5] drm/xe/pat: annotate pat_index with " Matthew Auld
2023-10-01 15:33   ` Mishra, Pallavi
2023-09-28 10:05 ` [Intel-xe] [PATCH v6 5/5] drm/xe/uapi: support pat_index selection with vm_bind Matthew Auld
2023-09-28 10:18 ` [Intel-xe] ✓ CI.Patch_applied: success for PAT and cache coherency support (rev7) Patchwork
2023-09-28 10:18 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-28 10:19 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-28 10:26 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-28 10:27 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-28 10:28 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-28 11:02 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-28 19:40 ` [Intel-xe] [PATCH v6 0/5] PAT and cache coherency support Souza, Jose
2023-09-28 20:02   ` Souza, Jose
2023-09-29  7:29     ` Matthew Auld

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=20230928100537.392675-8-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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