Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-18 Thread Christian König
Found and fixed. If nobody has any more objections are batter names for the new flags I'm going to push this to amd-staging-drm-next tomorrow. Thanks, Christian. Am 17.05.22 um 08:33 schrieb Christian König: Ok that sounds like a rather simple bug. I will try to take a look. Thanks,

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-17 Thread Christian König
Ok that sounds like a rather simple bug. I will try to take a look. Thanks, Christian. Am 17.05.22 um 02:12 schrieb Marek Olšák: Dmesg doesn't contain anything. There is no backtrace because it's not a crash. The VA map ioctl just fails with the new flag. It looks like the flag is considered

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Marek Olšák
Dmesg doesn't contain anything. There is no backtrace because it's not a crash. The VA map ioctl just fails with the new flag. It looks like the flag is considered invalid. Marek On Mon., May 16, 2022, 12:13 Christian König, < ckoenig.leichtzumer...@gmail.com> wrote: > I don't have access to

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Christian König
I don't have access to any gfx10 hardware. Can you give me a dmesg and/or backtrace, etc..? I can't push this unless it's working properly. Christian. Am 16.05.22 um 14:56 schrieb Marek Olšák: Reproduction steps: - use mesa/main on gfx10.3 (not sure what other GPUs do) - run:

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Marek Olšák
Reproduction steps: - use mesa/main on gfx10.3 (not sure what other GPUs do) - run: radeonsi_mall_noalloc=true glxgears Marek On Mon, May 16, 2022 at 7:53 AM Christian König < ckoenig.leichtzumer...@gmail.com> wrote: > Crap, do you have a link to the failure? > > Am 16.05.22 um 13:10 schrieb

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Christian König
Crap, do you have a link to the failure? Am 16.05.22 um 13:10 schrieb Marek Olšák: I forgot to say: The NOALLOC flag causes an allocation failure, so there is a kernel bug somewhere. Marek On Mon, May 16, 2022 at 7:06 AM Marek Olšák wrote: FYI, I think it's time to merge this because

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Marek Olšák
I forgot to say: The NOALLOC flag causes an allocation failure, so there is a kernel bug somewhere. Marek On Mon, May 16, 2022 at 7:06 AM Marek Olšák wrote: > FYI, I think it's time to merge this because the Mesa commits are going to > be merged in ~30 minutes if Gitlab CI is green, and that

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-16 Thread Marek Olšák
FYI, I think it's time to merge this because the Mesa commits are going to be merged in ~30 minutes if Gitlab CI is green, and that includes updated amdgpu_drm.h. Marek On Wed, May 11, 2022 at 2:55 PM Marek Olšák wrote: > Ok sounds good. > > Marek > > On Wed., May 11, 2022, 03:43 Christian

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-11 Thread Marek Olšák
Ok sounds good. Marek On Wed., May 11, 2022, 03:43 Christian König, < ckoenig.leichtzumer...@gmail.com> wrote: > It really *is* a NOALLOC feature. In other words there is no latency > improvement on reads because the cache is always checked, even with the > noalloc flag set. > > The only thing

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-11 Thread Christian König
It really *is* a NOALLOC feature. In other words there is no latency improvement on reads because the cache is always checked, even with the noalloc flag set. The only thing it affects is that misses not enter the cache and so don't cause any additional pressure on evicting cache lines. You

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-11 Thread Marek Olšák
Bypass means that the contents of the cache are ignored, which decreases latency at the cost of no coherency between bypassed and normal memory requests. NOA (noalloc) means that the cache is checked and can give you cache hits, but misses are not cached and the overall latency is higher. I don't

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-11 Thread Lazar, Lijo
On 5/11/2022 11:36 AM, Christian König wrote: Mhm, it doesn't really bypass MALL. It just doesn't allocate any MALL entries on write. How about AMDGPU_VM_PAGE_NO_MALL ? One more - AMDGPU_VM_PAGE_LLC_* [ LLC = last level cache, * = some sort of attribute which decides LLC behaviour]

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-11 Thread Christian König
Mhm, it doesn't really bypass MALL. It just doesn't allocate any MALL entries on write. How about AMDGPU_VM_PAGE_NO_MALL ? Christian. Am 10.05.22 um 23:21 schrieb Marek Olšák: A better name would be: AMDGPU_VM_PAGE_BYPASS_MALL Marek On Fri, May 6, 2022 at 7:23 AM Christian König wrote:

Re: [PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-10 Thread Marek Olšák
A better name would be: AMDGPU_VM_PAGE_BYPASS_MALL Marek On Fri, May 6, 2022 at 7:23 AM Christian König < ckoenig.leichtzumer...@gmail.com> wrote: > Add the AMDGPU_VM_NOALLOC flag to let userspace control MALL allocation. > > Only compile tested! > > Signed-off-by: Christian König > --- >

[PATCH 2/3] drm/amdgpu: add AMDGPU_VM_NOALLOC

2022-05-06 Thread Christian König
Add the AMDGPU_VM_NOALLOC flag to let userspace control MALL allocation. Only compile tested! Signed-off-by: Christian König --- drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 2 ++ drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c | 3 +++ drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c | 3 +++