Quoting Michał Winiarski (2019-03-05 12:48:27)
> There are still some cases where userspace needs to change the
> preemption granularity for compute workloads. Let's whitelist the
> per-ctx granularity control register to allow it.
>
> Signed-off-by: Michał Winiarski
> Cc: Anuj Phogat
> Cc: Joon
On Tue, Mar 05, 2019 at 01:48:27PM +0100, Michał Winiarski wrote:
> There are still some cases where userspace needs to change the
> preemption granularity for compute workloads. Let's whitelist the
> per-ctx granularity control register to allow it.
We are not planning to enable it just yet but w
There are still some cases where userspace needs to change the
preemption granularity for compute workloads. Let's whitelist the
per-ctx granularity control register to allow it.
Signed-off-by: Michał Winiarski
Cc: Anuj Phogat
Cc: Joonas Lahtinen
Cc: Matt Roper
Cc: Rafael Antognolli
Cc: Chris
Quoting Michał Winiarski (2019-02-27 15:51:09)
> There are still some cases where userspace needs to change the
> preemption granularity for compute workloads. Let's whitelist the
> per-ctx granularity control register to allow it.
>
> Signed-off-by: Michał Winiarski
> Cc: Anuj Phogat
> Cc: Joon
Quoting Michał Winiarski (2019-02-27 15:51:09)
> There are still some cases where userspace needs to change the
> preemption granularity for compute workloads. Let's whitelist the
> per-ctx granularity control register to allow it.
Just wondering aloud if this should a single patch; change the def
There are still some cases where userspace needs to change the
preemption granularity for compute workloads. Let's whitelist the
per-ctx granularity control register to allow it.
Signed-off-by: Michał Winiarski
Cc: Anuj Phogat
Cc: Joonas Lahtinen
Cc: Matt Roper
Cc: Rafael Antognolli
---
driv
