[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160822233320.4548-22-nicstange@gmail.com>
Date: Tue, 23 Aug 2016 01:33:19 +0200
From: Nicolai Stange <nicstange@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
Nicolai Stange <nicstange@...il.com>
Subject: [RFC v4 21/22] clockevents: make setting of ->mult and ->mult_adjusted atomic
In order to avoid races between setting a struct clock_event_device's
->mult_adjusted in clockevents_update_freq() and yet to be implemented
updates triggered from the timekeeping core, the setting of ->mult and
->mult_adjusted should be made atomic.
Protect the update in clockevents_update_freq() by locking the
clockevents_lock spinlock. Frequency updates are expected to be done
seldomly and thus, taking this subsystem lock should not have any impact
on performance.
Note that the call to tick_broadcast_update_freq() is also protected
by this clockevents_lock and thus, this patch introduces the locking
dependency clockevents_lock -> tick_broadcast_lock.
Signed-off-by: Nicolai Stange <nicstange@...il.com>
---
kernel/time/clockevents.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index 8a89b8a..ee7cd40 100644
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -592,11 +592,11 @@ int clockevents_update_freq(struct clock_event_device *dev, u32 freq)
unsigned long flags;
int ret;
- local_irq_save(flags);
+ raw_spin_lock_irqsave(&clockevents_lock, flags);
ret = tick_broadcast_update_freq(dev, freq);
if (ret == -ENODEV)
ret = __clockevents_update_freq(dev, freq);
- local_irq_restore(flags);
+ raw_spin_unlock_irqrestore(&clockevents_lock, flags);
return ret;
}
--
2.9.2
Powered by blists - more mailing lists