AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Felix Kuehling" <felix.kuehling@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"YuBiao Wang" <YuBiao.Wang@amd.com>,
	amd-gfx@lists.freedesktop.org, "Sharma,
	Shashank" <Shashank.Sharma@amd.com>
Cc: Feifei Xu <Feifei.Xu@amd.com>,
	horace.chen@amd.com, Kevin Wang <Kevin1.Wang@amd.com>,
	Tuikov Luben <Luben.Tuikov@amd.com>,
	Deucher Alexander <Alexander.Deucher@amd.com>,
	Monk Liu <Monk.Liu@amd.com>,
	Hawking Zhang <Hawking.Zhang@amd.com>
Subject: Re: [PATCH] drm/amdkfd: Use gpu_offset for user queue's wptr
Date: Mon, 18 Sep 2023 10:23:00 +0200	[thread overview]
Message-ID: <535e3add-e885-3c88-6afe-8371e565e675@gmail.com> (raw)
In-Reply-To: <f82d33ef-3ace-0b74-04ab-9ce646dfb0bb@amd.com>

Am 15.09.23 um 16:53 schrieb Felix Kuehling:
> On 2023-09-15 2:50, Christian König wrote:
>> Am 15.09.23 um 04:52 schrieb YuBiao Wang:
>>> Directly use tbo's start address will miss the domain start offset. 
>>> Need
>>> to use gpu_offset instead.
>>>
>>> Signed-off-by: YuBiao Wang <YuBiao.Wang@amd.com>
>>
>> Felix and/or Shashank should probably take a look as well, but of 
>> hand that looks like the correct fix.
>
> Looks reasonable to me. Why did this not cause problems before? Are we 
> just lucky that the domain start offset is 0 on the GPUs we've tested 
> so far?

By coincident the GART ended up being placed at 0 before. Now Alex has 
to move it to work around other issues.

Regards,
Christian.

>
> Regards,
>   Felix
>
>
>>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>
>>> ---
>>>   drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c 
>>> b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
>>> index 77159b03a422..36e7171ad9a7 100644
>>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
>>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
>>> @@ -216,7 +216,7 @@ static int add_queue_mes(struct 
>>> device_queue_manager *dqm, struct queue *q,
>>>         if (q->wptr_bo) {
>>>           wptr_addr_off = (uint64_t)q->properties.write_ptr & 
>>> (PAGE_SIZE - 1);
>>> -        queue_input.wptr_mc_addr = 
>>> ((uint64_t)q->wptr_bo->tbo.resource->start << PAGE_SHIFT) + 
>>> wptr_addr_off;
>>> +        queue_input.wptr_mc_addr = amdgpu_bo_gpu_offset(q->wptr_bo) 
>>> + wptr_addr_off;
>>>       }
>>>         queue_input.is_kfd_process = 1;
>>


      parent reply	other threads:[~2023-09-18  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  2:52 [PATCH] drm/amdkfd: Use gpu_offset for user queue's wptr YuBiao Wang
2023-09-15  6:50 ` Christian König
2023-09-15 14:53   ` Felix Kuehling
2023-09-18  2:14     ` Wang, YuBiao
2023-09-18 16:11       ` Felix Kuehling
2023-09-18  8:23     ` 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=535e3add-e885-3c88-6afe-8371e565e675@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Feifei.Xu@amd.com \
    --cc=Hawking.Zhang@amd.com \
    --cc=Kevin1.Wang@amd.com \
    --cc=Luben.Tuikov@amd.com \
    --cc=Monk.Liu@amd.com \
    --cc=Shashank.Sharma@amd.com \
    --cc=YuBiao.Wang@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=felix.kuehling@amd.com \
    --cc=horace.chen@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