<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86815#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86815">bug 86815</a>
from <span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span></b>
<pre>Hi, I'm not sure I can help you, but using 'perf' to try to see where exactly
that CPU is used when hogging it would be nice.
<a href="https://perf.wiki.kernel.org/index.php/Tutorial#Processor-wide_mode_2">https://perf.wiki.kernel.org/index.php/Tutorial#Processor-wide_mode_2</a>
That would be 'perf record -a', do the CPU hog, hit ctrl+c for perf to stop it,
and then you have a perf.data file to inspect with 'perf report'.
If you want to attach the perf.data file to this bug, then please also run
'perf archive' and attach the resulting perf.data.tar.bz2 or such too.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>