From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>, Borislav Petkov <bp@amd64.org>,
linux-kernel@vger.kernel.org, kay.sievers@vrfy.org,
trenn@suse.de, Andi Kleen <ak@linux.intel.com>,
davej@redhat.com
Subject: Re: [PATCH 07/10] cpufreq: Add support for x86 cpuinfo auto loading
Date: Fri, 16 Dec 2011 03:12:54 +0100 [thread overview]
Message-ID: <20111216021254.GG14839@one.firstfloor.org> (raw)
In-Reply-To: <4EEA9CB2.9020709@zytor.com>
On Thu, Dec 15, 2011 at 05:19:46PM -0800, H. Peter Anvin wrote:
> On 12/08/2011 06:37 AM, Andi Kleen wrote:
> >> Well, there is CPUID_8000_0007_EDX[7] which denotes the presence
> >> of the P-state registers. It probably could be added to
> >> init_scattered_cpuid_features() but there's still special handling
> >> needed for K8.
> >
> > Dave is probably right that it's not worth moving the list.
> >
> >> Can you do both a family and a feature bit test with the autoprobing
> >> code?
> >
>
> Another similar question: is it possible to key a load on more than one
> CPU feature? It's fairly common that you need more than one feature for
> a specific piece of code to function, and it would be good to be able to
> represent it.
Right now it's not possible. The driver just errors out if it can't
find some additional capability.
I considered it originally, but all the cases I looked at were quite
obscure (unlikely to happen) so I opted for this simpler setup.
-Andi
next prev parent reply other threads:[~2011-12-16 2:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 0:41 Updated cpu module autoprobing patchkit Andi Kleen
2011-12-08 0:41 ` [PATCH 01/10] Add driver auto probing for x86 features Andi Kleen
2011-12-08 1:57 ` H. Peter Anvin
2011-12-08 9:35 ` Jean Delvare
2011-12-08 14:45 ` Andi Kleen
2011-12-09 20:16 ` Jean Delvare
2011-12-09 20:24 ` Andi Kleen
2011-12-09 20:28 ` Jean Delvare
2011-12-16 1:25 ` H. Peter Anvin
2011-12-08 0:41 ` [PATCH 02/10] crypto: Add support for x86 cpuid auto loading for x86 crypto drivers Andi Kleen
2011-12-08 0:41 ` [PATCH 03/10] intel-idle: convert to x86_cpu_id auto probing Andi Kleen
2011-12-08 0:41 ` [PATCH 04/10] ACPI: Load acpi-cpufreq from processor driver automatically Andi Kleen
2011-12-08 0:41 ` [PATCH 05/10] HWMON: Convert via-cputemp to x86 cpuid autoprobing Andi Kleen
2011-12-08 10:51 ` Jean Delvare
2011-12-08 0:41 ` [PATCH 06/10] HWMON: Convert coretemp " Andi Kleen
2011-12-08 2:40 ` Guenter Roeck
2011-12-08 7:24 ` Jean Delvare
2011-12-08 16:09 ` Guenter Roeck
2011-12-08 16:13 ` Jean Delvare
2011-12-08 20:58 ` Andi Kleen
2011-12-08 14:35 ` Andi Kleen
2011-12-08 0:41 ` [PATCH 07/10] cpufreq: Add support for x86 cpuinfo auto loading Andi Kleen
2011-12-08 1:07 ` Dave Jones
2011-12-08 1:13 ` Andi Kleen
2011-12-08 1:24 ` Dave Jones
2011-12-08 4:01 ` Andi Kleen
2011-12-08 8:49 ` Borislav Petkov
2011-12-08 14:37 ` Andi Kleen
2011-12-16 1:19 ` H. Peter Anvin
2011-12-16 2:12 ` Andi Kleen [this message]
2011-12-08 0:41 ` [PATCH 08/10] x86: autoload microcode driver on Intel and AMD systems Andi Kleen
2011-12-08 0:41 ` [PATCH 09/10] x86: Add a test module for cpu loading Andi Kleen
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=20111216021254.GG14839@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=bp@amd64.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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