aboutsummaryrefslogtreecommitdiff
path: root/core/opal.c
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.vnet.ibm.com>2015-09-10 13:40:18 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>2015-09-10 13:40:18 +1000
commit1d31ae31aabae692484dc8c2e78f84dfa06aee99 (patch)
tree32b724290aa0dd0987366cbc123292022a1afe6e /core/opal.c
parentdbb59f077779bb6ae18dbef2eda79e61708f03bd (diff)
downloadskiboot-1d31ae31aabae692484dc8c2e78f84dfa06aee99.zip
skiboot-1d31ae31aabae692484dc8c2e78f84dfa06aee99.tar.gz
skiboot-1d31ae31aabae692484dc8c2e78f84dfa06aee99.tar.bz2
Remove FIXME for using atomics for opal_pending_events
The locking code is obviously correct and it's never shown up in a profile - so it's likely fine for a while yet. Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'core/opal.c')
-rw-r--r--core/opal.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/core/opal.c b/core/opal.c
index 4350ae7..c2c4d8d 100644
--- a/core/opal.c
+++ b/core/opal.c
@@ -168,7 +168,6 @@ void opal_update_pending_evt(uint64_t evt_mask, uint64_t evt_values)
{
uint64_t new_evts;
- /* XXX FIXME: Use atomics instead ??? Or caller locks (con_lock ?) */
lock(&evt_lock);
new_evts = (opal_pending_events & ~evt_mask) | evt_values;
if (opal_pending_events != new_evts) {