From: Andi Kleen <ak@suse.de>
To: "shin, jacob" <jacob.shin@amd.com>
Cc: cpufreq@lists.linux.org.uk, davej@redhat.com, "Langsdorf,
Mark" <mark.langsdorf@amd.com>
Subject: Re: [PATCH] [1/2] cpufreq: Fix handling for CPU hotplug
Date: Tue, 28 Feb 2006 13:15:52 +0100 [thread overview]
Message-ID: <200602281315.53204.ak@suse.de> (raw)
In-Reply-To: <B3870AD84389624BAF87A3C7B831499302935655@SAUSEXMB2.amd.com>
On Tuesday 28 February 2006 02:54, shin, jacob wrote:
> powernow-k8: Let cpufreq driver handle affected CPUs
>
> Let the cpufreq driver manage AMD Dual-Core CPUs being tied together.
>
> Since cpufreq driver's affected CPUs data, cpufreq_policy->cpus, already
> knows about which cores are tied together, powernow driver does not have
> keep its internal data for every core. (even a pointer.. it will never
> be called on) Telling cpufreq driver about cpu_core_map at init time is
> sufficient.
Nice - it even simplifies the code. And makes sense.
How much regression testing did you do? Is it well tested enough for 2.6.16?
-Andi
next prev parent reply other threads:[~2006-02-28 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 1:54 [PATCH] [1/2] cpufreq: Fix handling for CPU hotplug shin, jacob
2006-02-28 12:15 ` Andi Kleen [this message]
2006-02-28 16:22 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 15:33 shin, jacob
2006-02-28 16:41 shin, jacob
2006-02-28 16:50 shin, jacob
2006-02-28 16:54 shin, jacob
2006-02-28 17:36 shin, jacob
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=200602281315.53204.ak@suse.de \
--to=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=jacob.shin@amd.com \
--cc=mark.langsdorf@amd.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