From: Daniel Walker <dwalker@mvista.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 10/12] clocksource: add block notifier
Date: Mon, 22 Jan 2007 21:53:05 -0800 [thread overview]
Message-ID: <20070123055347.665062757@mvista.com> (raw)
In-Reply-To: 20070123055255.338254780@mvista.com
[-- Attachment #1: clocksource_add_block_notify_on_new_clock.patch --]
[-- Type: text/plain, Size: 3606 bytes --]
Adds a call back interface for register/rating change events. This is also used
later in this series to signal other interesting events.
Signed-Off-By: Daniel Walker <dwalker@mvista.com>
---
include/linux/clocksource.h | 37 +++++++++++++++++++++++++++++++++++++
include/linux/timekeeping.h | 3 +++
kernel/time/clocksource.c | 10 ++++++++++
3 files changed, 50 insertions(+)
Index: linux-2.6.19/include/linux/clocksource.h
===================================================================
--- linux-2.6.19.orig/include/linux/clocksource.h
+++ linux-2.6.19/include/linux/clocksource.h
@@ -14,6 +14,7 @@
#include <linux/list.h>
#include <linux/plist.h>
#include <linux/sysdev.h>
+#include <linux/notifier.h>
#include <asm/div64.h>
#include <asm/io.h>
@@ -24,6 +25,42 @@ typedef u64 cycle_t;
/* XXX - Would like a better way for initializing curr_clocksource */
extern struct clocksource clocksource_jiffies;
+/*
+ * Allows inlined calling for notifier routines.
+ */
+extern struct atomic_notifier_head clocksource_list_notifier;
+
+/*
+ * Block notifier flags.
+ */
+#define CLOCKSOURCE_NOTIFY_REGISTER 1
+#define CLOCKSOURCE_NOTIFY_RATING 2
+#define CLOCKSOURCE_NOTIFY_FREQ 4
+
+/**
+ * clocksource_notifier_register - Registers a list change notifier
+ * @nb: pointer to a notifier block
+ *
+ * Returns zero always.
+ */
+static inline int clocksource_notifier_register(struct notifier_block *nb)
+{
+ return atomic_notifier_chain_register(&clocksource_list_notifier, nb);
+}
+
+/**
+ * clocksource_freq_change - Allows notification of dynamic frequency changes.
+ *
+ * Signals that a clocksource is dynamically changing it's frequency.
+ * This could happen if a clocksource becomes more/less stable.
+ */
+static inline void clocksource_freq_change(struct clocksource *c)
+{
+ atomic_notifier_call_chain(&clocksource_list_notifier,
+ CLOCKSOURCE_NOTIFY_FREQ, c);
+}
+
+
/**
* struct clocksource - hardware abstraction for a free running counter
* Provides mostly state-free accessors to the underlying hardware.
Index: linux-2.6.19/include/linux/timekeeping.h
===================================================================
--- linux-2.6.19.orig/include/linux/timekeeping.h
+++ linux-2.6.19/include/linux/timekeeping.h
@@ -14,6 +14,9 @@ static inline int change_clocksource(voi
{
return 0;
}
+
+static inline void change_clocksource(void) { }
+
#endif /* !CONFIG_GENERIC_TIME */
#endif /* _LINUX_TIMEKEEPING_H */
Index: linux-2.6.19/kernel/time/clocksource.c
===================================================================
--- linux-2.6.19.orig/kernel/time/clocksource.c
+++ linux-2.6.19/kernel/time/clocksource.c
@@ -49,6 +49,8 @@ static DEFINE_SPINLOCK(clocksource_lock)
static char override_name[32];
static int finished_booting;
+ATOMIC_NOTIFIER_HEAD(clocksource_list_notifier);
+
/* clocksource_done_booting - Called near the end of bootup
*
* Hack to avoid lots of clocksource churn at boot time
@@ -196,6 +198,10 @@ int clocksource_register(struct clocksou
next_clocksource = select_clocksource();
}
spin_unlock_irqrestore(&clocksource_lock, flags);
+
+ atomic_notifier_call_chain(&clocksource_list_notifier,
+ CLOCKSOURCE_NOTIFY_REGISTER, c);
+
return ret;
}
EXPORT_SYMBOL(clocksource_register);
@@ -224,6 +230,10 @@ void clocksource_rating_change(struct cl
next_clocksource = select_clocksource();
spin_unlock_irqrestore(&clocksource_lock, flags);
+
+ atomic_notifier_call_chain(&clocksource_list_notifier,
+ CLOCKSOURCE_NOTIFY_RATING, c);
+
}
EXPORT_SYMBOL(clocksource_rating_change);
--
next prev parent reply other threads:[~2007-01-23 5:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 5:52 [PATCH 00/12] clocksource/timekeeping cleanup Daniel Walker
2007-01-23 5:52 ` [PATCH 01/12] timekeeping: create kernel/time/timekeeping.c Daniel Walker
2007-01-23 5:52 ` [PATCH 02/12] clocksource: rating sorted list Daniel Walker
2007-01-23 5:52 ` [PATCH 03/12] clocksource: arm initialize list value Daniel Walker
2007-01-23 5:52 ` [PATCH 04/12] clocksource: avr32 " Daniel Walker
2007-01-23 12:42 ` Haavard Skinnemoen
2007-01-23 13:02 ` Daniel Walker
2007-01-23 13:44 ` Haavard Skinnemoen
2007-01-23 5:53 ` [PATCH 05/12] clocksource: mips " Daniel Walker
2007-01-23 5:53 ` [PATCH 06/12] clocksource: i386 " Daniel Walker
2007-01-23 5:53 ` [PATCH 07/12] clocksource: x86_64 " Daniel Walker
2007-01-23 5:53 ` [PATCH 08/12] clocksource: driver " Daniel Walker
2007-01-23 5:53 ` [PATCH 09/12] clocksource: " Daniel Walker
2007-01-23 5:53 ` Daniel Walker [this message]
2007-01-23 5:53 ` [PATCH 11/12] clocksource: remove update_callback Daniel Walker
2007-01-23 5:53 ` [PATCH 12/12] clocksource: atomic signals Daniel Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070123055347.665062757@mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox