: Deucher, Alexander
Sent: 2018年3月9日 11:30
To: Liu, Monk <monk@amd.com>; Koenig, Christian <christian.koe...@amd.com>;
Mao, David <david@amd.com>
Cc: Jin, Jian-Rong <jian-rong@amd.com>; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Can GIM
; 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 acc
@amd.com>; Deucher, Alexander
<alexander.deuc...@amd.com>; Mao, David <david@amd.com>
Cc: Jin, Jian-Rong <jian-rong@amd.com>; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Although KMD now use a cache way to give libdrm the CC_RB_BACKEND_D
<alexander.deuc...@amd.com>; Mao, David <david@amd.com>
Cc: Jin, Jian-Rong <jian-rong@amd.com>; 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
<christian.koe...@amd.com>; Deucher, Alexander
<alexander.deuc...@amd.com>; Mao, David <david@amd.com>
*Cc:* Jin, Jian-Rong <jian-rong@amd.com>;
amd-gfx@lists.freedesktop.org
*Subject:* RE: deprecated register issues
Yeah, I agree with you we’d better find all those re
...@amd.com>; 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 issue in other place, I knew it.
The frustrating job is h
@amd.com>
Cc: Jin, Jian-Rong <jian-rong@amd.com>; amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Hi Monk,
While we can avoid such vm flush failure by stitch together of the sending REQ
and reading ACK part, at least for compute ring this is confirmed.
Well
tian; Mao, David
*Cc:* amd-gfx@lists.freedesktop.org
<mailto:amd-gfx@lists.freedesktop.org>; Jin, Jian-Rong
*Subject:* RE: deprecated register issues
Hi guys
According to Christian’s found, reading this register would make vm
hub failed to finish the vm flush request , e.g.: sdma is do
@amd.com>;
Mao, David <david@amd.com>
Cc: amd-gfx@lists.freedesktop.org; Jin, Jian-Rong <jian-rong@amd.com>
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 reg
n <christian.koe...@amd.com>; Mao, David
<david@amd.com>; Liu, Monk <monk@amd.com>
Cc: amd-gfx@lists.freedesktop.org; Jin, Jian-Rong <jian-rong@amd.com>
Subject: Re: deprecated register issues
Right. We ran into issues with reading back that register at
avid@amd.com>; Liu, Monk <monk@amd.com>
Cc: amd-gfx@lists.freedesktop.org; Jin, Jian-Rong <jian-rong@amd.com>
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
, 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
onk@amd.com <mailto:monk@amd.com>>; Deucher,
Alexander <alexander.deuc...@amd.com <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
t;
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 it still contains some useful values?
Key point was that we needed
...@lists.freedesktop.org] On Behalf Of
Christian K?nig
Sent: 2018年3月7日 20:26
To: Liu, Monk <monk@amd.com>; Deucher, Alexander <alexander.deuc...@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: deprecated register issues
Hi Monk,
I honestly don't have the slightest idea why we are sti
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
16 matches
Mail list logo
