From: Bhavana Nagendra <bnagendr@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: RE: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time
Date: Thu, 13 Jul 2006 09:37:49 -0400 [thread overview]
Message-ID: <44B64CAD.5080804@redhat.com> (raw)
Here are some results without changing frequencies on a system whose
BIOS does not support Power Now! on MP systems:
Basically the system booted up with "nohpet, nopmtimer"i.e. using TSC as
the GTOD time source and system stayed idle for 13 hours. There
appears to be drift of 20 secs in the CPU 2 readings. This TSC drift
will be worse when
the system is active and doing GTOD operations.
CPU 2: Syncing TSC to CPU 0.
CPU 2: synchronized TSC with CPU 0 (last diff -108 cycles, maxerr 826
cycles)
CPU 3: Syncing TSC to CPU 0.
CPU 3: synchronized TSC with CPU 0 (last diff -119 cycles, maxerr 845
cycles)
*** CPUs go offline ***
*** back online ***
CPU 2: Syncing TSC to CPU 0.
CPU 2: synchronized TSC with CPU 0 (last diff -117 cycles, maxerr 846
cycles)
CPU 3: Syncing TSC to CPU 0.
CPU 3: synchronized TSC with CPU 0 (last diff -117 cycles, maxerr 845
cycles)
next reply other threads:[~2006-07-13 13:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 13:37 Bhavana Nagendra [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 16:11 [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time 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-06 20:31 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-12 14:06 ` 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
2006-07-26 18:34 ` Langsdorf, Mark
2006-07-26 18:53 ` Andi Kleen
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=44B64CAD.5080804@redhat.com \
--to=bnagendr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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