[Bug 58761] related_cpus truncated with acpi-cpufreq driver on kernel 3.9.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=58761





--- Comment #8 from Viresh Kumar <viresh.kumar@xxxxxxxxxx>  2013-05-30 15:14:16 ---
(In reply to comment #7)
> @Viresh Kumar Yes but on my Intel Core i7 processor, all the offline+online
> cores are sharing the same frequency domain, which means they should all appear
> in the related_cpu files.

cpufreq doesn't care how actual hardware clock domains are managed, it just
trusts whatever underlying cpufreq driver has communicated. Because x86 drivers
want cpufreq core to believe that every core has a separate clock, so it is.

It doesn't make any sense what so ever to keep only one cpu in affected_cpus
and all cpus 0-7 in related_cpus as that information isn't used by core.
related cpus comes same as affected cpus in your case because you only have one
core per domain (virtual domain :) ).. But in case you have more cores in a
cluster and few of them are offlined, these two will have different values.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux