From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH 1/3] drm/xe/pf: Use explicit VRAM BO flag for VRAM provisioning
Date: Fri, 20 Feb 2026 21:18:53 +0100 [thread overview]
Message-ID: <20260220201857.6113-2-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20260220201857.6113-1-michal.wajdeczko@intel.com>
When we are about to provision VRAM/LMEM for VF, there is no point
in using semi-automatic flag that supports fallback to the SMEM.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
index cba20eb6b36b..6383763d02ab 100644
--- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
+++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
@@ -1652,7 +1652,7 @@ static int pf_provision_vf_lmem(struct xe_gt *gt, unsigned int vfid, u64 size)
bo = xe_bo_create_pin_range_novm(xe, tile,
ALIGN(size, PAGE_SIZE), 0, ~0ull,
ttm_bo_type_kernel,
- XE_BO_FLAG_VRAM_IF_DGFX(tile) |
+ XE_BO_FLAG_VRAM(tile->mem.vram) |
XE_BO_FLAG_NEEDS_2M |
XE_BO_FLAG_PINNED |
XE_BO_FLAG_PINNED_LATE_RESTORE |
--
2.47.1
next prev parent reply other threads:[~2026-02-20 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 20:18 [PATCH 0/3] drm/xe/pf: Some VRAM flag improvements Michal Wajdeczko
2026-02-20 20:18 ` Michal Wajdeczko [this message]
2026-02-20 23:07 ` [PATCH 1/3] drm/xe/pf: Use explicit VRAM BO flag for VRAM provisioning Matthew Brost
2026-02-20 20:18 ` [PATCH 2/3] drm/xe/pf: Don't use LMTT page size if no LMTT Michal Wajdeczko
2026-02-20 23:12 ` Matthew Brost
2026-02-20 20:18 ` [PATCH 3/3] drm/xe/pf: Don't force 2MB VRAM alignment Michal Wajdeczko
2026-02-20 23:11 ` Matthew Brost
2026-02-20 20:26 ` ✓ CI.KUnit: success for drm/xe/pf: Some VRAM flag improvements Patchwork
2026-02-20 21:07 ` ✓ Xe.CI.BAT: " 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=20260220201857.6113-2-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