linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, benh@ozlabs.org,
	linuxppc-dev@ozlabs.org, tglx@linutronix.de, arndb@de.ibm.com,
	mingo@elte.hu, David Miller <davem@davemloft.net>
Subject: Re: cpu_clock confusion
Date: Mon, 28 Apr 2008 10:46:30 +0200	[thread overview]
Message-ID: <20080428084630.GA1623@iram.es> (raw)
In-Reply-To: <1209029257.3357.55.camel@johannes.berg>

On Thu, Apr 24, 2008 at 11:27:37AM +0200, Johannes Berg wrote:
> On Thu, 2008-04-24 at 02:24 -0700, David Miller wrote:
> > From: Johannes Berg <johannes@sipsolutions.net>
> > Date: Thu, 24 Apr 2008 11:21:52 +0200
> > 
> > > Hmm. Why is that whole cpu_clock stuff in place anyway? powerpc has
> > > perfectly synchronised time across processors with dirt cheap access to
> > > it as well, so why build all this code that only messes it up on top of
> > > it?
> > 
> > Same on sparc64.  These changes add more bugs than they fix.
> 
> I tend to think all this clock business should be done local to those
> arches that aren't capable of providing cheap, useful synchronised and
> accurate clocks themselves. Or be a lib that they can link in if needed.
> As it stands, it seems to me that it all just penalises those
> architectures that have decent clocks.

100% agreed. 

	Gabriel

      reply	other threads:[~2008-04-28  8:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 14:23 printk time confusion? Johannes Berg
2008-04-03 10:48 ` Benjamin Herrenschmidt
2008-04-03 11:07   ` Johannes Berg
2008-04-03 11:08   ` Andreas Schwab
2008-04-03 11:12     ` Johannes Berg
2008-04-03 11:24       ` Andreas Schwab
2008-04-03 16:34   ` cpu_clock confusion (was: printk time confusion?) Johannes Berg
2008-04-04 14:46     ` Ingo Molnar
2008-04-24  9:21       ` Johannes Berg
2008-04-24  9:24         ` cpu_clock confusion David Miller
2008-04-24  9:27           ` Johannes Berg
2008-04-28  8:46             ` Gabriel Paubert [this message]

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=20080428084630.GA1623@iram.es \
    --to=paubert@iram.es \
    --cc=arndb@de.ibm.com \
    --cc=benh@ozlabs.org \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).