Using the cached values has less latency for bare metal
and SR-IOV, and prevents reading back bogus values if the
engine is powergated.
v2: fix typo in tile idx calculation
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/vi.c | 117 +---
1 file cha
Alex Deucher wrote:
On Tue, Oct 11, 2016 at 7:48 PM, Andy Furniss wrote:
The boot vce/uvd issue is fixed in 4.9-wip now, so I can boot latest but -
The segfault on startx is still there.
Fixed in v2.
Yea, all OK now.
___
amd-gfx mailing list
amd
viewed-by: Alex Deucher
>>
>> :04 04 a8f2ca9290985991b3cc37cbeb902f060573fdbb
>> 2309b176a1d4ff9e59eaf25688b5db6eb9759dd0 M drivers
>>
>>
>>
>>
>> ________
>> From: amd-gfx on behalf of
>> StDenis, Tom
>> Sent: Tuesday, October 11, 2016 09:20
Grazvydas Ignotas wrote:
On Wed, Oct 12, 2016 at 2:48 AM, Andy Furniss wrote:
I still can't shutdown/reboot
as in https://bugs.freedesktop.org/show_bug.cgi?id=98200
which is fixed for radeon, but apparently not (for me at least) with amdgpu.
You probably need a951ed85abd46 that went to 4.8-f
On Wed, Oct 12, 2016 at 2:48 AM, Andy Furniss wrote:
>
> I still can't shutdown/reboot
> as in https://bugs.freedesktop.org/show_bug.cgi?id=98200
> which is fixed for radeon, but apparently not (for me at least) with amdgpu.
You probably need a951ed85abd46 that went to 4.8-fixes and is not part
o
Alexander
Subject: Re: [PATCH 4/4] drm/amdgpu: used cached gca values for vi_read_register
Hi Andy,
Ha, I'm 1 step away (that was my last bad commit) from determining that. I'll
finish up for formality sake but I suspect that is the bad one.
Cheers,
Tom
___
: Tuesday, October 11, 2016 09:20
To: Andy Furniss; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander
Subject: Re: [PATCH 4/4] drm/amdgpu: used cached gca values for vi_read_register
Hi Andy,
Ha, I'm 1 step away (that was my last bad commit) from determining that. I'll
finish up for
m; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander
Subject: Re: [PATCH 4/4] drm/amdgpu: used cached gca values for vi_read_register
StDenis, Tom wrote:
> Actually NAK that, I don't have the cache patch internally. So my Tonga
> crash is something else.
Yes, seems the boot fail starts with
patch.
Tom
From: amd-gfx on behalf of StDenis, Tom
Sent: Tuesday, October 11, 2016 08:11
To: Andy Furniss; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander
Subject: Re: [PATCH 4/4] drm/amdgpu: used cached gca values for vi_read_register
Yup, my Tonga s
ander
Subject: Re: [PATCH 4/4] drm/amdgpu: used cached gca values for vi_read_register
Yup, my Tonga system dies on modprobe with the tip of stg-4.7 this morning.
Tom
From: amd-gfx on behalf of Andy Furniss
Sent: Tuesday, October 11, 2016 08:07
To: Alex Deucher; am
/amdgpu: used cached gca values for vi_read_register
Alex Deucher wrote:
> Using the cached values has less latency for bare metal and SR-IOV,
> and prevents reading back bogus values if the engine is powergated.
I can't startx since this on r9285.
Seems there are further issues later
Alex Deucher wrote:
Using the cached values has less latency for bare metal and SR-IOV,
and prevents reading back bogus values if the engine is powergated.
I can't startx since this on r9285.
Seems there are further issues later in current 4.9-wip = I die on
driver load, will see if that's rel
Using the cached values has less latency for bare metal
and SR-IOV, and prevents reading back bogus values if the
engine is powergated.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/vi.c | 117 +---
1 file changed, 97 insertions(+), 20 deletions(-
13 matches
Mail list logo
