All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111987] Unstable performance (periodic and repeating patterns of fps change) and changing VDDGFX
Date: Sun, 13 Oct 2019 09:34:06 +0000	[thread overview]
Message-ID: <bug-111987-502-n9y7tRpdih@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111987-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4523 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111987

--- Comment #8 from Witold Baryluk <witold.baryluk+freedesktop@gmail.com> ---
My random guess is that it is due to some bug in calculating gpu_busy_percent
possibly, or SCLK_{UP,DOWN}_HYST parameters:

Here is a dump of various values, when running Talos:

Sun Oct 13 09:29:46 UTC 2019
/sys/class/drm/renderD128/device files:
gpu_busy_percent:5
pp_num_states:states: 2
pp_num_states:0 boot
pp_num_states:1 performance
pp_cur_state:1
pp_power_profile_mode:NUM        MODE_NAME     SCLK_UP_HYST   SCLK_DOWN_HYST
SCLK_ACTIVE_LEVEL     MCLK_UP_HYST   MCLK_DOWN_HYST MCLK_ACTIVE_LEVEL
pp_power_profile_mode:  0   BOOTUP_DEFAULT:        -                -          
     -                -                -                -
pp_power_profile_mode:  1   3D_FULL_SCREEN:        0              100          
    30                0              100               10
pp_power_profile_mode:  2     POWER_SAVING:       10                0          
    30                -                -                -
pp_power_profile_mode:  3            VIDEO:        -                -          
     -               10               16               31
pp_power_profile_mode:  4               VR:        0               11          
    50                0              100               10
pp_power_profile_mode:  5        COMPUTE *:        0                5          
    30                0              100               10
pp_power_profile_mode:  6           CUSTOM:        -                -          
     -                -                -                -
vbios_version:113-C8800100-102
revision:0xc8
mem_info_gtt_total:4294967296
mem_info_gtt_used:364883968
mem_info_vis_vram_total:268435456
mem_info_vis_vram_used:50188288
mem_info_vram_total:4294967296
mem_info_vram_used:2290094080
power_dpm_force_performance_level:manual
power_dpm_state:performance
hwmon/hwmon0/freq1_label:sclk
hwmon/hwmon0/freq1_input:944000000
hwmon/hwmon0/freq2_label:mclk
hwmon/hwmon0/freq2_input:500000000
hwmon/hwmon0/temp1_input:31000
hwmon/hwmon0/power1_average:85182000
hwmon/hwmon0/fan1_input:3069
hwmon/hwmon0/pwm1:239
hwmon/hwmon0/in0_label:vddgfx
hwmon/hwmon0/in0_input:1100
pp_dpm_mclk:0: 500Mhz *
pp_dpm_sclk:0: 300Mhz 
pp_dpm_sclk:1: 512Mhz 
pp_dpm_sclk:2: 724Mhz 
pp_dpm_sclk:3: 892Mhz 
pp_dpm_sclk:4: 944Mhz *
pp_dpm_sclk:5: 984Mhz 
pp_dpm_sclk:6: 1018Mhz 
pp_dpm_sclk:7: 1050Mhz 
pp_mclk_od:0
pp_sclk_od:0
d3cold_allowed:1
power_dpm_force_performance_level:manual
/sys/class/drm/ttm/buffer_objects/bo_count:2997
/sys/kernel/debug/dri/0/clients:             command   pid dev master a   uid  
   magic
/sys/kernel/debug/dri/0/clients:                Xorg 118921   0   y    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:                Xorg 118921 128   n    y     0 
        0
/sys/kernel/debug/dri/0/clients:               Talos 37263 128   n    n  1000  
       0


The default pp_power_profile_mode was 1 (3D_FULL_SCREEN). I switched it just
now to 5 (COMPUTE), but results are the same.

The gpu_busy_percent switches every second between something close to 0 and
something close to 100. Despite the game constantly submitting the work and
rendering at ~200 FPS.

The pp_dpm_sclk starts high and slowly goes down step by step, and eventually
goes back to 7 (1050MHz), and process repeats.

I tried doing:

echo "7" >  /sys/class/drm/card0/device/pp_dpm_sclk
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level

and I see no differences, still same effect.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5429 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-10-13  9:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13  5:03 [Bug 111987] Unstable performance (periodic and repeating patterns of fps change) and changing VDDGFX bugzilla-daemon
2019-10-13  5:03 ` bugzilla-daemon
2019-10-13  5:04 ` bugzilla-daemon
2019-10-13  5:08 ` bugzilla-daemon
2019-10-13  5:08 ` bugzilla-daemon
2019-10-13  5:13 ` bugzilla-daemon
2019-10-13  5:14 ` bugzilla-daemon
2019-10-13  5:15 ` bugzilla-daemon
2019-10-13  5:24 ` bugzilla-daemon
2019-10-13  9:34 ` bugzilla-daemon [this message]
2019-10-13 10:08 ` bugzilla-daemon
2019-10-13 10:25 ` bugzilla-daemon
2019-10-15 20:54 ` bugzilla-daemon
2019-10-16 12:44 ` bugzilla-daemon
2019-10-17 11:51 ` bugzilla-daemon
2019-10-17 13:06 ` bugzilla-daemon
2019-10-17 18:12 ` bugzilla-daemon
2019-10-17 18:19 ` bugzilla-daemon
2019-10-17 18:41 ` bugzilla-daemon
2019-11-19  9:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111987-502-n9y7tRpdih@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.