summaryrefslogtreecommitdiffstats
path: root/userspace/units/posix-env/posix-env.c
diff options
context:
space:
mode:
authorLeon Yu <leoyu@nvidia.com>2019-08-21 09:02:12 -0400
committermobile promotions <svcmobile_promotions@nvidia.com>2019-08-30 04:25:01 -0400
commitd601ff515902b4840109742f5f2ac8881058405c (patch)
treec90ceedd7b131d774d5acde6f1872c6536c46423 /userspace/units/posix-env/posix-env.c
parent84f48df530a6ce0423920ebd8fd4e1dde52dd09f (diff)
nvgpu: don't report max load when counter overflow
This is to prevent GPU (and thus EMC) frequency from being boosted from time to time when system is completely idle. It's caused by max GPU load being incorrectly reported by perfmon. When the issue happens, it can be observed that max load is reported but busy_cycles read from PMU is actually zero. Even though busy and total cycles returned by PMU may not be completely accurate when counter overflows, the counters accumulated so far still have some value that we shouldn't ignore. OTOH, returning max load could be the least accurate approximation in such cases. So let's just clear the interrupt status and let rest of the code handle the exception cases. Bug 200545546 Change-Id: I6882ae265029e881f5417fb2b82005b0112b0fda Signed-off-by: Leon Yu <leoyu@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2180771 Reviewed-by: Peng Liu <pengliu@nvidia.com> Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Mubushir Rahman <mubushirr@nvidia.com> Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'userspace/units/posix-env/posix-env.c')
0 files changed, 0 insertions, 0 deletions