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 3/4] drm/gpuva: Add drm_gpuva_for_each_op_reverse
Date: Thu, 31 Aug 2023 14:33:56 -0400 [thread overview]
Message-ID: <ZPDdFHCmB1TD2H+x@intel.com> (raw)
In-Reply-To: <20230831150048.1760018-4-matthew.brost@intel.com>
On Thu, Aug 31, 2023 at 08:00:47AM -0700, Matthew Brost wrote:
> Xe will make use of this, add helper to walk op list in reverse when
> unwinding GPUVA operations.
I'm no native, but I got confused here. Would it be better if we
change the order like:
Add a helper to walk op list in reverse. Xe will make use of this
when unwinding GPUVA operations.
with the msg changed:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
This is a patch that is likely better to be propagated with
Xe and not earlier with drm-misc. We will need an explicit ack
from Dave/Daniel on this.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> include/drm/drm_gpuva_mgr.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/drm/drm_gpuva_mgr.h b/include/drm/drm_gpuva_mgr.h
> index ed8d50200cc3..b2024ae19fd4 100644
> --- a/include/drm/drm_gpuva_mgr.h
> +++ b/include/drm/drm_gpuva_mgr.h
> @@ -557,6 +557,16 @@ struct drm_gpuva_ops {
> #define drm_gpuva_for_each_op_from_reverse(op, ops) \
> list_for_each_entry_from_reverse(op, &(ops)->list, entry)
>
> +/**
> + * drm_gpuva_for_each_op_reverse - iterator to walk over &drm_gpuva_ops in reverse
> + * @op: &drm_gpuva_op to assign in each iteration step
> + * @ops: &drm_gpuva_ops to walk
> + *
> + * This iterator walks over all ops within a given list of operations in reverse
> + */
> +#define drm_gpuva_for_each_op_reverse(op, ops) \
> + list_for_each_entry_reverse(op, &(ops)->list, entry)
> +
> /**
> * drm_gpuva_first_op() - returns the first &drm_gpuva_op from &drm_gpuva_ops
> * @ops: the &drm_gpuva_ops to get the fist &drm_gpuva_op from
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-08-31 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 15:00 [Intel-xe] [PATCH 0/4] Fix array of binds Matthew Brost
2023-08-31 15:00 ` [Intel-xe] [PATCH 1/4] drm/xe: Covert xe_vma_op_flags to BIT macros Matthew Brost
2023-08-31 18:26 ` Rodrigo Vivi
2023-08-31 15:00 ` [Intel-xe] [PATCH 2/4] drm/xe: Fixup unwind on VM ops errors Matthew Brost
2023-08-31 15:00 ` [Intel-xe] [PATCH 3/4] drm/gpuva: Add drm_gpuva_for_each_op_reverse Matthew Brost
2023-08-31 18:33 ` Rodrigo Vivi [this message]
2023-08-31 15:00 ` [Intel-xe] [PATCH 4/4] drm/xe: Fix array of binds Matthew Brost
2023-08-31 18:29 ` Rodrigo Vivi
2023-08-31 15:14 ` [Intel-xe] ✗ CI.Patch_applied: failure for Fix array of binds (rev2) 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=ZPDdFHCmB1TD2H+x@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.