From: "Welty, Brian" <brian.welty@intel.com>
To: "Chang, Bruce" <yu.bruce.chang@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Stuart Summers <stuart.summers@intel.com>
Subject: Re: [Intel-xe] [PATCH] drm/xe: Enable scratch page when page fault is enabled
Date: Tue, 29 Aug 2023 16:58:35 -0700 [thread overview]
Message-ID: <c352ecfe-3b68-72ad-2879-ca053be8201a@intel.com> (raw)
In-Reply-To: <20230829231648.4438-1-yu.bruce.chang@intel.com>
On 8/29/2023 4:16 PM, Chang, Bruce wrote:
> The PVC HW has a limitation that the page fault due to invalid access
> will halt the corresponding EUs. So, in order to activate the debugger,
> kmd needs to setup the scratch pages to unhalt the EUs.
>
> This feature can only be enabled if scratch flag is set per VM. So, once
> EU debugger is running, the debugger umd will set the scratch flag,
> otherwise, this flag should not be set. So, in regular run, this feature
> will not be activated.
>
> The idea is to bind a scratch vma if the page fault is from an
> invalid access. This patch is taking advantage of null pte.
> After the bind, the user app can continue to run without causing a
> fatal failure or reset and stop.
>
> In case the app will bind this scratch vma to a valid address, GPUVA
> handles all of this (e.g. it will create ops to unbind the old
> VMA, bind the new one).
>
> This patch only kicks in when there is a failure for both page fault
> and bind, so it should have no impact to regular code path. On
> another hand, it uses actual page tables instead of special scratch
> page tables, so it may not require to invalidate TLBs when doing
> unbind if all upper layer page tables are still being used.
>
> tested on new scratch igt tests which will be sent out for review.
>
> v2: per Matt's suggestion, remove the scratch page unbind.
>
> Cc: Oak Zeng <oak.zeng@intel.com>
> Cc: Brian Welty <brian.welty@intel.com>
> Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Cc: Stuart Summers <stuart.summers@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_pagefault.c | 9 +++++++--
> drivers/gpu/drm/xe/xe_vm.c | 24 +++++++++++++++++++-----
> drivers/gpu/drm/xe/xe_vm.h | 2 ++
> 3 files changed, 28 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_pagefault.c b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> index b6f781b3d9d7..adfd2206b942 100644
> --- a/drivers/gpu/drm/xe/xe_gt_pagefault.c
> +++ b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> @@ -137,8 +137,13 @@ static int handle_pagefault(struct xe_gt *gt, struct pagefault *pf)
> write_locked = true;
> vma = lookup_vma(vm, pf->page_addr);
> if (!vma) {
> - ret = -EINVAL;
> - goto unlock_vm;
> + if (vm->flags & XE_VM_FLAG_SCRATCH_PAGE)
> + vma = xe_vm_create_scratch_vma(vm, pf->page_addr);
> +
> + if (!vma) {
Looks like vma could have an embedded error. So maybe need
IS_ERR_OR_NULL() ?
> + ret = -EINVAL;
> + goto unlock_vm;
> + }
> }
>
> if (!xe_vma_is_userptr(vma) || !xe_vma_userptr_check_repin(vma)) {
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 389ac5ba8ddf..5190807089e8 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -1262,7 +1262,8 @@ struct xe_vm *xe_vm_create(struct xe_device *xe, u32 flags)
> }
> }
>
> - if (flags & XE_VM_FLAG_SCRATCH_PAGE) {
> + if (flags & XE_VM_FLAG_SCRATCH_PAGE &&
> + (!(flags & XE_VM_FLAG_FAULT_MODE))) {
> for_each_tile(tile, xe, id) {
> if (!vm->pt_root[id])
> continue;
> @@ -1998,10 +1999,6 @@ int xe_vm_create_ioctl(struct drm_device *dev, void *data,
> if (XE_IOCTL_DBG(xe, args->flags & ~ALL_DRM_XE_VM_CREATE_FLAGS))
> return -EINVAL;
>
> - if (XE_IOCTL_DBG(xe, args->flags & DRM_XE_VM_CREATE_SCRATCH_PAGE &&
> - args->flags & DRM_XE_VM_CREATE_FAULT_MODE))
> - return -EINVAL;
> -
> if (XE_IOCTL_DBG(xe, args->flags & DRM_XE_VM_CREATE_COMPUTE_MODE &&
> args->flags & DRM_XE_VM_CREATE_FAULT_MODE))
> return -EINVAL;
> @@ -2783,6 +2780,23 @@ static int __xe_vma_op_execute(struct xe_vm *vm, struct xe_vma *vma,
> return err;
> }
>
> +struct xe_vma *xe_vm_create_scratch_vma(struct xe_vm *vm, u64 addr)
> +{
> + struct xe_vma *vma = 0;
> +
> + if (xe_vm_is_closed_or_banned(vm))
> + return ERR_PTR(-ENOENT);
> +
> + vma = xe_vma_create(vm, NULL, 0, addr, addr + SZ_64K - 1, false, true, 0);
> + if (!vma)
> + return 0;
> + XE_WARN_ON(xe_vm_insert_vma(vm, vma));
I think might as well return the error to caller here?
(let the caller decide to ignore it or not).
And on error, seems best to call xe_vma_destroy_late() to free the
memory allocated for vma structure.
> +
> + /* fault will handle the bind */
> +
> + return vma;
> +}
> +
> static int xe_vma_op_execute(struct xe_vm *vm, struct xe_vma_op *op)
> {
> int ret = 0;
> diff --git a/drivers/gpu/drm/xe/xe_vm.h b/drivers/gpu/drm/xe/xe_vm.h
> index 6de6e3edb24a..ddd387333cd2 100644
> --- a/drivers/gpu/drm/xe/xe_vm.h
> +++ b/drivers/gpu/drm/xe/xe_vm.h
> @@ -212,6 +212,8 @@ int xe_vma_userptr_pin_pages(struct xe_vma *vma);
>
> int xe_vma_userptr_check_repin(struct xe_vma *vma);
>
> +struct xe_vma *xe_vm_create_scratch_vma(struct xe_vm *vm, u64 addr);
> +
> /*
> * XE_ONSTACK_TV is used to size the tv_onstack array that is input
> * to xe_vm_lock_dma_resv() and xe_vm_unlock_dma_resv().
next prev parent reply other threads:[~2023-08-29 23:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 23:16 [Intel-xe] [PATCH] drm/xe: Enable scratch page when page fault is enabled Chang, Bruce
2023-08-29 23:19 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Enable scratch page when page fault is enabled (rev3) Patchwork
2023-08-29 23:19 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-29 23:20 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-29 23:27 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-29 23:27 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-08-29 23:58 ` Welty, Brian [this message]
2023-08-30 21:37 ` [Intel-xe] [PATCH] drm/xe: Enable scratch page when page fault is enabled Chang, Yu bruce
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 21:34 Chang, Bruce
2023-09-01 0:31 ` Welty, Brian
2023-11-02 21:16 ` Summers, Stuart
2023-08-26 0:14 Chang, Bruce
2023-08-28 17:55 ` Summers, Stuart
2023-08-28 19:11 ` Chang, Yu bruce
2023-08-28 22:25 ` Summers, Stuart
2023-08-28 22:44 ` Chang, Yu bruce
2023-08-29 16:36 ` Summers, Stuart
2023-08-28 19:22 ` Matthew Brost
2023-08-28 22:34 ` Chang, Yu bruce
2023-08-28 23:44 ` Chang, Yu bruce
2023-07-10 22:06 Chang, Bruce
2023-07-11 2:11 ` Zeng, Oak
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=c352ecfe-3b68-72ad-2879-ca053be8201a@intel.com \
--to=brian.welty@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=stuart.summers@intel.com \
--cc=yu.bruce.chang@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