From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 2/3] drm/xe/vf: Don't try to program MOCS if VF
Date: Fri, 5 Apr 2024 15:39:35 +0200 [thread overview]
Message-ID: <20240405133936.891-3-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20240405133936.891-1-michal.wajdeczko@intel.com>
VFs drivers don't have access to MOCS registers. It is a PF driver
responsibility to program MOCS according to the HW team guidelines.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_mocs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_mocs.c b/drivers/gpu/drm/xe/xe_mocs.c
index bff659d20062..d16fa64da881 100644
--- a/drivers/gpu/drm/xe/xe_mocs.c
+++ b/drivers/gpu/drm/xe/xe_mocs.c
@@ -568,6 +568,9 @@ void xe_mocs_init(struct xe_gt *gt)
flags = get_mocs_settings(gt_to_xe(gt), &table);
mocs_dbg(gt, "flag:0x%x\n", flags);
+ if (IS_SRIOV_VF(gt_to_xe(gt)))
+ return;
+
if (flags & HAS_GLOBAL_MOCS)
__init_mocs_table(gt, &table);
if (flags & HAS_LNCF_MOCS)
--
2.43.0
next prev parent reply other threads:[~2024-04-05 13:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 13:39 [PATCH 0/3] More VF tweaks Michal Wajdeczko
2024-04-05 13:39 ` [PATCH 1/3] drm/xe/vf: Don't emit access to Global HWSP if VF Michal Wajdeczko
2024-04-08 11:19 ` Piotr Piórkowski
2024-04-05 13:39 ` Michal Wajdeczko [this message]
2024-04-08 6:02 ` [PATCH 2/3] drm/xe/vf: Don't try to program MOCS " Ghimiray, Himal Prasad
2024-04-05 13:39 ` [PATCH 3/3] drm/xe/vf: Don't try to read legacy GuC MMIO notification " Michal Wajdeczko
2024-04-08 6:03 ` Ghimiray, Himal Prasad
2024-04-05 16:09 ` ✓ CI.Patch_applied: success for More VF tweaks Patchwork
2024-04-05 16:10 ` ✓ CI.checkpatch: " Patchwork
2024-04-05 16:12 ` ✓ CI.KUnit: " Patchwork
2024-04-05 16:24 ` ✓ CI.Build: " Patchwork
2024-04-05 16:27 ` ✓ CI.Hooks: " Patchwork
2024-04-05 16:29 ` ✓ CI.checksparse: " Patchwork
2024-04-05 17:06 ` ✓ CI.BAT: " Patchwork
2024-04-08 12:32 ` Michal Wajdeczko
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=20240405133936.891-3-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.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