From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Danilo Krummrich <dakr@kernel.org>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: <intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
Brendan King <Brendan.King@imgtec.com>,
Matt Coster <matt.coster@imgtec.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Caterina Shablia <caterina.shablia@collabora.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v8 01/24] drm/gpuvm: Pass map arguments through a struct
Date: Wed, 20 Aug 2025 20:53:54 +0530 [thread overview]
Message-ID: <b5a948c9-9ba3-48a3-bd17-2e9ef650133d@intel.com> (raw)
In-Reply-To: <c1e58abf-fe9e-4a80-b742-aa35f0683db7@intel.com>
On 20-08-2025 18:34, Ghimiray, Himal Prasad wrote:
>
>
> On 20-08-2025 17:34, Danilo Krummrich wrote:
>> On Wed Aug 20, 2025 at 1:56 PM CEST, Boris Brezillon wrote:
>>> On Tue, 19 Aug 2025 03:27:30 +0530
>>> Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com> wrote:
>>>> +/**
>>>> + * struct drm_gpuvm_map_req - arguments passed to
>>>> drm_gpuvm_sm_map[_ops_create]()
>>>> + */
>>>> +struct drm_gpuvm_map_req {
>>>> + /**
>>>> + * @op_map: struct drm_gpuva_op_map
>>>
>>> Doc name doesn't match the field name.
>>>
>>>> + */
>>>> + struct drm_gpuva_op_map map;
>>>
>>> Nit: not convinced map is a good name for that field, given this is a
>>> map_req, so we now those are map-related arguments. I would probably
>>> go for 'op'.
>>
>> Indeed, thanks for catching this! I thought I was suggesting this name
>> in a
>> previous version too.
>
> True, somehow I misread your comment and changed it from op_map to map
> instead of op. Will fix it.
Patch is already in drm-tip. Sent a new patch with fixes tags to make
these changes.
https://lore.kernel.org/intel-xe/20250820152335.2899501-1-himal.prasad.ghimiray@intel.com/T/#u
Requesting for reviews.
>
> Thanks
>
>
next prev parent reply other threads:[~2025-08-20 15:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 21:57 [PATCH v8 00/24] MADVISE FOR XE Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 01/24] drm/gpuvm: Pass map arguments through a struct Himal Prasad Ghimiray
2025-08-19 8:26 ` Matt Coster
2025-08-20 11:56 ` Boris Brezillon
2025-08-20 12:04 ` Danilo Krummrich
2025-08-20 13:04 ` Ghimiray, Himal Prasad
2025-08-20 15:23 ` Ghimiray, Himal Prasad [this message]
2025-08-20 13:01 ` Ghimiray, Himal Prasad
2025-08-18 21:57 ` [PATCH v8 02/24] drm/gpuvm: Kill drm_gpuva_init() Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 03/24] drm/gpuvm: Introduce drm_gpuvm_madvise_ops_create Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 04/24] drm/xe/uapi: Add madvise interface Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 05/24] drm/xe/vm: Add attributes struct as member of vma Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 06/24] drm/xe/vma: Move pat_index to vma attributes Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 07/24] drm/xe/vma: Modify new_vma to accept struct xe_vma_mem_attr as parameter Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 08/24] drm/gpusvm: Make drm_gpusvm_for_each_* macros public Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 09/24] drm/xe/svm: Split system allocator vma incase of madvise call Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 10/24] drm/xe: Allow CPU address mirror VMA unbind with gpu bindings for madvise Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 11/24] drm/xe/svm: Add xe_svm_ranges_zap_ptes_in_range() for PTE zapping Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 12/24] drm/xe: Implement madvise ioctl for xe Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 13/24] drm/xe/svm: Add svm ranges migration policy on atomic access Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 14/24] drm/xe/madvise: Update migration policy based on preferred location Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 15/24] drm/xe/svm: Support DRM_XE_SVM_MEM_RANGE_ATTR_PAT memory attribute Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 16/24] drm/xe/uapi: Add flag for consulting madvise hints on svm prefetch Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 17/24] drm/xe/svm: Consult madvise preferred location in prefetch Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 18/24] drm/xe/bo: Add attributes field to xe_bo Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 19/24] drm/xe/bo: Update atomic_access attribute on madvise Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 20/24] drm/xe/madvise: Skip vma invalidation if mem attr are unchanged Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 21/24] drm/xe/vm: Add helper to check for default VMA memory attributes Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 22/24] drm/xe: Reset VMA attributes to default in SVM garbage collector Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 23/24] drm/xe: Enable madvise ioctl for xe Himal Prasad Ghimiray
2025-08-18 21:57 ` [PATCH v8 24/24] drm/xe/uapi: Add UAPI for querying VMA count and memory attributes Himal Prasad Ghimiray
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=b5a948c9-9ba3-48a3-bd17-2e9ef650133d@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=Brendan.King@imgtec.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=caterina.shablia@collabora.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matt.coster@imgtec.com \
--cc=matthew.brost@intel.com \
--cc=robin.clark@oss.qualcomm.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;
as well as URLs for NNTP newsgroup(s).