<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:huax.lu@intel.com" title="lu hua <huax.lu@intel.com>"> <span class="fn">lu hua</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW Bisected]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90332">bug 90332</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>[HSW Regression]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails
</td>
<td>[HSW Bisected]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW Bisected]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90332#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW Bisected]ES3-CTS.shaders.uniform_block.random.all_shared_buffer.12 fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90332">bug 90332</a>
from <span class="vcard"><a class="email" href="mailto:huax.lu@intel.com" title="lu hua <huax.lu@intel.com>"> <span class="fn">lu hua</span></a>
</span></b>
<pre>84d56e66b9b4a646f04ec30696ca1aeea5e654d5 is the first bad commit
commit 84d56e66b9b4a646f04ec30696ca1aeea5e654d5
Author: Ulrich Obergfell <<a href="mailto:uobergfe@redhat.com">uobergfe@redhat.com</a>>
AuthorDate: Tue Apr 14 15:43:55 2015 -0700
Commit: Linus Torvalds <<a href="mailto:torvalds@linux-foundation.org">torvalds@linux-foundation.org</a>>
CommitDate: Tue Apr 14 16:48:58 2015 -0700
watchdog: new definitions and variables, initialization
The hardlockup and softockup had always been tied together. Due to the
request of KVM folks, they had a need to have one enabled but not the
other. Internally rework the code to split things apart more cleanly.
There is a bunch of churn here, but the end result should be code that
should be easier to maintain and fix without knowing the internals of what
is going on.
This patch (of 9):
Introduce new definitions and variables to separate the user interface in
/proc/sys/kernel from the internal run state of the lockup detectors. The
internal run state is represented by two bits in a new variable that is
named 'watchdog_enabled'. This helps simplify the code, for example:
- In order to check if any of the two lockup detectors is enabled,
it is sufficient to check if 'watchdog_enabled' is not zero.
- In order to enable/disable one or both lockup detectors,
it is sufficient to set/clear one or both bits in 'watchdog_enabled'.
- Concurrent updates of 'watchdog_enabled' need not be synchronized via
a spinlock or a mutex. Updates can either be atomic or concurrency can
be detected by using 'cmpxchg'.
Signed-off-by: Ulrich Obergfell <<a href="mailto:uobergfe@redhat.com">uobergfe@redhat.com</a>>
Signed-off-by: Don Zickus <<a href="mailto:dzickus@redhat.com">dzickus@redhat.com</a>>
Cc: Ingo Molnar <<a href="mailto:mingo@elte.hu">mingo@elte.hu</a>>
Signed-off-by: Andrew Morton <<a href="mailto:akpm@linux-foundation.org">akpm@linux-foundation.org</a>>
Signed-off-by: Linus Torvalds <<a href="mailto:torvalds@linux-foundation.org">torvalds@linux-foundation.org</a>></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>