From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: a.p.zijlstra@chello.nl, tglx@linutronix.de, guichaz@gmail.com,
andi@firstfloor.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, efault@gmx.de,
dhaval@linux.vnet.ibm.com
Subject: Re: [RFC][PATCH] sched_clock_cpu()
Date: Sat, 03 May 2008 21:26:07 -0700 (PDT) [thread overview]
Message-ID: <20080503.212607.157994166.davem@davemloft.net> (raw)
In-Reply-To: <20080503170130.GB21967@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Sat, 3 May 2008 19:01:30 +0200
>
> * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > it _DOESN'T_ boot ;-/ and I seem to have caught a flu that makes my
> > whole body hurt like hell, so I'm not getting anything done.
>
> i think i see where your boot problem comes from:
>
> > +struct sched_clock_data {
> > + spinlock_t lock;
>
> that wont work very well when sched_clock() is called from within
> CONFIG_LOCK_STAT instrumentation. Does the patch below solve the boot
> problems for you?
Also, no platform can set HAVE_STABLE_CLOCK until we instantiate it in
a Kconfig somewhere. I've choosen to do it in kernel/Kconfig.hz and
here are the sparc/sparc64 bits as well, I've booted this up with
Peter's patch on my 64-cpu niagara2 box and done some basic testing.
It would be nice if a powerpc person could test the trivial
powerpc Kconfig patch.
Possibly this should be HAVE_UNSTABLE_CLOCK, then only one platform
needs to set it :-)
sparc: Instantiate and set HAVE_STABLE_CLOCK
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
index d211fdb..c60f5d4 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/Kconfig
@@ -69,6 +69,7 @@ config SPARC
select HAVE_IDE
select HAVE_OPROFILE
select HAVE_ARCH_KGDB if !SMP
+ select HAVE_STABLE_CLOCK
# Identify this as a Sparc32 build
config SPARC32
diff --git a/arch/sparc64/Kconfig b/arch/sparc64/Kconfig
index eb36f3b..711d4b1 100644
--- a/arch/sparc64/Kconfig
+++ b/arch/sparc64/Kconfig
@@ -14,6 +14,7 @@ config SPARC64
select HAVE_IDE
select HAVE_LMB
select HAVE_ARCH_KGDB
+ select HAVE_STABLE_CLOCK
config GENERIC_TIME
bool
diff --git a/kernel/Kconfig.hz b/kernel/Kconfig.hz
index 526128a..b88c82a 100644
--- a/kernel/Kconfig.hz
+++ b/kernel/Kconfig.hz
@@ -56,3 +56,6 @@ config HZ
config SCHED_HRTICK
def_bool HIGH_RES_TIMERS && X86
+
+config HAVE_STABLE_CLOCK
+ boolean
next prev parent reply other threads:[~2008-05-04 4:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 16:29 [RFC][PATCH] sched_clock_cpu() Peter Zijlstra
2008-05-03 16:29 ` Peter Zijlstra
2008-05-03 16:37 ` Ingo Molnar
2008-05-03 16:37 ` Ingo Molnar
2008-05-03 16:55 ` Ingo Molnar
2008-05-03 17:30 ` Dhaval Giani
2008-05-03 17:30 ` Dhaval Giani
2008-05-04 4:16 ` David Miller
2008-05-04 4:30 ` Dhaval Giani
2008-05-04 4:38 ` Dhaval Giani
2008-05-04 4:38 ` Dhaval Giani
2008-05-03 17:01 ` Ingo Molnar
2008-05-04 4:26 ` David Miller [this message]
2008-05-04 5:09 ` Dhaval Giani
2008-05-04 9:00 ` Ingo Molnar
2008-05-05 11:32 ` Ingo Molnar
2008-05-05 21:47 ` Tony Breeds
2008-05-05 21:47 ` Tony Breeds
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=20080503.212607.157994166.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=guichaz@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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