<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 2x Media CPU power usage, or 15% perf drop when CPU bound GPU use-case is TDP limited"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108700#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 2x Media CPU power usage, or 15% perf drop when CPU bound GPU use-case is TDP limited"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108700">bug 108700</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Jani Saarinen from <a href="show_bug.cgi?id=108700#c2">comment #2</a>)
<span class="quote">> Yeah, can you bisect Eero ;)</span >
I don't have anything set up that would automate bisecting kernel well enough
(reboots, boot failures, handling drm-tip rebases etc).
However, if you have in mind few commits in that range, I could manually check
whether they give good or bad performance.
And I can of course (internally) provide ready-made SW setup and reserve
suitable HW for whomever is going to look into this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>