Date: Thu, 16 Oct 2008 19:33:11 -0700 (PDT)
Message-Id: <20081016.193310.47274971.davem@davemloft.net>
To: mathieu.desnoyers@polymtl.ca
Cc: paulus@samba.org, torvalds@linux-foundation.org, akpm@linux-foundation.org,
       mingo@elte.hu, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
       rostedt@goodmis.org, a.p.zijlstra@chello.nl, tglx@linutronix.de,
       benh@kernel.crashing.org, mingo@redhat.com
Subject: Re: [RFC patch 04/15] get_cycles() : powerpc64 HAVE_GET_CYCLES
 (update)
From: David Miller <davem@davemloft.net>
In-Reply-To: <20081017020813.GA32468@Krystal>
References: <20081017004328.GA29768@Krystal>
	<20081016.184252.193691889.davem@davemloft.net>
	<20081017020813.GA32468@Krystal>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 904
Lines: 24

From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date: Thu, 16 Oct 2008 22:08:13 -0400

> * David Miller (davem@davemloft.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/