All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: "Devriendt, Paul" <paul.devriendt@amd.com>
Cc: cpufreq@ZenII.linux.org.uk
Subject: Re: powernow-k8 problem
Date: Mon, 14 Mar 2005 19:14:58 +0100	[thread overview]
Message-ID: <20050314181458.GI2298@poupinou.org> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A843021DDF84@SAUSEXMB1.amd.com>

On Mon, Mar 14, 2005 at 11:44:53AM -0600, Devriendt, Paul wrote:
> As for having the driver calculate a correction factor based
> on by how much you are overclocking the part ... this is somewhere
> AMD does not want to go. Besides, I am not sure how the driver
> would figure out what the actual speed was versus the reported
> speed. Probably only by calibrating TSC against an external source,
> but if the system is overclocked, what confidence level would I
> have that the external source is true ? It would be bad to penalize
> all in-spec users with excessive delays to support out-of-spec
> users.

Well you are right.  Anyway I am not sure if the system is stable enough
to compile a new kernel ;)

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2005-03-14 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 17:44 powernow-k8 problem Devriendt, Paul
2005-03-14 18:14 ` Bruno Ducrot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-10 20:07 Devriendt, Paul
2005-03-14 12:10 ` Bruno Ducrot
2005-03-04 12:00 red
2005-03-10 16:51 ` Bruno Ducrot
2004-12-01 14:26 Devriendt, Paul
2004-12-01 15:09 ` Markus Trippelsdorf
     [not found] <200411141859.32964.pytasz@lodz.home.pl>
2004-11-14 18:19 ` Michał Pytasz
2004-11-14 16:31 Devriendt, Paul
2004-11-14 11:13 Michał Pytasz

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=20050314181458.GI2298@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@ZenII.linux.org.uk \
    --cc=paul.devriendt@amd.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.