From: Matthew Brost <matthew.brost@intel.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>
Cc: <dri-devel@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v1 5/5] drm/xe/pt: Add an additional check for dmabuf BOs while updating PTEs
Date: Sun, 20 Oct 2024 18:25:11 +0000 [thread overview]
Message-ID: <ZxVLB/71cImZTRhl@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20241012024524.1377836-6-vivek.kasireddy@intel.com>
On Fri, Oct 11, 2024 at 07:40:27PM -0700, Vivek Kasireddy wrote:
> If a BO's is_devmem_external flag is set, it means that it is an
> imported dmabuf BO that has a backing store in VRAM. Therefore, we
> need to add XE_PPGTT_PTE_DM to the PTE flags as part of vm_bind.
>
So here if we land on a DPA cursor [1] we'd have to update the bind code
to use this cursor. Again I think this is my preference.
Matt
[1] https://patchwork.freedesktop.org/patch/619451/?series=139920&rev=1#comment_1127450
> Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pt.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> index f27f579f4d85..909e5b96d518 100644
> --- a/drivers/gpu/drm/xe/xe_pt.c
> +++ b/drivers/gpu/drm/xe/xe_pt.c
> @@ -660,10 +660,11 @@ xe_pt_stage_bind(struct xe_tile *tile, struct xe_vma *vma,
> xe_walk.default_pte &= ~XE_USM_PPGTT_PTE_AE;
> }
>
> - if (is_devmem) {
> + if (is_devmem || bo->is_devmem_external)
> xe_walk.default_pte |= XE_PPGTT_PTE_DM;
> +
> + if (is_devmem)
> xe_walk.dma_offset = vram_region_gpu_offset(bo->ttm.resource);
> - }
>
> if (!xe_vma_has_no_bo(vma) && xe_bo_is_stolen(bo))
> xe_walk.dma_offset = xe_ttm_stolen_gpu_offset(xe_bo_device(bo));
> --
> 2.45.1
>
next prev parent reply other threads:[~2024-10-20 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 2:40 [PATCH v1 0/5] drm/xe/sriov: Don't migrate dmabuf BO to System RAM while running in VM Vivek Kasireddy
2024-10-12 2:40 ` [PATCH v1 1/5] PCI/P2PDMA: Don't enforce ACS check for functions of same device Vivek Kasireddy
2024-10-15 17:45 ` Logan Gunthorpe
2024-10-16 5:29 ` Kasireddy, Vivek
2024-10-16 19:29 ` Logan Gunthorpe
2024-10-12 2:40 ` [PATCH v1 2/5] drm/xe/dmabuf: Don't migrate BO to System RAM while running in VF mode Vivek Kasireddy
2024-10-12 2:40 ` [PATCH v1 3/5] drm/xe/pf: Add a helper function to get a VF's starting address in LMEM Vivek Kasireddy
2024-10-12 2:40 ` [PATCH v1 4/5] drm/xe/bo: Create a new sg for dmabuf BOs that are associated with a VF Vivek Kasireddy
2024-10-12 4:17 ` Matthew Brost
2024-10-16 5:41 ` Kasireddy, Vivek
2024-10-20 18:06 ` Matthew Brost
2024-10-12 2:40 ` [PATCH v1 5/5] drm/xe/pt: Add an additional check for dmabuf BOs while updating PTEs Vivek Kasireddy
2024-10-20 18:25 ` Matthew Brost [this message]
2024-10-12 3:16 ` ✓ CI.Patch_applied: success for drm/xe/sriov: Don't migrate dmabuf BO to System RAM while running in VM Patchwork
2024-10-12 3:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-12 3:18 ` ✓ CI.KUnit: success " Patchwork
2024-10-12 3:34 ` ✓ CI.Build: " Patchwork
2024-10-12 3:36 ` ✓ CI.Hooks: " Patchwork
2024-10-12 3:38 ` ✗ CI.checksparse: warning " Patchwork
2024-10-12 4:17 ` ✗ CI.BAT: failure " Patchwork
2024-10-12 9:27 ` ✗ CI.FULL: " 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=ZxVLB/71cImZTRhl@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=vivek.kasireddy@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