On Thursday 11 March 2010 09:07 am, John Baldwin wrote:
> On Thursday 11 March 2010 8:43:29 am Alexander Best wrote:
> > since ed@ noticed that there's no CPUID_TO_STEPPING() macro this
> > new patch adds one. i checked and include/specialreg.h is only
> > available on amd64,
>
> i386
>
> > and pc9
On Thursday 11 March 2010 8:43:29 am Alexander Best wrote:
> since ed@ noticed that there's no CPUID_TO_STEPPING() macro this new patch
> adds one. i checked and include/specialreg.h is only available on amd64,
i386
> and pc98. all the latter does however is:
>
> #include
I don't think we need
since ed@ noticed that there's no CPUID_TO_STEPPING() macro this new patch
adds one. i checked and include/specialreg.h is only available on amd64, i386
and pc98. all the latter does however is:
#include
cheers.
alex
Index: amd64/include/specialreg.h
=
On Mon, 1 Mar 2010 19:29, alexbestms@ wrote:
jhell schrieb am 2010-03-01:
On Fri, 26 Feb 2010 22:19, alexbestms@ wrote:
hi there,
i always forget how to decipher model and family from the cpu id.
of course
there're 3rd party tools to do that for you, but instead i decided
to hack the
kerne
Alexander Best writes:
> i also think that on some archs it's not possible to output cpu id,
> stepping, family and model simply because there's no cpu instruction
> (CPUID or something similar) returning those info for freebsd to use.
In many cases it doesn't even make sense, e.g. ARM which is a
jhell schrieb am 2010-03-01:
> On Fri, 26 Feb 2010 22:19, alexbestms@ wrote:
> >hi there,
> >i always forget how to decipher model and family from the cpu id.
> >of course
> >there're 3rd party tools to do that for you, but instead i decided
> >to hack the
> >kernel. ;)
> >maybe somebody finds t
On Friday 26 February 2010 10:19:46 pm Alexander Best wrote:
> hi there,
>
> i always forget how to decipher model and family from the cpu id. of course
> there're 3rd party tools to do that for you, but instead i decided to hack
the
> kernel. ;)
>
> maybe somebody finds these changes useful.
T
Garrett Cooper schrieb am 2010-03-01:
> On Sun, Feb 28, 2010 at 5:43 PM, jhell wrote:
> > On Fri, 26 Feb 2010 22:19, alexbestms@ wrote:
> >> hi there,
> >> i always forget how to decipher model and family from the cpu id.
> >> of
> >> course
> >> there're 3rd party tools to do that for you, but
On Sun, Feb 28, 2010 at 5:43 PM, jhell wrote:
>
> On Fri, 26 Feb 2010 22:19, alexbestms@ wrote:
>>
>> hi there,
>>
>> i always forget how to decipher model and family from the cpu id. of
>> course
>> there're 3rd party tools to do that for you, but instead i decided to hack
>> the
>> kernel. ;)
>>
On Fri, 26 Feb 2010 22:19, alexbestms@ wrote:
hi there,
i always forget how to decipher model and family from the cpu id. of course
there're 3rd party tools to do that for you, but instead i decided to hack the
kernel. ;)
maybe somebody finds these changes useful.
cheers.
alex
What about
On Fri, Feb 26, 2010 at 7:19 PM, Alexander Best wrote:
> hi there,
>
> i always forget how to decipher model and family from the cpu id. of course
> there're 3rd party tools to do that for you, but instead i decided to hack the
> kernel. ;)
>
> maybe somebody finds these changes useful.
I thi
hmm...i guess the person who added the CPUID_TO_* macros to
/usr/include/machine/specialreg.h thought a CPUID_TO_STEPPING macro wasn't
necessary since getting the stepping from cpu_id can be done fairly easy
without any shifting and such.
a CPUID_TO_STEPPING macro would look something like this:
Hello Alexander,
* Alexander Best wrote:
> + printf(" Stepping = %u"
> +" Model = %u"
> +" Family = %u",
> +cpu_id & CPUID_STEPPING,
> +CPUID_TO_MODEL(cpu_id),
> +CPUID_TO_FAMILY(cpu
hi there,
i always forget how to decipher model and family from the cpu id. of course
there're 3rd party tools to do that for you, but instead i decided to hack the
kernel. ;)
maybe somebody finds these changes useful.
cheers.
alex
Index: sys/amd64/amd64/identcpu.c
==
14 matches
Mail list logo