Summary: | feature request: allow increasing maxium GPU power consumption like implemented in Wattman on Windows | ||
---|---|---|---|
Product: | DRI | Reporter: | tempel.julian |
Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | grmat, hugosv.mlg |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
tempel.julian
2018-05-03 12:15:16 UTC
It is implemented. power1_cap_min/max are RO. They define the range of values that are valid for power. The OEM defines the range and the information is stored in tables in the vbios. The driver uses that to set the range of valid values. My understanding is that windows does the same thing. I'll see if I can find out why you are seeing a different limit on windows. I suppose the Windows Wattman doesn't consider the values defined by the OEM and instead always allows +75% (not 50% as I mentioned before) on top of the card's value that is defined for 100%: https://abload.de/img/759nu06.png I had a Sapphire RX 580 Nitro installed instead of my MSI RX 560 Aero. The Sapphire card offers two bioses. Under Windows, one allows increasing power up 20%, the other bios up to 50%. Under Linux, power1_cap_max always showed just the 100% ASIC power value with both bioses. So it seems reading out the max values from the bios just doesn't work with the "Linux Wattman"? I am having the same issue. That is a big problem cause GPU cannot reach its max power. A RX Vega 64 for example can consume around 300w with OC and the 220w is causing frame drops in the case of games. It got implemented into 4.21 WIP kernel: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.21-wip&id=f7becf9a0803030ae125189823328e2d62b90f7b I can confirm it works, big thanks @ Joseph Greathouse! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.