From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Robert Richter <robert.richter@amd.com>,
Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 3/10 -tip] x86: Add cpufeatures for Advanced Power Management
Date: Wed, 20 May 2009 12:45:35 +0530 [thread overview]
Message-ID: <1242803735.3260.44.camel@localhost.localdomain> (raw)
In-Reply-To: <4A12E122.1020009@kernel.org>
On Tue, 2009-05-19 at 09:41 -0700, H. Peter Anvin wrote:
> Jaswinder Singh Rajput wrote:
> >
> > Peter, Ingo:
> > Do you think we need to arrange x86_capability in some order, currently
> > we are using x86_capability numbering in random order.
> >
>
> No.
>
I think better I will show with the coding to get the clear picture.
Currently we are using hardcoded x86_capability as [0], [2], [4], [5].
Thomas prefer to use constant so may be we can define current system as:
enum {
CPUID_0000_0001_EDX = 0, /* 0x00000001 edx */
CPUID_8000_0001_EDX, /* 0x80000001 edx */
CPUID_8086_0001_EDX, /* 0x80860001 edx */
CPUID_SOFT_MISC1, /* Software Misc1 */
CPUID_0000_0001_ECX, /* 0x00000001 ecx */
CPUID_C000_0001_EDX, /* 0xC0000001 edx */
CPUID_8000_0001_ECX, /* 0x80000001 ecx */
CPUID_SOFT_MISC2, /* Software Misc2 */
CPUID_SOFT_VIRTUAL, /* Software Virtualization */
};
I was suggesting to also sort it out based on address and register like this:
enum {
/* Hardware CPUIDs */
CPUID_0000_0001_ECX = 0, /* 0x00000001 ecx */
CPUID_0000_0001_EDX, /* 0x00000001 edx */
CPUID_8000_0001_ECX, /* 0x80000001 ecx */
CPUID_8000_0001_EDX, /* 0x80000001 edx */
CPUID_8086_0001_EDX, /* 0x80860001 edx */
CPUID_C000_0001_EDX, /* 0xC0000001 edx */
/* Software/Miscellaneous CPUIDs */
CPUID_SOFT_MISC1, /* Software Misc1 */
CPUID_SOFT_MISC2, /* Software Misc2 */
CPUID_SOFT_VIRTUAL, /* Software Virtualization */
};
Do you have some better suggestion.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-05-20 7:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:35 [git-pull -tip][PATCH 0/10] few cpufeature additions and users Jaswinder Singh Rajput
2009-05-12 15:37 ` [PATCH 1/10 -tip] x86: Add cpufeature for Processor Name Jaswinder Singh Rajput
2009-05-12 15:38 ` [PATCH 2/10 -tip] x86: get_model_name() user of X86_FEATURE_PNAME Jaswinder Singh Rajput
2009-05-12 15:39 ` [PATCH 3/10 -tip] x86: Add cpufeatures for Advanced Power Management Jaswinder Singh Rajput
2009-05-12 15:40 ` [PATCH 4/10 -tip] x86: check_powernow() for K7 user of Advanced Power Management features Jaswinder Singh Rajput
2009-05-12 15:40 ` [PATCH 5/10 -tip] x86: check_powernow() for K8 and later " Jaswinder Singh Rajput
2009-05-12 15:41 ` [PATCH 6/10 -tip] x86: early_init_intel() " Jaswinder Singh Rajput
2009-05-12 15:42 ` [PATCH 7/10 -tip] x86: early_init_amd() " Jaswinder Singh Rajput
2009-05-12 15:43 ` [PATCH 8/10 -tip] x86: Add cpufeature for Microcode update Jaswinder Singh Rajput
2009-05-12 15:44 ` [PATCH 9/10 -tip] x86: collect_cpu_info() of Intel user of Microcode feature Jaswinder Singh Rajput
2009-05-12 15:44 ` [PATCH 10/10 -tip] x86: collect_cpu_info() of AMD " Jaswinder Singh Rajput
2009-05-13 5:47 ` Andreas Herrmann
2009-05-13 7:20 ` Jaswinder Singh Rajput
2009-05-13 5:46 ` [PATCH 8/10 -tip] x86: Add cpufeature for Microcode update Andreas Herrmann
2009-05-13 7:18 ` Jaswinder Singh Rajput
2009-05-13 6:18 ` [PATCH 6/10 -tip] x86: early_init_intel() user of Advanced Power Management features Andreas Herrmann
2009-05-13 7:20 ` Jaswinder Singh Rajput
2009-05-12 17:48 ` [PATCH 5/10 -tip] x86: check_powernow() for K8 and later " Ingo Molnar
2009-05-12 18:45 ` Jaswinder Singh Rajput
2009-05-13 6:36 ` Andreas Herrmann
2009-05-12 19:07 ` [PATCH 4/10 -tip] x86: check_powernow() for K7 " Jaswinder Singh Rajput
2009-05-12 19:06 ` [PATCH 3/10 -tip] x86: Add cpufeatures for Advanced Power Management Jaswinder Singh Rajput
2009-05-12 21:04 ` Thomas Gleixner
2009-05-13 8:57 ` Jaswinder Singh Rajput
2009-05-15 13:47 ` Jaswinder Singh Rajput
2009-05-17 12:17 ` Thomas Gleixner
2009-05-17 14:18 ` Jaswinder Singh Rajput
2009-05-19 15:01 ` Jaswinder Singh Rajput
2009-05-19 16:41 ` H. Peter Anvin
2009-05-20 7:15 ` Jaswinder Singh Rajput [this message]
2009-05-20 7:23 ` Jaswinder Singh Rajput
2009-05-20 18:30 ` H. Peter Anvin
2009-05-21 5:09 ` Jaswinder Singh Rajput
2009-05-13 6:27 ` Andreas Herrmann
2009-05-21 6:14 ` H. Peter Anvin
2009-05-21 6:11 ` [PATCH 1/10 -tip] x86: Add cpufeature for Processor Name H. Peter Anvin
2009-05-21 7:38 ` Jaswinder Singh Rajput
2009-05-21 20:09 ` H. Peter Anvin
2009-05-12 20:15 ` [git-pull -tip][PATCH 0/10] few cpufeature additions and users Jaswinder Singh Rajput
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=1242803735.3260.44.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=davej@redhat.com \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).