From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!
Date: Fri, 22 Aug 2008 02:02:52 +0200 [thread overview]
Message-ID: <200808220202.52853.elendil@planet.nl> (raw)
In-Reply-To: <20080821113141.GB3796@srcf.ucam.org>
On Thursday 21 August 2008, Matthew Garrett wrote:
> On Wed, Aug 20, 2008 at 10:26:45PM +0200, Frans Pop wrote:
> > The only weirdness I can see (only spotted that just now) is that
> > both cores will always seem to be changing frequency together (using
> > ondemand governor), even when 'top' shows one as idle. On my other
> > Core Duo system (an older desktop) the cores react independently.
>
> The cores can't actually be independently scaled.
That makes sense.
> Some older kernels
> would give the impression that they could, but the package itself will
> run at the greater of the defined frequencies.
It does not seem to be kernel related, but processor related.
Here are some results from two different systems (desktop and laptop)
running an _identical_ 2.6.27-rc4 x86_64 kernel.
(The desktop is actually Pentium D, not also Core Duo.)
Desktop
=======
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) D CPU 3.20GHz
stepping : 7
cpu MHz : 2800.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
Samples from /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq:
2800000 2800000
2800000 2800000
2800000 3200000 # Start single busy loop, one core idle
3200000 3200000
2800000 3200000
2800000 3200000
Laptop
======
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU U7700 @ 1.33GHz
stepping : 13
cpu MHz : 1333.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
Samples from /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq:
800000 800000
800000 800000
1333000 1333000 # Start single busy loop, one core idle
1333000 1333000
1333000 1333000
So in the first case frequency changes are reported as if the cores are
independent while in the second case the cores appear linked.
Is a Pentium D really different from a Core Duo in that respect?
prev parent reply other threads:[~2008-08-22 0:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 19:06 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume! Frans Pop
2008-08-20 19:38 ` Rafael J. Wysocki
2008-08-20 20:26 ` Frans Pop
2008-08-20 21:56 ` Rafael J. Wysocki
2008-08-21 9:27 ` Maciej W. Rozycki
2008-08-21 11:18 ` Vegard Nossum
2008-08-21 11:51 ` Maciej W. Rozycki
2008-08-21 12:01 ` Maciej W. Rozycki
2008-08-21 12:20 ` Vegard Nossum
2008-08-21 12:57 ` Maciej W. Rozycki
2008-08-21 13:14 ` Vegard Nossum
2008-08-21 13:15 ` Mikael Pettersson
2008-08-30 19:33 ` Yinghai Lu
2008-08-30 19:16 ` Frans Pop
2008-08-30 20:16 ` Maciej W. Rozycki
2008-09-04 20:18 ` Frans Pop
2008-08-21 11:30 ` Matthew Garrett
2008-08-21 11:31 ` Matthew Garrett
2008-08-22 0:02 ` Frans Pop [this message]
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=200808220202.52853.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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