RE: "double" hpet clocksource && hard freeze [bisected]

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Luck, Tony <tony.luck@...>
Cc: Paolo Ornati <ornati@...>, Linux Kernel Mailing List <linux-kernel@...>, Bob Picco <bob.picco@...>
Date: Thursday, August 23, 2007 - 5:41 pm

On Thu, 2007-08-23 at 14:05 -0700, john stultz wrote:

Here is a possible quick fix. I'm open to other approaches, but I also
want to avoid too much churn before 2.6.23 goes out.

Paolo, could you verify this fixes the issue for you?

thanks
-john

diff --git a/drivers/char/hpet.c b/drivers/char/hpet.c
index 77bf4aa..c782d8c 100644
--- a/drivers/char/hpet.c
+++ b/drivers/char/hpet.c
@@ -78,7 +78,17 @@ static struct clocksource clocksource_hpet = {
         .shift          = 10,
         .flags          = CLOCK_SOURCE_IS_CONTINUOUS,
 };
+
+/* XXX - FIXME: i386, x86_64 and ia64 all have separate 
+ * hpet clocksource implementations. They should be merged 
+ * and this would be a good place for it.
+ * Right now this is ia64 only.
+ */
+#ifdef CONFIG_IA64
 static struct clocksource *hpet_clocksource;
+#else /* this isn't generic enough to use for everyone yet */
+static struct clocksource *hpet_clocksource = (struct clocksource*)0xdead;
+#endif
 
 /* A lock for concurrent access by app and isr hpet activity. */
 static DEFINE_SPINLOCK(hpet_lock);


-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
RE: "double" hpet clocksource && hard freeze [bisected], john stultz, (Thu Aug 23, 5:41 pm)
Re: "double" hpet clocksource &amp;&amp; hard freeze [bisected], Luiz Fernando N. Capitulino..., (Mon Aug 27, 4:34 pm)