From: Andi Kleen <ak@suse.de>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: "Gulam, Nagib" <nagib.gulam@amd.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
cpufreq@lists.linux.org.uk
Subject: Re: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time
Date: Wed, 26 Jul 2006 18:54:20 +0200 [thread overview]
Message-ID: <200607261854.20670.ak@suse.de> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84303218F04@SAUSEXMB1.amd.com>
> AMD Opteron(tm) Processor 838 stepping 01
> CPU 3: Syncing TSC to CPU 0.
> CPU 3: synchronized TSC with CPU 0 (last diff -109 cycles, maxerr 1024
Hmm, indeed - i would have expected higher max errors too.
It should have worked in theory. No explanation currently.
> cycles)
> powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x6
> powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x8
> powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
> powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
>
> Is there a better test we can be using?
I don't know of any. Ok I guess it would be possible to write
something in user space, but it would likely look similar to
the algorithm the kernel uses.
-Andi
next prev parent reply other threads:[~2006-07-26 16:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 20:31 [PATCH] Allow all Opteron processors to change pstate at same time Mark Langsdorf
2006-07-07 12:10 ` Andi Kleen
2006-07-07 17:36 ` [discuss] " Langsdorf, Mark
2006-07-10 12:45 ` Joachim Deguara
2006-07-10 13:02 ` Joachim Deguara
2006-07-11 12:55 ` Joachim Deguara
2006-07-11 13:07 ` Andi Kleen
2006-07-11 13:14 ` Arjan van de Ven
2006-07-11 16:15 ` Alan Cox
2006-07-11 16:01 ` Arjan van de Ven
2006-07-11 16:04 ` Andi Kleen
2006-07-11 13:31 ` Langsdorf, Mark
2006-07-11 13:34 ` Arjan van de Ven
2006-07-11 13:51 ` Andi Kleen
2006-07-11 13:14 ` [OT] Evolution use (was: Re: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time) Xavier Bestel
2006-07-12 14:06 ` [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time Joachim Deguara
2006-07-12 14:54 ` Andi Kleen
2006-07-25 21:47 ` Langsdorf, Mark
2006-07-26 11:31 ` Joachim Deguara
2006-07-26 16:42 ` Langsdorf, Mark
2006-07-26 16:54 ` Andi Kleen [this message]
2006-07-26 18:34 ` Langsdorf, Mark
2006-07-26 18:53 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 16:11 shin, jacob
2006-07-12 16:14 ` Langsdorf, Mark
2006-07-13 13:06 ` Pavel Machek
2006-07-13 14:32 ` Joachim Deguara
2006-07-16 1:56 ` Pavel Machek
2006-07-17 7:37 ` Joachim Deguara
2006-07-20 15:59 ` Pavel Machek
2006-07-13 13:37 Bhavana Nagendra
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=200607261854.20670.ak@suse.de \
--to=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=nagib.gulam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox