public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dhaval@linux.vnet.ibm.com
Cc: mingo@elte.hu, 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
Subject: Re: [RFC][PATCH] sched_clock_cpu()
Date: Sat, 03 May 2008 21:16:46 -0700 (PDT)	[thread overview]
Message-ID: <20080503.211646.250661233.davem@davemloft.net> (raw)
In-Reply-To: <20080503173023.GA2394@linux.vnet.ibm.com>

From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Date: Sat, 3 May 2008 23:00:23 +0530

> On Sat, May 03, 2008 at 06:55:11PM +0200, Ingo Molnar wrote:
> > 
> > * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > 
> > > it _DOESN'T_ boot ;-/ [...]
> > 
> > FYI, the merged version against sched-devel.git does boot fine here and 
> > the clock does seem to advance as expected.
> > 
> 
> boots here against linus as well.

If you tested on powerpc (just guessing), did you set
HAVE_STABLE_CLOCK in arch/powerpc/Kconfig?  That's
what you'll need to do to take advantage of the
new code.

  parent reply	other threads:[~2008-05-04  4:16 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 [this message]
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
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.211646.250661233.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