All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Don't use regs to obtain FSB frequency
Date: Thu, 14 Dec 2006 00:22:48 +0100	[thread overview]
Message-ID: <45808B48.9060103@interia.pl> (raw)
In-Reply-To: <20061213225009.GL2418@redhat.com>

> On Wed, Dec 13, 2006 at 11:38:18PM +0100, Rafa³ Bilski wrote:
>  > Current code has a problem with FSB on "PowerSaver 1.0" 
>  > CPU. FSB is incorrecly guessed (again) for mini PC by Ebox. 
>  > There is 8x100MHz CPU with "Nehemiah" core. It is reported 
>  > as 8x133MHz. Apparently Longhaul MSR isn't reliable source 
>  > of information if it is RevisionID == 0 for anything else 
>  > then max multiplier. We can't read 200MHz FSB from it nor 
>  > from EBLCR_POWER_ON too. This driver is working only with 
>  > multipliers. FSB frequency is only needed to calculate CPU 
>  > f for Cpufreq core. At boot kernel is calculating processor 
>  > frequency. We know the multiplier. In this way we have bus 
>  > frequency with kHz precision.
> 
> I'm puzzled.  This description talks exclusively about Nehemiah,
> and yet it's making changes to code only run by the pre-Nehemiah cores.
> This makes me especially nervous as those chips don't get a
> great deal of testing any more, and we typically learn that we
> broke them months after making changes.
Well. I don't see a reason for not making this change. It is even more 
compatible with older CPU's, because EBL_CR_POWERON is returning current 
multiplier. And according to Your comments in source it isn't good to 
depend on EBL_CR_POWERON for "PowerSaver" CPU's. Why guess FSB if 
kernel calculated it at boot? In this way it is much simplier. Only 
possible bug is for "PowerSaver" processor running at lower multiplier 
then max.
My point is: can't use EBL_CR_POWERON FSB bits, nor Longhaul MSR FSB bits, 
for "Powersaver" - don't use it at all for any CPU. Find the way that will 
work for all of them.
> Has this been tested on anything other than the system mentioned above?
> It seems like huge potential for regressions here, due to the size
> and impact of the changes.
It has been tested on my Epia M-10000, system mentioned above and two 
Epia SP-13000. I'm currently exchanging e-mails with user who has 
Ezra with "Longhaul ver. 2" connected to SIS630 chipset. Version 2 seems 
to have only max BR bits - same as "Powersaver 1.0". I was planing to use 
same code for V2. I'm not sure yet if Longhaul version 2 can use ACPI C3 
to change frequency.
> 
> 		Dave
Rafa³


----------------------------------------------------------------------
smieszne, muzyka, pilka, sexy, kibice, kino, ciekawe, extreme, kabaret
http://link.interia.pl/f19d4 - najlepsze filmy w intermecie

  reply	other threads:[~2006-12-13 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 22:38 [PATCH] Longhaul - Don't use regs to obtain FSB frequency Rafał Bilski
2006-12-13 22:50 ` Dave Jones
2006-12-13 23:22   ` Rafał Bilski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-13 22:28 Rafał Bilski
2006-12-03 16:17 Rafał Bilski

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=45808B48.9060103@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    /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.