: Deucher, Alexander
Sent: 2018年3月9日 11:30
To: Liu, Monk ; Koenig, Christian ;
Mao, David
Cc: Jin, Jian-Rong ; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Can GIM read the value and pass it to the VF's via the vbios or the shared area?
*Cc:* Jin, Jian-Rong; amd-gfx@lists.freedesktop.org
*Subject:* RE: deprecated register issues
>Although KMD now use a cache way to give libdrm the
CC_RB_BACKEND_DISABLE value, but KMD still need to read it at least
one shot during loading driver right ?
Correct, but we do this while having
t: RE: deprecated register issues
> Although KMD now use a cache way to give libdrm the CC_RB_BACKEND_DISABLE
> value, but KMD still need to read it at least one shot during loading driver
> right ?
Correct, but we do this while having exclusive access.
The problem is although for VF0
Jian-Rong ; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Although KMD now use a cache way to give libdrm the CC_RB_BACKEND_DISABLE
value, but KMD still need to read it at least one shot during loading driver
right ?
Correct, but we do this while having exclusive access.
stian ; Deucher, Alexander
; Mao, David
*Cc:* Jin, Jian-Rong ;
amd-gfx@lists.freedesktop.org
*Subject:* RE: deprecated register issues
Yeah, I agree with you we’d better find all those registers
Stitch together the REQ and ACK part only avoid this issue for vm
flush only, and we may still hit the iss
From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Liu,
Monk
Sent: 2018年3月8日 18:03
To: Koenig, Christian ; Deucher, Alexander
; Mao, David
Cc: Jin, Jian-Rong ; amd-gfx@lists.freedesktop.org
Subject: RE: deprecated register issues
Yeah, I agree with you we’d better find all
reason to stand there.
any thought ?
/Monk
From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com]
Sent: 2018年3月8日 17:41
To: Liu, Monk ; Deucher, Alexander
; Koenig, Christian ; Mao,
David
Cc: Jin, Jian-Rong ; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Hi Monk
se, A.K.A use one
package for the REQ and ACK job
/Monk
*From:*Deucher, Alexander
*Sent:* 2018年3月8日10:53
*To:* Liu, Monk ; Koenig, Christian
; Mao, David
*Cc:* amd-gfx@lists.freedesktop.org; Jin, Jian-Rong
*Subject:* Re: deprecated register issues
I think there are more than just CC_RB_BA
op.org; Jin, Jian-Rong
Subject: Re: deprecated register issues
I think there are more than just CC_RB_BACKEND_DISABLE that could cause this
problem. IIRC, some entire class of gfx registers could cause it, it just
happened that this was one of the only ones we readback via mmio. Also for the
; Mao, David
; Liu, Monk
Cc: amd-gfx@lists.freedesktop.org; Jin, Jian-Rong
Subject: Re: deprecated register issues
Right. We ran into issues with reading back that register at runtime when UMDs
queried it when other stuff was in flight, so we just read it once at startup
and cache th
),
I will do some test against this CC_RB_BACKEND_DISABLE register, see if vm
flush failure issue could be avoided by removing those four register from SR
list
Thanks
/Monk
From: Deucher, Alexander
Sent: 2018年3月7日 23:13
To: Koenig, Christian ; Mao, David
; Liu, Monk
Cc: amd-gfx@lists.
, Christian
Sent: Wednesday, March 7, 2018 9:31:13 AM
To: Mao, David; Liu, Monk
Cc: Deucher, Alexander; amd-gfx@lists.freedesktop.org; Jin, Jian-Rong
Subject: Re: deprecated register issues
Hi David,
well I just figured that this is a misunderstanding.
Accessing this register and some other deprecated
com>>; Deucher,
Alexander mailto:alexander.deuc...@amd.com>>
*Cc:*amd-gfx@lists.freedesktop.org <mailto:amd-gfx@lists.freedesktop.org>
*Subject:*Re: deprecated register issues
Hi Monk,
I honestly don't have the slightest idea why we are still accessing
CC_RB_BACKEND_DISABLE. Maybe
Subject: Re: deprecated register issues
Hi Monk,
I honestly don't have the slightest idea why we are still accessing
CC_RB_BACKEND_DISABLE. Maybe it still contains some useful values?
Key point was that we needed to stop accessing it all the time to avoid
triggering problems.
Regards,
Chris
...@lists.freedesktop.org] On Behalf Of
Christian K?nig
Sent: 2018年3月7日 20:26
To: Liu, Monk ; Deucher, Alexander
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Hi Monk,
I honestly don't have the slightest idea why we are still accessing
CC_RB_BACKEND_DISABLE. Maybe it still con
Hi Monk,
I honestly don't have the slightest idea why we are still accessing
CC_RB_BACKEND_DISABLE. Maybe it still contains some useful values?
Key point was that we needed to stop accessing it all the time to avoid
triggering problems.
Regards,
Christian.
Am 07.03.2018 um 13:11 schrieb Li
Hi Christian
I remember you and AlexD mentioned that a handful registers are deprecated for
greenland (gfx9)
e.g. CC_RB_BACKEND_DISABLE
do you know why we still have this routine ?
static u32 gfx_v9_0_get_rb_active_bitmap(struct amdgpu_device *adev)
{
u32 data, mask;
data = RREG32_S
17 matches
Mail list logo
