Re: [PATCH libdrm 3/4] amdgpu: use the high VA range if possible v2

2018-02-03 Thread Christian König
Hi Marek, it looks like the hardware sign extends bit 47 into bits 48-63. E.g. 0x8000 gets extended to 0x8000. Christian. Am 03.02.2018 um 03:02 schrieb Marek Olšák: Hi Christian, How does this work with 48-bit addresses that the 3D engine uses? It can't set 0x8000 for the high

Re: [PATCH libdrm 3/4] amdgpu: use the high VA range if possible v2

2018-01-08 Thread Marek Olšák
Actually, 0x8000 is fine. For the series: Reviewed-by: Marek Olšák Marek ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [PATCH libdrm 3/4] amdgpu: use the high VA range if possible v2

2018-01-08 Thread Marek Olšák
Can we put the 32-bit address space higher? E.g. high bits = 0xfff0 ? Marek On Sun, Jan 7, 2018 at 10:11 AM, Christian König wrote: > Retire the low range on Vega10 this frees up everything below > 0x8000 for HMM. > > v2: keep the 32bit range

[PATCH libdrm 3/4] amdgpu: use the high VA range if possible v2

2018-01-07 Thread Christian König
Retire the low range on Vega10 this frees up everything below 0x8000 for HMM. v2: keep the 32bit range working. Signed-off-by: Christian König --- amdgpu/amdgpu_device.c | 18 ++ 1 file changed, 14 insertions(+), 4 deletions(-) diff --git