Reviewed-by: Bas Nieuwenhuizen for then,
because the Mesa code indeed prevents AMDGPU_CHUNK_ID_FENCE in
submissions.
On Wed, May 8, 2019 at 3:24 PM Christian König
wrote:
>
> Am 08.05.19 um 15:23 schrieb Liu, Leo:
> > On 5/8/19 9:19 AM, Koenig, Christian wrote:
> >> Am 08.05.19 um 15:14 schrieb
Am 08.05.19 um 15:23 schrieb Liu, Leo:
On 5/8/19 9:19 AM, Koenig, Christian wrote:
Am 08.05.19 um 15:14 schrieb Liu, Leo:
On 5/8/19 9:02 AM, Christian König wrote:
[CAUTION: External Email]
Am 08.05.19 um 14:56 schrieb Liu, Leo:
There is no user fence for JPEG, the bug triggering
kernel
On 5/8/19 9:19 AM, Koenig, Christian wrote:
> Am 08.05.19 um 15:14 schrieb Liu, Leo:
>> On 5/8/19 9:02 AM, Christian König wrote:
>>> [CAUTION: External Email]
>>>
>>> Am 08.05.19 um 14:56 schrieb Liu, Leo:
There is no user fence for JPEG, the bug triggering
kernel WARN_ON(flags &
Am 08.05.19 um 15:14 schrieb Liu, Leo:
> On 5/8/19 9:02 AM, Christian König wrote:
>> [CAUTION: External Email]
>>
>> Am 08.05.19 um 14:56 schrieb Liu, Leo:
>>> There is no user fence for JPEG, the bug triggering
>>> kernel WARN_ON(flags & AMDGPU_FENCE_FLAG_64BIT)
>> Oh, we are probably going to
On 5/8/19 9:02 AM, Christian König wrote:
> [CAUTION: External Email]
>
> Am 08.05.19 um 14:56 schrieb Liu, Leo:
>> There is no user fence for JPEG, the bug triggering
>> kernel WARN_ON(flags & AMDGPU_FENCE_FLAG_64BIT)
>
> Oh, we are probably going to need to check for this in the kernel as
>
Am 08.05.19 um 14:56 schrieb Liu, Leo:
There is no user fence for JPEG, the bug triggering
kernel WARN_ON(flags & AMDGPU_FENCE_FLAG_64BIT)
Oh, we are probably going to need to check for this in the kernel as well.
Currently we only check for UVD and VCE there, do you want to take a
look Leo
There is no user fence for JPEG, the bug triggering
kernel WARN_ON(flags & AMDGPU_FENCE_FLAG_64BIT)
Signed-off-by: Leo Liu
Cc: mesa-sta...@lists.freedesktop.org
---
src/gallium/winsys/amdgpu/drm/amdgpu_cs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
