From: fei.yang@intel.com
To: intel-xe@lists.freedesktop.org
Cc: matthew.d.roper@intel.com
Subject: [Intel-xe] [PATCH 1/1] drm/xe: set PTE_AE for all platforms supporting it
Date: Wed, 27 Sep 2023 21:43:35 -0700 [thread overview]
Message-ID: <20230928044335.1474903-2-fei.yang@intel.com> (raw)
In-Reply-To: <20230928044335.1474903-1-fei.yang@intel.com>
From: Fei Yang <fei.yang@intel.com>
Atomic access is supported by PVC, and became a common feature for all
platforms starting from Xe2. To enable that XE_VMA_ATOMIC_PTE_BIT needs
to be set, then pte encode will eventually set PTE_AE for devmem.
Signed-off-by: Fei Yang <fei.yang@intel.com>
---
drivers/gpu/drm/xe/xe_vm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index beffbb1039d3..5f700c0d5ef9 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -897,7 +897,7 @@ static struct xe_vma *xe_vma_create(struct xe_vm *vm,
vma->tile_mask |= 0x1 << id;
}
- if (vm->xe->info.platform == XE_PVC)
+ if (vm->xe->info.platform == XE_PVC || GRAPHICS_VER(vm->xe) >= 20)
vma->gpuva.flags |= XE_VMA_ATOMIC_PTE_BIT;
if (bo) {
--
2.25.1
next prev parent reply other threads:[~2023-09-28 4:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 4:43 [Intel-xe] [PATCH 0/1] drm/xe: set PTE_AE for all platforms supporting it fei.yang
2023-09-28 4:43 ` fei.yang [this message]
2023-09-28 18:11 ` [Intel-xe] [PATCH 1/1] " Matt Roper
2023-09-29 6:05 ` Lucas De Marchi
2023-09-28 4:51 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-28 4:52 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-28 4:53 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-28 5:00 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-28 5:00 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-28 5:01 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-28 5:36 ` [Intel-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=20230928044335.1474903-2-fei.yang@intel.com \
--to=fei.yang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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