<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [CI][SHARDS] igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b - dmesg-warn - Delta way too big!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111883#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [CI][SHARDS] igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b - dmesg-warn - Delta way too big!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111883">bug 111883</a>
from <span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span></b>
<pre>I believe using global clock has a performance impact (although only for
specific operations so I'm not sure how visible it is to an end user), but
should be safe in general. Unfortunately I don't believe the kernel can detect
that a platform is going to have an unstable clock through suspend/resume and
will need to fall back to the global clock until it's too late (i.e., once it's
already actually gone through a suspend cycle).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>