Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-06 Thread Peter Humphrey
On Wednesday 05 March 2008 18:08:33 Neil Bothwick wrote:

 Run lshw and look at the width value for the CPU.

I'd forgotten about lshw - thanks for the reminder.

At the risk of a thread hijack, what should I do about this, which is shown 
for both CPU's:

*-cache:2 DISABLED

Does that mean the hardware feature is unavailable in these Opteron 246s, or 
that I've overlooked a kernel config parameter? I don't remember any 
motherboard jumpers for it.

-- 
Rgds
Peter
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Stratos Psomadakis

O/H Alan McKinnon έγραψε:

Hi all,

Sometime in the last month someone posted (in a thread that went wildly 
OT) a definite way to determine if an Intel cpu is 32 or 64 bit. 
Unfortunately I can't find the post anymore.


It involved checking the cpu-family, model and flags fields in cpuinfo.

Could that same kind soul please repost the info? And if possible the 
same for AMD? 



  

gentoo-wiki's article about safe cflags has the information you want...
http://gentoo-wiki.com/Safe_Cflags

for pentium4, the ones with the prescott core are 64bit...
at /proc/cpuinfo you should see with a prescott:
cpu_family:15
model : 3 or 4

you could also look for the pni cpuflag...

--
Stratos Psomadakis
[EMAIL PROTECTED]




signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread kashani

Alan McKinnon wrote:

Hi all,

Sometime in the last month someone posted (in a thread that went wildly 
OT) a definite way to determine if an Intel cpu is 32 or 64 bit. 
Unfortunately I can't find the post anymore.


It involved checking the cpu-family, model and flags fields in cpuinfo.

Could that same kind soul please repost the info? And if possible the 
same for AMD? 





cat /proc/cpuinfo and look for lm, which stands for long mode, under the 
flags. I'm pretty sure that works for Intel and AMD.


kashani
--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread cypherstrong
another way to test is to run a livecd in amd64 mode on new intel chips
if it doesn't work, try the ia64 version

if it doesn't work ... your intel is a 32 bits version :)



Le Wednesday 05 March 2008 16:47:10 kashani, vous avez écrit :
 Alan McKinnon wrote:
  Hi all,
 
  Sometime in the last month someone posted (in a thread that went wildly
  OT) a definite way to determine if an Intel cpu is 32 or 64 bit.
  Unfortunately I can't find the post anymore.
 
  It involved checking the cpu-family, model and flags fields in cpuinfo.
 
  Could that same kind soul please repost the info? And if possible the
  same for AMD?

 cat /proc/cpuinfo and look for lm, which stands for long mode, under the
 flags. I'm pretty sure that works for Intel and AMD.

 kashani




signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Chris Brennan

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Here is the output of my cpuinfo, I'll point out where it will mean
64bit. For the sake of this demonstration, I have only pasted one (1) CPU.

[EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 15
model   : 75
model name  : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ -- Here
will be your first indication. 64 bit processors, weather they are
SPARC, AMD or intel, must identify themselves clearly in the model name
field.
stepping: 2
cpu MHz : 1000.000 -- forgive this, my cpu's are idle at the moment
and speedstep droped me down for the moment.
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2 -- If you are a multi-core CPU, this will tell you how
many cores per processor. All cores are identical, so if you have a
64-bit Dual/Quad-Core CPU, then all cores are 64bit.
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic
cr8_legacy -- you can look for flags that may give away 64bit, such as
lahf_lm, lm and nx.
bogomips: 2010.67
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc


For reference, this is a good read talking about 64 Bit processors and
how to identify them. http://en.wikipedia.org/wiki/X86-64

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHzswf8hUIAnGfls4RArR2AJ9X+BYt338vuPAK6Pa0Lmcbtp6GLgCcDAn4
QaXGbnhOKYx2PMKhVBpu5I8=
=9QKB
-END PGP SIGNATURE-
--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Stratos Psomadakis

O/H cypherstrong έγραψε:

another way to test is to run a livecd in amd64 mode on new intel chips
if it doesn't work, try the ia64 version

if it doesn't work ... your intel is a 32 bits version :)
  

no need for the ia64...
it's for intel's itanium cpus...
ia64 is not compatible with x86...

if he had an itanium machine, he would definitely know it...

--
Stratos Psomadakis
[EMAIL PROTECTED]




signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread cypherstrong
Of course :)

the test for amd64 could be fast with a livecd ... or with cpuinfo and good 
knowledge of flags

Le Wednesday 05 March 2008 17:45:16 Stratos Psomadakis, vous avez écrit :
 O/H cypherstrong έγραψε:
  another way to test is to run a livecd in amd64 mode on new intel chips
  if it doesn't work, try the ia64 version
 
  if it doesn't work ... your intel is a 32 bits version :)

 no need for the ia64...
 it's for intel's itanium cpus...
 ia64 is not compatible with x86...

 if he had an itanium machine, he would definitely know it...




signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Andrew MacKenzie
+++ Chris Brennan [gentoo-user] [Wed, Mar 05, 2008 at 11:36:47AM -0500]:
 Here is the output of my cpuinfo, I'll point out where it will mean
 64bit. For the sake of this demonstration, I have only pasted one (1) CPU.
 
 [EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
 processor : 0
 vendor_id : AuthenticAMD
 cpu family: 15
 model : 75
 model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ -- Here
 will be your first indication. 64 bit processors, weather they are
 SPARC, AMD or intel, must identify themselves clearly in the model name
 field.
They do identify themselves, but they may not indicate 64 vs. 32 bit.  

From my Core2 running 64-bit:
processor   : 3
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Core(TM)2 Quad CPUQ6600  @ 2.40GHz
stepping: 11
cpu MHz : 2400.000
cache size  : 4096 KB
physical id : 0
siblings: 4
core id : 3
cpu cores   : 4
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr lahf_lm
bogomips: 4799.96
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:


-- 
// Andrew MacKenzie  |  http://www.edespot.com
// GPG public key: http://www.edespot.com/~amackenz/public.key
// You will remember, Watson, how the dreadful business of the
// Abernetty family was first brought to my notice by the depth which the
// parsley had sunk into the butter upon a hot day.
// -- Sherlock Holmes


pgpZMoR2s4YHf.pgp
Description: PGP signature


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Ricardo Saffi Marques
On 3/5/08, Andrew MacKenzie [EMAIL PROTECTED] wrote:

 They do identify themselves, but they may not indicate 64 vs. 32 bit.


Something one can always do is cat /proc/cpuinfo and then check the family
and model at http://gentoo-wiki.com/Safe_Cflags .
If it indicates 64-bit profile and Cflags for it, then it is a 64-bit
capable processor. :-)

-- 
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Uwe Thiem
On Wednesday 05 March 2008, Chris Brennan wrote:
 Here is the output of my cpuinfo, I'll point out where it will mean
 64bit. For the sake of this demonstration, I have only pasted one
 (1) CPU.

 [EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
 processor : 0
 vendor_id : AuthenticAMD
 cpu family: 15
 model : 75
 model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ --
 Here will be your first indication. 64 bit processors, weather they
 are SPARC, AMD or intel, must identify themselves clearly in the
 model name field.
 stepping  : 2
 cpu MHz   : 1000.000 -- forgive this, my cpu's are idle at the
 moment and speedstep droped me down for the moment.
 cache size: 512 KB
 physical id   : 0
 siblings  : 2
 core id   : 0
 cpu cores : 2 -- If you are a multi-core CPU, this will tell you
 how many cores per processor. All cores are identical, so if you
 have a 64-bit Dual/Quad-Core CPU, then all cores are 64bit.
 fpu   : yes
 fpu_exception : yes
 cpuid level   : 1
 wp: yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
 cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
 fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm
 cmp_legacy svm extapic cr8_legacy -- you can look for flags that
 may give away 64bit, such as lahf_lm, lm and nx.
 bogomips  : 2010.67
 TLB size  : 1024 4K pages
 clflush size  : 64
 cache_alignment   : 64
 address sizes : 40 bits physical, 48 bits virtual
 power management: ts fid vid ttp tm stc

I am a bit confused now. I always thought my CPU was 32bit. Here are 
the relevant two lines from my /proc/cpuinfo:

model name  : Intel(R) Pentium(R) 4 CPU 3.00GHz
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx 
lm constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl cid cx16 xtpr 
lahf_lm

So the model name does not indicate anything 64bit while the flags 
contain lm, nx and lahf_lm.

What gives?

Uwe

-- 
Informal Linux Group Namibia:
http://www.linux.org.na/
SysEx (Pty) Ltd.:
http://www.SysEx.com.na/
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Ricardo Saffi Marques
On 3/5/08, Uwe Thiem [EMAIL PROTECTED] wrote:

 I am a bit confused now. I always thought my CPU was 32bit. Here are
 the relevant two lines from my /proc/cpuinfo:
 So the model name does not indicate anything 64bit while the flags
 contain lm, nx and lahf_lm.


Like I said, take the family and model and check Gentoo Safe Cflags website.

-- 
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Alan McKinnon
On Wednesday 05 March 2008, Stratos Psomadakis wrote:
 O/H cypherstrong έγραψε:
  another way to test is to run a livecd in amd64 mode on new intel
  chips if it doesn't work, try the ia64 version
 
  if it doesn't work ... your intel is a 32 bits version :)

 no need for the ia64...
 it's for intel's itanium cpus...
 ia64 is not compatible with x86...

 if he had an itanium machine, he would definitely know it...

More like the accountant would definitely know it. I might still have a 
lingering doubt :-)

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Alan McKinnon
On Wednesday 05 March 2008, cypherstrong wrote:
 Of course :)

 the test for amd64 could be fast with a livecd 

That might suit someone who's sitting with a new and unknown box on the 
desk in front of them. I usually have to discover this for machines 
that are in some unknown location and to which I only have ssh access.

Rebooting is most certainly not an option, even if i could get a CD into 
them. If I do that, the SLA kicks in and that will bankrupt the 
company...

 ... or with cpuinfo 
 and good knowledge of flags

The combination of what flags does what and which model number is which 
actual cpu product is much much more complex than I ever thought :-)


-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Chris Brennan

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Stratos Psomadakis wrote:
| O/H cypherstrong έγραψε:
| another way to test is to run a livecd in amd64 mode on new intel chips
| if it doesn't work, try the ia64 version
|
| if it doesn't work ... your intel is a 32 bits version :)
|   
| no need for the ia64...

| it's for intel's itanium cpus...
| ia64 is not compatible with x86...
|
| if he had an itanium machine, he would definitely know it...
|

indeed ...
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHztg78hUIAnGfls4RApxNAJ9Z2g0kBxZ7SZk4s7rhVKdBWxOSzgCgguz8
lbSGfmbmxDQhK8OLylVy/HE=
=eMlf
-END PGP SIGNATURE-

--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Neil Bothwick
On Wed, 5 Mar 2008 15:23:55 +0200, Alan McKinnon wrote:

 Could that same kind soul please repost the info? And if possible the 
 same for AMD? 

Run lshw and look at the width value for the CPU.


-- 
Neil Bothwick

If all the world is a stage, where is the audience sitting?


signature.asc
Description: PGP signature


Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Alan McKinnon
On Wednesday 05 March 2008, Neil Bothwick wrote:
 On Wed, 5 Mar 2008 15:23:55 +0200, Alan McKinnon wrote:
  Could that same kind soul please repost the info? And if possible
  the same for AMD?

 Run lshw and look at the width value for the CPU.

Aaaahhh. That has to be the most useful app I've emerged in at 
least 2 months :-)

Very very useful, thanks Neil

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Chris Brennan
from what you pasted, you have a 32bit cpu. But you have a flag I do as 
well, and that is 'ht'. Hyper-Threading is a whole different beast I 
know very little about, it's more of an Intel thing for there first 
generation dual-core cpu's.


Uwe Thiem wrote:

On Wednesday 05 March 2008, Chris Brennan wrote:

Here is the output of my cpuinfo, I'll point out where it will mean
64bit. For the sake of this demonstration, I have only pasted one
(1) CPU.

[EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 15
model   : 75
model name  : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ --
Here will be your first indication. 64 bit processors, weather they
are SPARC, AMD or intel, must identify themselves clearly in the
model name field.
stepping: 2
cpu MHz : 1000.000 -- forgive this, my cpu's are idle at the
moment and speedstep droped me down for the moment.
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2 -- If you are a multi-core CPU, this will tell you
how many cores per processor. All cores are identical, so if you
have a 64-bit Dual/Quad-Core CPU, then all cores are 64bit.
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm
cmp_legacy svm extapic cr8_legacy -- you can look for flags that
may give away 64bit, such as lahf_lm, lm and nx.
bogomips: 2010.67
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc


I am a bit confused now. I always thought my CPU was 32bit. Here are 
the relevant two lines from my /proc/cpuinfo:


model name  : Intel(R) Pentium(R) 4 CPU 3.00GHz
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx 
lm constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl cid cx16 xtpr 
lahf_lm


So the model name does not indicate anything 64bit while the flags 
contain lm, nx and lahf_lm.


What gives?

Uwe


--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Alan McKinnon
On Wednesday 05 March 2008, Chris Brennan wrote:
 Here is the output of my cpuinfo, I'll point out where it will mean
 64bit. For the sake of this demonstration, I have only pasted one (1)
 CPU.

 model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ -- Here
 will be your first indication. 64 bit processors, weather they are
 SPARC, AMD or intel, must identify themselves clearly in the model
 name field.

In my case must equates to should. but doesn't
The box on my desk identifies the cpu as Pentium4. But it's running 64 
bit SLES, so something got omitted on the chip

 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
 cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
 fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm
 cmp_legacy svm extapic cr8_legacy -- you can look for flags that may
 give away 64bit, such as lahf_lm, lm and nx.

Is there a list somewhere of which flags are definitely 64 bit 
capabilities only, and which might be found on 32 bit chips?

It would not surprise me if a manufacturer announced they had 
implemented ssse3 on 32 bit silicon for example

 address sizes : 40 bits physical, 48 bits virtual

How about this? Current amd64 implements 48 bit addressing, how wide is 
it for 32 bit? OTOH my Core2 Duo notebook does not have this field at 
all

 For reference, this is a good read talking about 64 Bit processors
 and how to identify them. http://en.wikipedia.org/wiki/X86-64

I see it's vastly more complex than I ever imagined. Thanks for the link 
though, learned a lot!

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Alan McKinnon
On Wednesday 05 March 2008, Chris Brennan wrote:
 from what you pasted, you have a 32bit cpu. But you have a flag I do
 as well, and that is 'ht'. Hyper-Threading is a whole different beast
 I know very little about, it's more of an Intel thing for there first
 generation dual-core cpu's.

HT is an abomination that should not be suffered to live. It's Intel's 
attempt to implement application level threading in silicon and it 
simply does not work in practice.

I've yet to benchmark any reasonably complex app that runs better with 
hyper-threading enabled. In fact when I still worked support at a 
certain database vendor we simply refused to support any of our apps 
running on machines where HT was enabled.

Note that it wasn't you should not do this, it was go away and phone 
back when you have rebooted with sane kernel options :-)

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Detecting 64 bit Intel chips

2008-03-05 Thread Chris Brennan

well said ...

Alan McKinnon wrote:

On Wednesday 05 March 2008, Chris Brennan wrote:

from what you pasted, you have a 32bit cpu. But you have a flag I do
as well, and that is 'ht'. Hyper-Threading is a whole different beast
I know very little about, it's more of an Intel thing for there first
generation dual-core cpu's.


HT is an abomination that should not be suffered to live. It's Intel's 
attempt to implement application level threading in silicon and it 
simply does not work in practice.


I've yet to benchmark any reasonably complex app that runs better with 
hyper-threading enabled. In fact when I still worked support at a 
certain database vendor we simply refused to support any of our apps 
running on machines where HT was enabled.


Note that it wasn't you should not do this, it was go away and phone 
back when you have rebooted with sane kernel options :-)



--
gentoo-user@lists.gentoo.org mailing list