amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Christian König" <christian.koenig@amd.com>,
	amd-gfx@lists.freedesktop.org,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Alexandre Demers" <alexandre.f.demers@gmail.com>,
	"Rodrigo Siqueira" <siqueira@igalia.com>
Subject: Re: [PATCH 04/14] drm/amdgpu/gart: Add helper to bind VRAM BO
Date: Wed, 29 Oct 2025 11:57:47 +0100	[thread overview]
Message-ID: <15262eb50762bf09a6b85ed4d955f29ef98e8722.camel@gmail.com> (raw)
In-Reply-To: <4685c497-7e29-4245-9960-db572bdb83f9@amd.com>

On Wed, 2025-10-29 at 11:16 +0100, Christian König wrote:
> 
> 
> On 10/28/25 23:06, Timur Kristóf wrote:
> > Binds a BO that is allocated in VRAM to the GART page table.
> > 
> > Useful when a kernel BO is located in VRAM but
> > needs to be accessed from the GART address space,
> > for example to give a kernel BO a 32-bit address
> > when GART is placed in LOW address space.
> > 
> > Co-developed-by: Christian König <christian.koenig@amd.com>
> > Signed-off-by: Christian König <christian.koenig@amd.com>
> > Signed-off-by: Timur Kristóf <timur.kristof@gmail.com>
> > ---
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c | 41
> > ++++++++++++++++++++++++
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_gart.h |  2 ++
> >  2 files changed, 43 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
> > b/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
> > index 83f3b94ed975..19b5e72a6a26 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
> > @@ -390,6 +390,47 @@ void amdgpu_gart_bind(struct amdgpu_device
> > *adev, uint64_t offset,
> >  	amdgpu_gart_map(adev, offset, pages, dma_addr, flags,
> > adev->gart.ptr);
> >  }
> >  
> > +/**
> > + * amdgpu_gart_bind - bind VRAM BO into the GART page table
> 
> That should be the function name or otherwise you get automated
> warnings.

That's a copy paste mistake on my part. Thanks for catching that.

> 
> > + *
> > + * @adev: amdgpu_device pointer
> > + * @offset: offset into the GPU's gart aperture
> > + * @bo: the BO whose pages should be mapped
> > + * @flags: page table entry flags
> > + *
> > + * Binds a BO that is allocated in VRAM to the GART page table
> > + * (all ASICs).
> > + * Useful when a kernel BO is located in VRAM but
> > + * needs to be accessed from the GART address space,
> > + * for example to give a kernel BO a 32-bit address
> > + * when GART is placed in LOW address space.
> > + */
> > +void amdgpu_gart_bind_vram_bo(struct amdgpu_device *adev, uint64_t
> > offset,
> > +		     struct amdgpu_bo *bo, uint64_t flags)
> 
> Please not the BO but just the VRAM pa.

Sure, will do

> 
> > +{
> > +	u64 pa, bo_size;
> > +	u32 num_pages, start_page, i, idx;
> > +
> > +	if (!adev->gart.ptr)
> > +		return;
> > +
> > +	if (!drm_dev_enter(adev_to_drm(adev), &idx))
> > +		return;
> > +
> > +	pa = amdgpu_gmc_vram_pa(adev, bo);
> > +	bo_size = amdgpu_bo_size(bo);
> > +	num_pages = ALIGN(bo_size, AMDGPU_GPU_PAGE_SIZE) /
> > AMDGPU_GPU_PAGE_SIZE;
> > +	start_page = offset / AMDGPU_GPU_PAGE_SIZE;
> > +
> > +	for (i = 0; i < num_pages; ++i) {
> > +		amdgpu_gmc_set_pte_pde(adev, adev->gart.ptr,
> > +			start_page + i, pa + AMDGPU_GPU_PAGE_SIZE
> > * i, flags);
> > +	}
> > +
> 
> Ideally amdgpu_gart_map() should be able to take both dma_addr array
> or VRAM pa (or have two map functions).
> 
> This way we could cleanup the code in amdgpu_ttm_map_buffer as well.

Alright, I'll rework this new function so that it can be reused also by
amdgpu_ttm_map_buffer, does that sound alright to you?

> 
> 
> > +	amdgpu_gart_invalidate_tlb(adev);
> 
> IIRC we moved that out of amdgpu_gart_bind(), probably best to do so
> here as well.

Sure, will do

> 
> Regards,
> Christian.
> 
> > +	drm_dev_exit(idx);
> > +}
> > +
> >  /**
> >   * amdgpu_gart_invalidate_tlb - invalidate gart TLB
> >   *
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.h
> > b/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.h
> > index 7cc980bf4725..756548d0b520 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.h
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.h
> > @@ -64,5 +64,7 @@ void amdgpu_gart_map(struct amdgpu_device *adev,
> > uint64_t offset,
> >  		     void *dst);
> >  void amdgpu_gart_bind(struct amdgpu_device *adev, uint64_t offset,
> >  		      int pages, dma_addr_t *dma_addr, uint64_t
> > flags);
> > +void amdgpu_gart_bind_vram_bo(struct amdgpu_device *adev, uint64_t
> > offset,
> > +		     struct amdgpu_bo *bo, uint64_t flags);
> >  void amdgpu_gart_invalidate_tlb(struct amdgpu_device *adev);
> >  #endif

  reply	other threads:[~2025-10-29 10:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 22:06 [PATCH 00/14] drm/amdgpu: Support VCE1 IP block Timur Kristóf
2025-10-28 22:06 ` [PATCH 01/14] drm/amdgpu/gmc: Don't hardcode GART page count before GTT Timur Kristóf
2025-10-29 10:00   ` Christian König
2025-10-29 11:41     ` Timur Kristóf
2025-10-28 22:06 ` [PATCH 02/14] drm/amdgpu/gmc6: Place gart at low address range Timur Kristóf
2025-10-29 10:00   ` Christian König
2025-10-28 22:06 ` [PATCH 03/14] drm/amdgpu/gmc6: Add GART space for VCPU BO Timur Kristóf
2025-10-29 10:05   ` Christian König
2025-10-29 11:26     ` Timur Kristóf
2025-10-28 22:06 ` [PATCH 04/14] drm/amdgpu/gart: Add helper to bind VRAM BO Timur Kristóf
2025-10-29 10:16   ` Christian König
2025-10-29 10:57     ` Timur Kristóf [this message]
2025-10-28 22:06 ` [PATCH 05/14] drm/amdgpu/vce: Clear VCPU BO before copying firmware to it Timur Kristóf
2025-10-29 10:19   ` Christian König
2025-10-29 10:48     ` Timur Kristóf
2025-10-28 22:06 ` [PATCH 06/14] drm/amdgpu/vce: Move firmware load to amdgpu_vce_early_init Timur Kristóf
2025-10-29 10:26   ` Christian König
2025-10-29 17:16   ` Liu, Leo
2025-10-28 22:06 ` [PATCH 07/14] drm/amdgpu/si, cik, vi: Verify IP block when querying video codecs Timur Kristóf
2025-10-29 10:35   ` Christian König
2025-10-29 10:54     ` [PATCH 07/14] drm/amdgpu/si,cik,vi: " Timur Kristóf
2025-10-28 22:06 ` [PATCH 08/14] drm/amdgpu/vce1: Clean up register definitions Timur Kristóf
2025-10-29 11:23   ` Christian König
2025-10-28 22:06 ` [PATCH 09/14] drm/amdgpu/vce1: Load VCE1 firmware Timur Kristóf
2025-10-29 11:28   ` Christian König
2025-10-28 22:06 ` [PATCH 10/14] drm/amdgpu/vce1: Implement VCE1 IP block Timur Kristóf
2025-10-29 11:38   ` Christian König
2025-10-29 22:48     ` Timur Kristóf
2025-10-30 11:12       ` Christian König
2025-10-30 13:47         ` Timur Kristóf
2025-10-30 13:56           ` Christian König
2025-10-28 22:06 ` [PATCH 11/14] drm/amdgpu/vce1: Ensure VCPU BO is in lower 32-bit address space Timur Kristóf
2025-10-29 11:41   ` Christian König
2025-10-28 22:06 ` [PATCH 12/14] drm/amd/pm/si: Hook up VCE1 to SI DPM Timur Kristóf
2025-10-29 11:47   ` Christian König
2025-10-28 22:06 ` [PATCH 13/14] drm/amdgpu/vce1: Enable VCE1 on Tahiti, Pitcairn, Cape Verde GPUs Timur Kristóf
2025-10-29 11:51   ` Christian König
2025-10-28 22:06 ` [PATCH 14/14] drm/amdgpu/vce1: Tolerate VCE PLL timeout better Timur Kristóf
2025-10-29 12:02   ` Christian König
2025-10-29 19:46     ` Deucher, Alexander
2025-11-03 16:01       ` timur.kristof

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=15262eb50762bf09a6b85ed4d955f29ef98e8722.camel@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexandre.f.demers@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=siqueira@igalia.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).