All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.6.7-mm1] perfctr ppc32 update
Date: Tue, 22 Jun 2004 15:21:02 -0500	[thread overview]
Message-ID: <1087935661.1855.10.camel@gaston> (raw)
In-Reply-To: <16600.37372.473221.988885@alkaid.it.uu.se>

On Tue, 2004-06-22 at 15:09, Mikael Pettersson wrote:
> Benjamin Herrenschmidt writes:
>  > Hrm... your code will not work with externally clocked timebases
>  > (like the G5) and I'm not sure you get the core freq. right with
>  > CPU that can do clock slewing or machines that can switch the
>  > core/bus ratio (laptops).
> 
> Do you mean the PLL_CFG code that's been in -mm for the last couple
> of weeks, or just the recently posted update? The update replaced
> in-kernel /proc/cpuinfo parsing (gross) with OF queries taken straight
> from the pmac code in arch/ppc/platform/.
> 
> I'm ignoring 970/G5 until IBM releases the damn documentation.

Well, the G5 can have it's own tb but can also be externally clocked and
that's how Apple does. I'm not sure about all G4 models.

>  > We should rather define an arch API to return those infos...
> 
> No argument there.
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>


  reply	other threads:[~2004-06-22 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 20:14 [PATCH][2.6.7-mm1] perfctr ppc32 update Mikael Pettersson
2004-06-22 18:17 ` Benjamin Herrenschmidt
2004-06-22 20:09   ` Mikael Pettersson
2004-06-22 20:21     ` Benjamin Herrenschmidt [this message]
2004-06-22 20:40       ` Mikael Pettersson
2004-06-22 21:19         ` Benjamin Herrenschmidt
2004-06-22 22:18           ` Mikael Pettersson
2004-06-22 22:14             ` Benjamin Herrenschmidt

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=1087935661.1855.10.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.