Am 18.07.19 um 22:46 schrieb Greathouse, Joseph:
>> -Original Message-
>> From: Christian König
>> Sent: Thursday, July 18, 2019 3:14 AM
>> To: Kuehling, Felix ; Greathouse, Joseph
>> ; amd-gfx@lists.freedesktop.org
>> Subject: Re: [PATCH v2] drm/amd
> -Original Message-
> From: Christian König
> Sent: Thursday, July 18, 2019 3:14 AM
> To: Kuehling, Felix ; Greathouse, Joseph
> ; amd-gfx@lists.freedesktop.org
> Subject: Re: [PATCH v2] drm/amdgpu: Default disable GDS for compute
> VMIDs
>
> Am 17.07.19 um 22
Am 17.07.19 um 22:09 schrieb Kuehling, Felix:
On 2019-07-17 14:23, Greathouse, Joseph wrote:
The GDS and GWS blocks default to allowing all VMIDs to
access all entries. Graphics VMIDs can handle setting
these limits when the driver launches work. However,
compute workloads under HWS control
On 2019-07-17 14:23, Greathouse, Joseph wrote:
> The GDS and GWS blocks default to allowing all VMIDs to
> access all entries. Graphics VMIDs can handle setting
> these limits when the driver launches work. However,
> compute workloads under HWS control don't go through the
> kernel driver.
The GDS and GWS blocks default to allowing all VMIDs to
access all entries. Graphics VMIDs can handle setting
these limits when the driver launches work. However,
compute workloads under HWS control don't go through the
kernel driver. Instead, HWS firmware should set these
limits when a process is
