[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081016.193310.47274971.davem@davemloft.net>
Date: Thu, 16 Oct 2008 19:33:11 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mathieu.desnoyers@...ymtl.ca
Cc: paulus@...ba.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, mingo@...e.hu,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
rostedt@...dmis.org, a.p.zijlstra@...llo.nl, tglx@...utronix.de,
benh@...nel.crashing.org, mingo@...hat.com
Subject: Re: [RFC patch 04/15] get_cycles() : powerpc64 HAVE_GET_CYCLES
(update)
From: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Date: Thu, 16 Oct 2008 22:08:13 -0400
> * David Miller (davem@...emloft.net) wrote:
> > Date: Thu, 16 Oct 2008 20:43:28 -0400
> >
> > You'll need to make a similar fix on sparc64.
>
> I guess you are talking about using sparc64_get_clock_tick rather than
> CLOCK_TICK_RATE ? I assume sparc64_get_clock_tick() done on any CPU will
> return the same rate ?
You'll need to use tb_ticks_per_usec or similar.
The ->get_tick() thing you are using uses a TICK source which is
synchronized across the entire system and advances at a non-changing
rate.
sparc64_get_clock_tick() returns something different.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists