From: Jacob Shin <jacob.w.shin@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq & dual core CPUs.
Date: Wed, 31 May 2006 00:05:15 -0500 [thread overview]
Message-ID: <447D240B.6090507@gmail.com> (raw)
In-Reply-To: <20060531045417.GA9439@redhat.com>
Dave Jones wrote:
> On Tue, May 30, 2006 at 09:40:37PM -0700, Pallipadi, Venkatesh wrote:
> yes, sorry for omitting that, though I'm not sure this problem
> is unique to Intel CPUs, though powernow-k8 does seem to have
> some awareness of the cpu_core_map
Yes, powernow-k8 will populate cpufreq_policy->cpus with cpu_core_map[] in order
to communicate to cpufreq driver that the two cores are tied together in freq,
and voltage.
> Looking at that file on my core duo laptop, I see ..
>
> (00:47:47:davej@exile:~)$ cat /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus
> 0
> (00:47:54:davej@exile:~)$ cat /sys/devices/system/cpu/cpu1/cpufreq/affected_cpus
> 1
>
> That implies to me that they're separate cores no?
Are both cores on core-duos tied together? Then why not populate ->cpus with both
of the cores set?
-Jacob Shin
AMD, Inc.
next prev parent reply other threads:[~2006-05-31 5:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 4:40 cpufreq & dual core CPUs Pallipadi, Venkatesh
2006-05-31 4:54 ` Dave Jones
2006-05-31 5:05 ` Jacob Shin [this message]
2006-06-03 4:32 ` Carl Thompson
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 14:10 Pallipadi, Venkatesh
2006-05-31 5:02 Pallipadi, Venkatesh
2006-05-31 5:33 ` Dominik Brodowski
2006-06-23 6:50 ` Dominik Brodowski
2006-05-31 4:26 Dave Jones
2006-05-31 4:59 ` Jacob Shin
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=447D240B.6090507@gmail.com \
--to=jacob.w.shin@gmail.com \
--cc=akpm@osdl.org \
--cc=cpufreq@www.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.