All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84663] high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME
Date: Wed, 08 Oct 2014 02:50:44 +0000	[thread overview]
Message-ID: <bug-84663-502-TtxAMF8Xf6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84663-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Christoph Haag from comment #4)
> I hope this is better.

Yes, looks better, thanks.

> By the way, Is there a better way to profile something likethis or is
> sysprof already the most appropriate tool?

I find sysprof's UI the most intuitive, but perf is nice as well.


I don't notice anything using obviously too much CPU in your profile. Can you
get a screenshot with GALLIUM_HUD like in bug 84570?

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

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

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

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

  parent reply	other threads:[~2014-10-08  2:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04 15:19 [Bug 84663] New: high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME bugzilla-daemon
2014-10-06  8:41 ` [Bug 84663] " bugzilla-daemon
2014-10-06 11:48 ` bugzilla-daemon
2014-10-07  1:58 ` bugzilla-daemon
2014-10-07 11:04 ` bugzilla-daemon
2014-10-08  2:50 ` bugzilla-daemon [this message]
2014-10-09  7:54 ` bugzilla-daemon
2014-10-10  2:41 ` bugzilla-daemon
2014-10-10 13:46 ` bugzilla-daemon
2014-11-10 15:21 ` bugzilla-daemon
2017-03-12 11:11 ` bugzilla-daemon
2017-03-13 20:04 ` 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-84663-502-TtxAMF8Xf6@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.