From: Felix Kuehling <felix.kuehling@amd.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Alex Sierra" <alex.sierra@amd.com>,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: lower the VAs base offset to 8KB
Date: Mon, 8 Nov 2021 09:35:11 -0500 [thread overview]
Message-ID: <f97e6a35-ac4c-2ef5-5fd4-e83fa8832fdc@amd.com> (raw)
In-Reply-To: <7b2d01fc-1058-e92b-e30f-98a72701f274@gmail.com>
Am 2021-11-08 um 5:22 a.m. schrieb Christian König:
> Am 05.11.21 um 20:25 schrieb Alex Sierra:
>> The low 16MB of virtual address space are currently reserved for kernel
>> mode allocations mapped into user virtual address space. This causes
>> conflicts with HMM/SVM mappings at low virtual addresses. We tried to
>> move those kernel mode allocations to the upper half of the 64-bit
>> virtual address space for GFX9, which is naturally reserved for kernel
>> use. However, TBA (trap handler code) has problems to access addresses
>> in the high virtual space. We have decided to set this to 8KB of the
>> lower address space as a temporary fix, while investigate TBA address
>> problem. It is very unlikely for user space to map memory at this low
>> region.
>
> Unfortunately that is not correct. IIRC every program run inside wine
> maps something at the 16-64KiB addresses.
>
> Don't ask me what that stuff is good for, but we already ran into
> problems because of exactly that.
It's only a problem if the application tries to map that memory on the
GPU through the HMM/SVM API. As long as there is no conflict with GPU
mappings created by the application, the GPU can safely use those
addresses for its purposes.
Regards,
Felix
>
> Regards,
> Christian.
>
>>
>> Signed-off-by: Alex Sierra <alex.sierra@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c
>> b/drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c
>> index 2e86692def19..d1388896f9c1 100644
>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c
>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c
>> @@ -308,7 +308,7 @@
>> * 16MB are reserved for kernel use (CWSR trap handler and kernel IB
>> * for now).
>> */
>> -#define SVM_USER_BASE 0x1000000ull
>> +#define SVM_USER_BASE (u64)(KFD_CWSR_TBA_TMA_SIZE + 2*PAGE_SIZE)
>> #define SVM_CWSR_BASE (SVM_USER_BASE - KFD_CWSR_TBA_TMA_SIZE)
>> #define SVM_IB_BASE (SVM_CWSR_BASE - PAGE_SIZE)
>>
>
next prev parent reply other threads:[~2021-11-08 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 19:25 [PATCH] drm/amdkfd: lower the VAs base offset to 8KB Alex Sierra
2021-11-05 20:57 ` Felix Kuehling
2021-11-08 10:22 ` Christian König
2021-11-08 14:35 ` Felix Kuehling [this message]
2021-11-08 16:32 ` 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=f97e6a35-ac4c-2ef5-5fd4-e83fa8832fdc@amd.com \
--to=felix.kuehling@amd.com \
--cc=alex.sierra@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.