From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: Signal out-syncs on VM binds if no operations
Date: Wed, 26 Jul 2023 14:57:59 -0400 [thread overview]
Message-ID: <ZMFst7HGWshO7/zh@intel.com> (raw)
In-Reply-To: <20230726164624.358822-1-matthew.brost@intel.com>
On Wed, Jul 26, 2023 at 09:46:24AM -0700, Matthew Brost wrote:
> If no operations are generated for VM binds the out-syncs must still be
> signaled.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_vm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 6429d6e5113d..ddb1b4af6458 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -3374,6 +3374,8 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
> unwind_ops:
> vm_bind_ioctl_ops_unwind(vm, ops, args->num_binds);
> free_syncs:
> + for (i = 0; err == -ENODATA && i < num_syncs; i++)
> + xe_sync_entry_signal(&syncs[i], NULL, dma_fence_get_stub());
after offline chat and after carefully checking all the possible
cases where err == -ENODATA,
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> while (num_syncs--)
> xe_sync_entry_cleanup(&syncs[num_syncs]);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-26 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 16:46 [Intel-xe] [PATCH] drm/xe: Signal out-syncs on VM binds if no operations Matthew Brost
2023-07-26 18:57 ` Rodrigo Vivi [this message]
2023-07-26 19:33 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-07-26 19:33 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-07-26 19:34 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-07-26 19:38 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-26 19:38 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-26 19:40 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-26 20:14 ` [Intel-xe] ○ CI.BAT: info " 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=ZMFst7HGWshO7/zh@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.