From: "Christian König" <christian.koenig@amd.com>
To: Felix Kuehling <felix.kuehling@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/amdgpu: Let KFD use more VMIDs on Arcturus
Date: Thu, 25 Jun 2020 17:38:10 +0200 [thread overview]
Message-ID: <841359ec-a1cd-7722-55e6-182b6e2b6578@amd.com> (raw)
In-Reply-To: <77c53962-fd2e-7004-76ab-aae4580a49b9@amd.com>
Am 25.06.20 um 17:15 schrieb Felix Kuehling:
> Am 2020-06-25 um 4:19 a.m. schrieb Christian König:
>> Am 25.06.20 um 05:18 schrieb Felix Kuehling:
>>> When there is no graphics support, KFD can use more of the VMIDs.
>>> Graphics
>>> VMIDs are only used for video decoding/encoding and post processing.
>>> With
>>> two VCE engines, there is no reason to reserve more than 2 VMIDs for
>>> that.
>> IIRC the expectation is that we still use the compute queues for post
>> processing and not the KFD.
>>
>> So we will need at least VMIDs for that as well.
> Correct. Post processing uses compute queues and VMIDs in the GFXHUB.
> VCE uses VMIDs in the MMHUB. I believe in Mesa they use the same VM
> context. So can't they share the same VMIDs?
Ah! Good point, But we still need at least 3 VMID when VMID reservation
is active.
I don't think you can go below this.
Regards,
Christian.
>
> Regards,
> Felix
>
>
>>> Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
>>> ---
>>> drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 11 ++++++++---
>>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
>>> b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
>>> index 6e10b42c57e5..3470929e5b8e 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
>>> @@ -1245,10 +1245,15 @@ static int gmc_v9_0_sw_init(void *handle)
>>> /*
>>> * number of VMs
>>> * VMID 0 is reserved for System
>>> - * amdgpu graphics/compute will use VMIDs 1-7
>>> - * amdkfd will use VMIDs 8-15
>>> + * amdgpu graphics/compute will use VMIDs 1..n-1
>>> + * amdkfd will use VMIDs n..15
>>> + *
>>> + * The first KFD VMID is 8 for GPUs with graphics, 3 for
>>> + * compute-only GPUs. On compute-only GPUs that leaves 2 VMIDs
>>> + * for video processing.
>>> */
>>> - adev->vm_manager.first_kfd_vmid = 8;
>>> + adev->vm_manager.first_kfd_vmid =
>>> + adev->asic_type == CHIP_ARCTURUS ? 3 : 8;
>>> amdgpu_vm_manager_init(adev);
>>>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-06-25 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 3:18 [PATCH 1/2] drm/amdgpu: Clean up KFD VMID assignment Felix Kuehling
2020-06-25 3:18 ` [PATCH 2/2] drm/amdgpu: Let KFD use more VMIDs on Arcturus Felix Kuehling
2020-06-25 8:19 ` Christian König
2020-06-25 15:15 ` Felix Kuehling
2020-06-25 15:38 ` Christian König [this message]
2020-06-25 15:43 ` Felix Kuehling
2020-06-25 15:50 ` Christian König
2020-06-25 15:58 ` Felix Kuehling
2020-06-25 16:01 ` Christian König
2020-06-25 20:39 ` Felix Kuehling
2020-06-26 6:57 ` Christian König
2020-06-25 8:18 ` [PATCH 1/2] drm/amdgpu: Clean up KFD VMID assignment Christian König
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=841359ec-a1cd-7722-55e6-182b6e2b6578@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@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;
as well as URLs for NNTP newsgroup(s).