From: Matthew Brost <matthew.brost@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/exec: Fix minor bug related to xe_sync_entry_cleanup
Date: Thu, 11 Jul 2024 20:50:34 +0000 [thread overview]
Message-ID: <ZpBFmnsstUpiuP7H@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240711204552.3724442-1-ashutosh.dixit@intel.com>
On Thu, Jul 11, 2024 at 01:45:52PM -0700, Ashutosh Dixit wrote:
> Increment num_syncs after xe_sync_entry_parse() is successful to ensure
> the xe_sync_entry_cleanup() logic under "err_syncs" label works correctly.
>
Patch LGTM. A couple of nits though.
Fixes tag?
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> drivers/gpu/drm/xe/xe_exec.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_exec.c b/drivers/gpu/drm/xe/xe_exec.c
> index 2d72cdec3a0b..95c0b21096f0 100644
> --- a/drivers/gpu/drm/xe/xe_exec.c
> +++ b/drivers/gpu/drm/xe/xe_exec.c
> @@ -156,8 +156,8 @@ int xe_exec_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
>
> vm = q->vm;
>
> - for (i = 0; i < args->num_syncs; i++) {
> - err = xe_sync_entry_parse(xe, xef, &syncs[num_syncs++],
> + for (i = 0; i < args->num_syncs; i++, num_syncs++) {
How about?
'for (num_syncs = 0; num_syncs < args->num_syncs; num_syncs++) {'
This is what we do in xe_vm.c.
Matt
> + err = xe_sync_entry_parse(xe, xef, &syncs[i],
> &syncs_user[i], SYNC_PARSE_FLAG_EXEC |
> (xe_vm_in_lr_mode(vm) ?
> SYNC_PARSE_FLAG_LR_MODE : 0));
> --
> 2.41.0
>
next prev parent reply other threads:[~2024-07-11 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 20:45 [PATCH] drm/xe/exec: Fix minor bug related to xe_sync_entry_cleanup Ashutosh Dixit
2024-07-11 20:50 ` Matthew Brost [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-11 20:48 Ashutosh Dixit
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=ZpBFmnsstUpiuP7H@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=ashutosh.dixit@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