From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58761] related_cpus truncated with acpi-cpufreq driver on kernel 3.9.3
Date: Wed, 29 May 2013 15:26:03 +0000 (UTC) [thread overview]
Message-ID: <20130529152603.C67CC11FACF@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-58761-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=58761
--- Comment #2 from Jean-Philippe Halimi <jean-philippe.halimi@exascale-computing.eu> 2013-05-29 15:26:03 ---
@Viresh Kumar: Alright, I get this. But my Intel(R) Core(TM) i7-3770 CPU @
3.40GHz (Ivy Bridge) cpu does have threads that share clock frequency domain.
Here are the results any older version (from 3.2.0 at least) of the kernel have
:
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus: 0 1 2 3 4 5 6 7
Which means : Any thread within this set of threads physically apply the same
frequency.
In the 3.9.3 kernel version, I don't have this result anymore (see my previous
post), and I doubt the Linux kernel has changed any physical property of my
processor.
According to what you said in your post, is "shared clock line" different from
"shared frequency domain" ?
Thank you for your time
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-29 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-58761-12968@https.bugzilla.kernel.org/>
2013-05-29 1:03 ` [Bug 58761] related_cpus truncated with acpi-cpufreq driver on kernel 3.9.3 bugzilla-daemon
2013-05-29 6:07 ` bugzilla-daemon
2013-05-29 15:26 ` bugzilla-daemon [this message]
2013-05-29 15:48 ` bugzilla-daemon
2013-05-29 15:51 ` bugzilla-daemon
2013-05-29 16:09 ` bugzilla-daemon
2013-05-30 15:05 ` bugzilla-daemon
2013-05-30 15:09 ` bugzilla-daemon
2013-05-30 15:14 ` bugzilla-daemon
2013-05-30 15:44 ` bugzilla-daemon
2013-05-30 15:53 ` bugzilla-daemon
2013-05-30 16:00 ` bugzilla-daemon
2013-05-30 16:05 ` bugzilla-daemon
2013-05-30 16:28 ` bugzilla-daemon
2013-05-30 16:51 ` bugzilla-daemon
2013-05-30 17:37 ` bugzilla-daemon
2013-05-30 20:00 ` bugzilla-daemon
2013-06-19 6:48 ` bugzilla-daemon
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=20130529152603.C67CC11FACF@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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 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.