All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Brendan King" <Brendan.King@imgtec.com>,
	"Boris Brezillon" <bbrezillon@kernel.org>,
	"Caterina Shablia" <caterina.shablia@collabora.com>,
	"Rob Clark" <robin.clark@oss.qualcomm.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v7 01/24] drm/gpuvm: Pass map arguments through a struct
Date: Mon, 18 Aug 2025 19:27:34 +0200	[thread overview]
Message-ID: <DC5QAWS5QUG8.28DC0DJFT5S2X@kernel.org> (raw)
In-Reply-To: <20250814105950.2177480-2-himal.prasad.ghimiray@intel.com>

On Thu Aug 14, 2025 at 12:59 PM CEST, Himal Prasad Ghimiray wrote:
> From: Boris Brezillon <boris.brezillon@collabora.com>
>
> We are about to pass more arguments to drm_gpuvm_sm_map[_ops_create](),
> so, before we do that, let's pass arguments through a struct instead
> of changing each call site every time a new optional argument is added.
>
> v5
>  - Use drm_gpuva_op_map—same as drm_gpuvm_map_req
>  - Rebase changes for drm_gpuvm_sm_map_exec_lock()
>  - Fix kernel-docs
>
> v6
>  - Use drm_gpuvm_map_req (Danilo/Matt)
>
> v7
>  - change member name to map instead of op_map
>  - use local variable to minize the code changes in _sm_map

I know it's a thing in DRM, but I'd rather not have the version changes in the
commit message. Please move them below "---" or into the cover letter.

(No need to resend for this. :)

> Cc: Danilo Krummrich <dakr@kernel.org>
> Cc: Brendan King <Brendan.King@imgtec.com>
> Cc: Boris Brezillon <bbrezillon@kernel.org>
> Cc: Caterina Shablia <caterina.shablia@collabora.com>
> Cc: Rob Clark <robin.clark@oss.qualcomm.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: <dri-devel@lists.freedesktop.org>
> Co-developed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> Acked-by: Danilo Krummrich <dakr@kernel.org> #v4
> Reviewed-by: Matthew Brost <matthew.brost@intel.com> #v6

  reply	other threads:[~2025-08-18 17:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 10:59 [PATCH v7 00/24] MADVISE FOR XE Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 01/24] drm/gpuvm: Pass map arguments through a struct Himal Prasad Ghimiray
2025-08-18 17:27   ` Danilo Krummrich [this message]
2025-08-18 18:12     ` Ghimiray, Himal Prasad
2025-08-18 20:49   ` Rob Clark
2025-08-14 10:59 ` [PATCH v7 02/24] drm/gpuvm: Kill drm_gpuva_init() Himal Prasad Ghimiray
2025-08-14 14:08   ` Rob Clark
2025-08-18 17:29   ` Danilo Krummrich
2025-08-18 18:15     ` Ghimiray, Himal Prasad
2025-08-14 10:59 ` [PATCH v7 03/24] drm/gpuvm: Introduce drm_gpuvm_madvise_ops_create Himal Prasad Ghimiray
2025-08-18 17:32   ` Danilo Krummrich
2025-08-18 18:16     ` Ghimiray, Himal Prasad
2025-08-14 10:59 ` [PATCH v7 04/24] drm/xe/uapi: Add madvise interface Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 05/24] drm/xe/vm: Add attributes struct as member of vma Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 06/24] drm/xe/vma: Move pat_index to vma attributes Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 07/24] drm/xe/vma: Modify new_vma to accept struct xe_vma_mem_attr as parameter Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 08/24] drm/gpusvm: Make drm_gpusvm_for_each_* macros public Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 09/24] drm/xe/svm: Split system allocator vma incase of madvise call Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 10/24] drm/xe: Allow CPU address mirror VMA unbind with gpu bindings for madvise Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 11/24] drm/xe/svm: Add xe_svm_ranges_zap_ptes_in_range() for PTE zapping Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 12/24] drm/xe: Implement madvise ioctl for xe Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 13/24] drm/xe/svm: Add svm ranges migration policy on atomic access Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 14/24] drm/xe/madvise: Update migration policy based on preferred location Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 15/24] drm/xe/svm: Support DRM_XE_SVM_MEM_RANGE_ATTR_PAT memory attribute Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 16/24] drm/xe/uapi: Add flag for consulting madvise hints on svm prefetch Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 17/24] drm/xe/svm: Consult madvise preferred location in prefetch Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 18/24] drm/xe/bo: Add attributes field to xe_bo Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 19/24] drm/xe/bo: Update atomic_access attribute on madvise Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 20/24] drm/xe/madvise: Skip vma invalidation if mem attr are unchanged Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 21/24] drm/xe/vm: Add helper to check for default VMA memory attributes Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 22/24] drm/xe: Reset VMA attributes to default in SVM garbage collector Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 23/24] drm/xe: Enable madvise ioctl for xe Himal Prasad Ghimiray
2025-08-14 10:59 ` [PATCH v7 24/24] drm/xe/uapi: Add UAPI for querying VMA count and memory attributes Himal Prasad Ghimiray
2025-08-14 12:16 ` ✗ CI.checkpatch: warning for MADVISE FOR XE (rev7) Patchwork
2025-08-14 12:17 ` ✓ CI.KUnit: success " Patchwork
2025-08-14 12:35 ` ✗ CI.checksparse: warning " Patchwork
2025-08-14 13:23 ` ✓ Xe.CI.BAT: success " Patchwork
2025-08-14 15:33 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-14 19:01   ` Matthew Brost
2025-08-18 18:31 ` [PATCH v7 00/24] MADVISE FOR XE Ghimiray, Himal Prasad
2025-08-18 20:28 ` Rodrigo Vivi

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=DC5QAWS5QUG8.28DC0DJFT5S2X@kernel.org \
    --to=dakr@kernel.org \
    --cc=Brendan.King@imgtec.com \
    --cc=bbrezillon@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=caterina.shablia@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=thomas.hellstrom@linux.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.