diff options
author | Konsta Holtta <kholtta@nvidia.com> | 2018-02-14 11:12:47 -0500 |
---|---|---|
committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2018-03-07 12:45:04 -0500 |
commit | b063870f909f368820ae9b0726407d18dc28f24c (patch) | |
tree | 0b966c4628da3c52b46d2bcd386f6c4dbf5735ec /drivers/gpu/nvgpu/common/linux/nvgpu_mem.c | |
parent | ca95adb2d4e51431de2f8fbe252bade55ba0ed46 (diff) |
gpu: nvgpu: BUG_ON for sema increment, not value
When adding a sema wait to a pushbuf, verify that the sema threshold has
been incremented from the original value by reading the incremented
field instead of value (which is set to nonzero by
nvgpu_semaphore_incr()). Value could be 0 even after an increment if new
semas weren't reset to 0.
Jira NVGPU-514
Change-Id: I295451fbc7eb9e597aea12d73074e99f74a6a899
Signed-off-by: Konsta Holtta <kholtta@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1658100
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/common/linux/nvgpu_mem.c')
0 files changed, 0 insertions, 0 deletions