From: "Christian König" <christian.koenig@amd.com>
To: Yifan Zhang <yifan1.zhang@amd.com>,
amd-gfx@lists.freedesktop.org, "Sharma,
Shashank" <Shashank.Sharma@amd.com>
Cc: Alexander.Deucher@amd.com
Subject: Re: [PATCH 1/2] drm/amdgpu: change page_table_base_addr caculation in mes queue property
Date: Tue, 22 Aug 2023 13:49:11 +0200 [thread overview]
Message-ID: <ec741915-a0da-e3f2-ee98-bfe516fa4dc3@amd.com> (raw)
In-Reply-To: <20230822061724.3917603-1-yifan1.zhang@amd.com>
Am 22.08.23 um 08:17 schrieb Yifan Zhang:
> current method doesn't work for GTT domain page table, change
> it to support both VRAM and GTT domain.
>
> Signed-off-by: Yifan Zhang <yifan1.zhang@amd.com>
Of hand that looks like the right thing to do, one comment below.
With that fixed feel free to add my Acked-by, but Shashank should
probably take a look as well.
Thanks,
Christian.
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c | 6 ++----
> drivers/gpu/drm/amd/amdgpu/amdgpu_mes.h | 2 +-
> 2 files changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c
> index 10ce5557bb11..ee957f059786 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c
> @@ -259,7 +259,7 @@ int amdgpu_mes_create_process(struct amdgpu_device *adev, int pasid,
> process->vm = vm;
> process->pasid = pasid;
> process->process_quantum = adev->mes.default_process_quantum;
> - process->pd_gpu_addr = amdgpu_bo_gpu_offset(vm->root.bo);
> + process->pd_phys_addr = amdgpu_gmc_pd_addr(vm->root.bo);
>
> amdgpu_mes_unlock(&adev->mes);
> return 0;
> @@ -621,9 +621,7 @@ int amdgpu_mes_add_hw_queue(struct amdgpu_device *adev, int gang_id,
> /* add hw queue to mes */
> queue_input.process_id = gang->process->pasid;
>
> - queue_input.page_table_base_addr =
> - adev->vm_manager.vram_base_offset + gang->process->pd_gpu_addr -
> - adev->gmc.vram_start;
> + queue_input.page_table_base_addr =gang->process->pd_phys_addr;
>
> queue_input.process_va_start = 0;
> queue_input.process_va_end =
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.h
> index a27b424ffe00..e1c20e2453c7 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_mes.h
> @@ -140,7 +140,7 @@ struct amdgpu_mes {
> struct amdgpu_mes_process {
> int pasid;
> struct amdgpu_vm *vm;
> - uint64_t pd_gpu_addr;
> + uint64_t pd_phys_addr;
phys_addr for physical address is quite a bit misleading since this
isn't a physical address at all. It's actually using the PDE format.
The entry in the job structure is equally bad named because of
historical reasons.
Maybe a name like root_pde or something similar would be better.
Regards,
Christian.
> struct amdgpu_bo *proc_ctx_bo;
> uint64_t proc_ctx_gpu_addr;
> void *proc_ctx_cpu_ptr;
prev parent reply other threads:[~2023-08-22 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 6:17 [PATCH 1/2] drm/amdgpu: change page_table_base_addr caculation in mes queue property Yifan Zhang
2023-08-22 6:17 ` [PATCH 2/2] drm/amdgpu: Put page tables to GTT memory for APUs Yifan Zhang
2023-08-22 11:50 ` Christian König
2023-08-22 15:48 ` Alex Deucher
2023-08-22 11:49 ` Christian König [this message]
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=ec741915-a0da-e3f2-ee98-bfe516fa4dc3@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Shashank.Sharma@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=yifan1.zhang@amd.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