dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97075] VCE encoding slow when GPU is not stressed (HD 7970M)
Date: Mon, 25 Jul 2016 17:04:48 +0000	[thread overview]
Message-ID: <bug-97075-502-XLvYVI8jJp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97075-502@http.bugs.freedesktop.org/>


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

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

Andy Furniss <adf.lists@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adf.lists@gmail.com

--- Comment #2 from Andy Furniss <adf.lists@gmail.com> ---
So maybe there is also some dpm type issue on your system.

Rather than running gears maybe there is somewhere you can force gpu clocks to
high.

My setup is very different but I would do -

echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

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

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

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

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

  parent reply	other threads:[~2016-07-25 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 14:27 [Bug 97075] VCE encoding slow when GPU is not stressed (HD 7970M) bugzilla-daemon
2016-07-25 14:43 ` bugzilla-daemon
2016-07-25 17:04 ` bugzilla-daemon [this message]
2016-07-25 17:07 ` bugzilla-daemon
2016-07-25 17:28 ` bugzilla-daemon
2016-07-25 17:29 ` bugzilla-daemon
2016-07-25 18:13 ` bugzilla-daemon
2016-07-26  7:57 ` bugzilla-daemon
2019-09-25 17:54 ` 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-97075-502-XLvYVI8jJp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox