From: "Huang, Honglei" <honghuan@amd.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: sima@ffwll.ch, rodrigo.vivi@intel.com,
thomas.hellstrom@linux.intel.com,
himal.prasad.ghimiray@intel.com, dakr@kernel.org,
intel-xe@lists.freedesktop.org, aliceryhl@google.com,
Alexander.Deucher@amd.com, Felix.Kuehling@amd.com,
Christian.Koenig@amd.com, Ray.Huang@amd.com, Junhua.Shen@amd.com,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] drm/gpusvm: move dma_addr allocation before the notifier lock
Date: Wed, 2 Sep 2026 14:21:19 +0800 [thread overview]
Message-ID: <5101ad21-aa02-40d6-877c-38ae13f3cf3b@amd.com> (raw)
In-Reply-To: <apcp/XJpPdG3jzPd@gsse-cloud1.jf.intel.com>
On 9/2/2026 3:39 AM, Matthew Brost wrote:
> On Tue, Sep 01, 2026 at 05:00:57PM +0800, Honglei Huang wrote:
>> The dma_addr allocation was in a lazy allocation flow, it needs unlock
>> and goto map_pages. The allocation only needs npages, so just do it
>> before taking the lock. Drop the map_pages label and the relock flow, so
>> the sequence becomes fault, allocate, then lock, validate, map and
>> unlock. No functional change intended.
>>
>> Signed-off-by: Honglei Huang <honghuan@amd.com>
>
> One follow up suggestion below - not blocker for merging this series.
> Feel free to implement this or at some point (we) Intel will get around
> to this.
Got it, you can give me RB after you are really satisfied. I can keep
modifying until you feel there are no problems.
>
> This patch is:
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
>
>> ---
>> drivers/gpu/drm/drm_gpusvm.c | 22 +++++++++-------------
>> 1 file changed, 9 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_gpusvm.c b/drivers/gpu/drm/drm_gpusvm.c
>> index a93eee7ddb9..b507de539e6 100644
>> --- a/drivers/gpu/drm/drm_gpusvm.c
>> +++ b/drivers/gpu/drm/drm_gpusvm.c
>> @@ -1516,10 +1516,18 @@ int drm_gpusvm_get_pages(struct drm_gpusvm *gpusvm,
>> if (err)
>> goto err_free;
>>
>> + if (!svm_pages->dma_addr) {
>> + svm_pages->dma_addr =
>> + kvzalloc_objs(*svm_pages->dma_addr, npages);
>
> One thing that isn't great about the current code is that, regardless of
> `npages`, the overwhelming majority of cases result in exactly one DMA
> mapping. As a result, we end up wasting a significant amount of memory.
> If an IOVA is allocated, we only ever need a single DMA mapping. Even
> without IOVA support (e.g., `iommu=off` or `iommu=pt`), a 2 MiB backing
> store implemented as a THP would still yield a single DMA mapping via
> `dma_map_page()`.
>
> Longer term, I'd like to do something like the structure changes below.
> We would still preallocate unless `npages == 1`, but if
> `drm_gpusvm_dma_map_pages()` finds exactly one DMA mapping, we could free
> `dma_addr`, store the `drm_pagemap_addr` in `inline_addr`, and set an
> `inline_dma_mapping` flag. This would save 8 KiB per page of
> `drm_gpusvm_pages` for every 2 MiB THP-backed allocation.
Makes sense, working on it to reduce memory waste.
>
> Then the final piece is teach drivers to understand 'inline_dma_mapping'
> in their iterators (xe_res_cursor.h in Xe) to correctly walk the
> dma-mapping.
Agreed, the important part is driver maybe miss this change and the
compiles still fine, maybe worth changing xe_res_first_dma() to take a
drm_gpusvm_pages instead of a bare pointer.
>
> Matt
>
> diff --git a/include/drm/drm_gpusvm.h b/include/drm/drm_gpusvm.h
> index b7d987bf76aa..73b7065610f0 100644
> --- a/include/drm/drm_gpusvm.h
> +++ b/include/drm/drm_gpusvm.h
> @@ -121,6 +121,7 @@ struct drm_gpusvm_pages_flags {
> u16 unmapped : 1;
> u16 has_devmem_pages : 1;
> u16 has_dma_mapping : 1;
> + u16 inline_dma_mapping : 1;
> };
> u16 __flags;
> };
> @@ -140,7 +141,10 @@ struct drm_gpusvm_pages_flags {
> */
> struct drm_gpusvm_pages {
> struct drm_device *drm;
> - struct drm_pagemap_addr *dma_addr;
> + union {
> + struct drm_pagemap_addr *dma_addr;
> + struct drm_pagemap_addr inline_addr;
> + };
> struct drm_pagemap *dpagemap;
> struct dma_iova_state state;
> unsigned long state_offset;
Will modify the code according to your suggestion.
Regards,
Honglei
>
>
>> + if (!svm_pages->dma_addr) {
>> + err = -ENOMEM;
>> + goto err_free;
>> + }
>> + }
>> +
>> *state = (struct dma_iova_state){};
>> svm_pages->state_offset = 0;
>>
>> -map_pages:
>> /*
>> * Perform all dma mappings under the notifier lock to not
>> * access freed pages. A notifier will either block on
>> @@ -1540,18 +1548,6 @@ int drm_gpusvm_get_pages(struct drm_gpusvm *gpusvm,
>> goto retry;
>> }
>>
>> - if (!svm_pages->dma_addr) {
>> - /* Unlock and restart mapping to allocate memory. */
>> - drm_gpusvm_notifier_unlock(gpusvm);
>> - svm_pages->dma_addr =
>> - kvzalloc_objs(*svm_pages->dma_addr, npages);
>> - if (!svm_pages->dma_addr) {
>> - err = -ENOMEM;
>> - goto err_free;
>> - }
>> - goto map_pages;
>> - }
>> -
>> zdd = NULL;
>> pagemap = NULL;
>> num_dma_mapped = 0;
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2026-09-02 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:00 [PATCH v2 0/4] drm/gpusvm: share one HMM fault across per-device DMA mappings Honglei Huang
2026-09-01 9:00 ` [PATCH v2 1/4] drm/gpusvm: move dma_addr allocation before the notifier lock Honglei Huang
2026-09-01 19:39 ` Matthew Brost
2026-09-02 6:21 ` Huang, Honglei [this message]
2026-09-01 9:00 ` [PATCH v2 2/4] drm/gpusvm: extract drm_gpusvm_dma_map_pages() helper Honglei Huang
2026-09-01 19:43 ` Matthew Brost
2026-09-02 6:22 ` Huang, Honglei
2026-09-01 9:00 ` [PATCH v2 3/4] drm/gpusvm: let drm_gpusvm_get_pages() map an array of pages Honglei Huang
2026-09-01 19:57 ` Matthew Brost
2026-09-02 6:39 ` Huang, Honglei
2026-09-01 9:01 ` [PATCH v2 4/4] drm/gpusvm: make the DMA mapping step in get_pages() optional Honglei Huang
2026-09-01 20:02 ` Matthew Brost
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=5101ad21-aa02-40d6-877c-38ae13f3cf3b@amd.com \
--to=honghuan@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Junhua.Shen@amd.com \
--cc=Ray.Huang@amd.com \
--cc=aliceryhl@google.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sima@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox