From: Chris Wilson <chris@chris-wilson.co.uk>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: xserver-xorg-video-radeon 6.14.4: X has constant 10 % CPU usage
Date: Tue, 11 Sep 2012 14:18:30 +0100 [thread overview]
Message-ID: <6c3329$605gtu@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1347368861.5438.26.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Tue, 11 Sep 2012 15:07:41 +0200, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> Am Dienstag, den 11.09.2012, 14:55 +0200 schrieb Michel Dänzer:
> > I'd focus on profiling the X server, making sure the profiles show
> > symbols, ideally with call graphs. sysprof or perf might work better for
> > this than oprofile.
>
> Thanks. Lucky me, that this is not needed now and I can postpone how to
> figure out how to start X that way under Debian with GDM.
For future reference, sysprof and perf can be used to perform system
wide profiling - that is you can launch them after starting the task you
need to profile. For sysprof this is its default mode, and for perf you
need 'perf record -a'
A quick 'sudo perf top' is always a useful first step. For best results,
make sure you have debugging symbols and frame pointers.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- 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
next prev parent reply other threads:[~2012-09-11 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 12:42 xserver-xorg-video-radeon 6.14.4: X has constant 10 % CPU usage Paul Menzel
2012-09-11 12:55 ` Michel Dänzer
2012-09-11 13:07 ` Paul Menzel
2012-09-11 13:18 ` Chris Wilson [this message]
2012-09-11 13:24 ` Michel Dänzer
2012-09-12 13:29 ` Paul Menzel
2012-09-14 15:01 ` Michel Dänzer
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='6c3329$605gtu@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=paulepanter@users.sourceforge.net \
/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.