cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: "Brown, Len" <len.brown@intel.com>, Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: [PATCH 6/8] acpi-cpufreq: use cpu_core_map on multicore processors
Date: Mon, 31 Jul 2006 22:53:45 +0400	[thread overview]
Message-ID: <44CE51B9.3060906@linux.intel.com> (raw)

 acpi-cpufreq.c |   11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

on some new systems “shared_cpu_map” from ACPI is wrong, so   “cpu_core_map” structure is used to define right “policy->cpus” group.

Signed-off: Denis Sadykov <denis.m.sadykov@intel.com>
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi at intel.com>
Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy at intel.com>

Index: linux-2.6.17/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
===================================================================
--- linux-2.6.17.orig/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c	2006-07-17 17:09:27.000000000 +0000
+++ linux-2.6.17/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c	2006-07-17 17:11:07.000000000 +0000
@@ -542,7 +542,16 @@
 		}
 	}
 
-	policy->cpus = data->acpi_data->shared_cpu_map;
+/*	policy->cpus = data->acpi_data->shared_cpu_map; */
+/* NOTE TODO:
+	Actually we must use "shared_cpu_map" from acpi data to define policy->cpus,
+	but on some new systems "shared_cpu_map" is wrong. So we use "cpu_core_map"
+	sructure temporarily. Should be return back. */
+#ifdef CONFIG_SMP
+	policy->cpus = cpu_core_map[cpu];
+#else
+	policy->cpus = cpumask_of_cpu(cpu);
+#endif /* CONFIG_SMP */
 	for_each_cpu_mask(i, policy->cpus) {
 		drv_data[i] = data;
 	}

             reply	other threads:[~2006-07-31 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 18:53 Alexey Starikovskiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 21:05 [PATCH 6/8] acpi-cpufreq: use cpu_core_map on multicore processors Pallipadi, Venkatesh
2006-08-03 21:08 ` Alexey Starikovskiy

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=44CE51B9.3060906@linux.intel.com \
    --to=alexey_y_starikovskiy@linux.intel.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=len.brown@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox