most likely, i'll be giving a kernel talk at ottawa LUG next week

most likely, i'll be giving a kernel talk at ottawa LUG next week

[Robert P. J. Day]

  while i'm still waiting for official confirmation, i've offered to
give next week's talk at the ottawa (ontario) linux users group.
here's the current posting which doesn't mention it yet:

  http://oclug.on.ca/meeting/70/

since i'm in town and there was nothing on the schedule, i volunteered
to give a short (hands-on) talk on building and booting a new kernel,
and how to write, compile and load your first kernel module.  nothing
earth-shaking, but if you wanted to see that done step-by-step in real
time and be able to ask questions as it's happening, stop by.

  i'm hoping that a synopsis goes up fairly soon.

rday

-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

How to identity processor architecture

[prabhu]

Hi Dear,

I just wanna to know my processor architecture(32bit or 64 bit) through 
c programming.

According to me the sizeof of pointer will give the result. Like below 
coding.

int main()
{
int *ptr;
printf("%d",sizeof(ptr));
}

If the result is 4 then it is 32 bit processor... If it is 8 then it is 
64 bit processor.

Please correct me if i am wrong... (I do not have system to check this.)

Any suggestion or help would be appreciated.

Thanks,
Prabhu

Added about new kernel on old distro (was Re: most likely, i'll be giving a kernel talk at ottawa LUG next week)

[Mulyadi Santosa]

On Thu, Jan 27, 2011 at 01:08, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> since i'm in town and there was nothing on the schedule, i volunteered
> to give a short (hands-on) talk on building and booting a new kernel,
> and how to write, compile and load your first kernel module. ?nothing
> earth-shaking, but if you wanted to see that done step-by-step in real
> time and be able to ask questions as it's happening, stop by.

If you don't mind, if someone ask you about how to run new kernel on
such old distro, you could teach them about the thing I write here:
http://the-hydra.blogspot.com/2011/01/making-latest-26x-linux-kernel-works.html

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

How to identity processor architecture

[prabhu]

Hi Dear,

I just wanna to know my processor architecture(32bit or 64 bit) through 
c programming.

According to me the sizeof of pointer will give the result. Like below 
coding.

int main()
{
   int *ptr;
   printf("%d",sizeof(ptr));
}

Please correct me if i am wrong...

Any suggestion or help would be appreciated.

Thanks,
Prabhu

How to identity processor architecture

[prabhu]

Hi Dear,

I just wanna to know my processor architecture(32bit or 64 bit) through 
c programming.

According to me the sizeof of pointer will give the result. Like below 
coding.

int main()
{
    int *ptr;
    printf("%d",sizeof(ptr));
}

Please correct me if i am wrong...

Any suggestion or help would be appreciated.

Thanks,
Prabhu

How to identity processor architecture

[Enrico Granata]

What if one is compiling 32bit code on a 64bit processor? Would 4 be an acceptable result to you in that case?

Enrico Granata
Computer Science & Engineering Department (EBU3B) - Room 3240
office phone 858 534 9914
University of California, San Diego

On Jan 26, 2011, at 10:07 PM, prabhu wrote:

> Hi Dear,
> 
> I just wanna to know my processor architecture(32bit or 64 bit) through 
> c programming.
> 
> According to me the sizeof of pointer will give the result. Like below 
> coding.
> 
> int main()
> {
>    int *ptr;
>    printf("%d",sizeof(ptr));
> }
> 
> Please correct me if i am wrong...
> 
> Any suggestion or help would be appreciated.
> 
> Thanks,
> Prabhu
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110126/bd71567b/attachment.html 

How to identity processor architecture

[arun kumar]

the size of the integer variable will be equal to your processor
architecture(32bit or 64 bit).

On Thu, Jan 27, 2011 at 11:56 AM, Enrico Granata <egranata@ucsd.edu> wrote:

> What if one is compiling 32bit code on a 64bit processor? Would 4 be an
> acceptable result to you in that case?
>
> *Enrico Granata*
> *Computer Science & Engineering Department (EBU3B) - **Room 3240*
> *office phone 858 534 9914*
> *University of California, San Diego*
>
> On Jan 26, 2011, at 10:07 PM, prabhu wrote:
>
> Hi Dear,
>
> I just wanna to know my processor architecture(32bit or 64 bit) through
> c programming.
>
> According to me the sizeof of pointer will give the result. Like below
> coding.
>
> int main()
> {
>    int *ptr;
>    printf("%d",sizeof(ptr));
> }
>
> Please correct me if i am wrong...
>
> Any suggestion or help would be appreciated.
>
> Thanks,
> Prabhu
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/fef7b460/attachment.html 

How to identity processor architecture

[prabhu]

Hi Enrico,

I am not sure.

No, because 32bit code will tell the datatype size and i think pointer 
variable depends on architecture.
So 64 bit processor needs 64 address line to point the data location. So 
pointer variable needs to be 8 byte.

please correct me if i am worng.

Thanks,
Prabhu


Enrico Granata wrote:
> What if one is compiling 32bit code on a 64bit processor? Would 4 be 
> an acceptable result to you in that case?
>
> /Enrico Granata/
> /Computer Science & Engineering Department (EBU3B) - //Room 3240/
> /office phone 858 534 9914/
> /University of California, San Diego/
>
> On Jan 26, 2011, at 10:07 PM, prabhu wrote:
>
>> Hi Dear,
>>
>> I just wanna to know my processor architecture(32bit or 64 bit) through
>> c programming.
>>
>> According to me the sizeof of pointer will give the result. Like below
>> coding.
>>
>> int main()
>> {
>>    int *ptr;
>>    printf("%d",sizeof(ptr));
>> }
>>
>> Please correct me if i am wrong...
>>
>> Any suggestion or help would be appreciated.
>>
>> Thanks,
>> Prabhu
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/37bc8117/attachment-0001.html 

How to identity processor architecture

[Mulyadi Santosa]

On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
> No, because 32bit code will tell the datatype size and i think pointer
> variable depends on architecture.
> So 64 bit processor needs 64 address line to point the data location. So
> pointer variable needs to be 8 byte.

Please don't top post and please use the new list address, ok? :)

IMO, I second your opinion. And as addition, I think it's worth to
check /proc/cpuinfo too  in "address sizes" field

NB: I was thinking, if in x64, it is operating in full 32 bit mode
(not hybrid one), it is supposed to yield 32 bit address too, right?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

How to identity processor architecture

[Enrico Granata]

On Jan 26, 2011, at 10:45 PM, Mulyadi Santosa wrote:

> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
>> No, because 32bit code will tell the datatype size and i think pointer
>> variable depends on architecture.
>> So 64 bit processor needs 64 address line to point the data location. So
>> pointer variable needs to be 8 byte.
> 
> Please don't top post and please use the new list address, ok? :)
> 
> IMO, I second your opinion. And as addition, I think it's worth to
> check /proc/cpuinfo too  in "address sizes" field
> 
> NB: I was thinking, if in x64, it is operating in full 32 bit mode
> (not hybrid one), it is supposed to yield 32 bit address too, right?
> 
> -- 
> regards,
> 
> Mulyadi Santosa
> Freelance Linux trainer and consultant
> 
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

I guess a 64bit processor does need 64bit addresses to reference memory. But at the same time, if 32 bit programs are to run unmodified on 64 bit architectures there needs to be ways in which 32bit pointers can still work. So, I am almost 100% sure that compiling 32bit code, even on a 64bit processor, should yield 4 for sizeof(void*)

Enrico Granata
Computer Science & Engineering Department (EBU3B) - Room 3240
office phone 858 534 9914
University of California, San Diego

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110126/92bcc874/attachment.html 

How to identity processor architecture

[dharmvir kumar]

 64-bit processors  have lm ("long mode") in the flags section of
cpuinfowhereas   32-bit processors have not.
regards
Dharmvir Kumar


On Thu, Jan 27, 2011 at 12:24 PM, Enrico Granata <egranata@ucsd.edu> wrote:

> On Jan 26, 2011, at 10:45 PM, Mulyadi Santosa wrote:
>
> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
>
> No, because 32bit code will tell the datatype size and i think pointer
>
> variable depends on architecture.
>
> So 64 bit processor needs 64 address line to point the data location. So
>
> pointer variable needs to be 8 byte.
>
>
> Please don't top post and please use the new list address, ok? :)
>
> IMO, I second your opinion. And as addition, I think it's worth to
> check /proc/cpuinfo too  in "address sizes" field
>
> NB: I was thinking, if in x64, it is operating in full 32 bit mode
> (not hybrid one), it is supposed to yield 32 bit address too, right?
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> I guess a 64bit processor does need 64bit addresses to reference memory.
> But at the same time, if 32 bit programs are to run unmodified on 64 bit
> architectures there needs to be ways in which 32bit pointers can still work.
> So, I am almost 100% sure that compiling 32bit code, even on a 64bit
> processor, should yield 4 for sizeof(void*)
>
> *Enrico Granata*
> *Computer Science & Engineering Department (EBU3B) - **Room 3240*
> *office phone 858 534 9914*
> *University of California, San Diego*
> *
> *
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/e349ee2a/attachment-0001.html 

How to identity processor architecture

[Mandeep Sandhu]

> I guess a 64bit processor does need 64bit addresses to reference memory. But
> at the same time, if 32 bit programs are to run unmodified on 64 bit
> architectures there needs to be ways in which 32bit pointers can still work.
> So, I am almost 100% sure that compiling 32bit code, even on a 64bit
> processor, should yield 4 for sizeof(void*)

You are 100% right. Tried this on  2 laptops:

printf("Is this a %s-bit machine?\n", ((sizeof(void*) == 4) ? "32" : "64"));

32-Bit ubuntu (10.10) on 64-bit proc:
"Is this a 32-bit machine?"

64-Bit ubuntu (10.10) on 64-bit proc:
"Is this a 64-bit machine?"

Regards,
-mandeep

> Enrico Granata
> Computer Science & Engineering Department (EBU3B) -?Room 3240
> office phone 858 534 9914
> University of California, San Diego
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>

How to identity processor architecture

[prabhu]

Mandeep Sandhu wrote:
>> I guess a 64bit processor does need 64bit addresses to reference memory. But
>> at the same time, if 32 bit programs are to run unmodified on 64 bit
>> architectures there needs to be ways in which 32bit pointers can still work.
>> So, I am almost 100% sure that compiling 32bit code, even on a 64bit
>> processor, should yield 4 for sizeof(void*)
>>     
>
> You are 100% right. Tried this on  2 laptops:
>
> printf("Is this a %s-bit machine?\n", ((sizeof(void*) == 4) ? "32" : "64"));
>
> 32-Bit ubuntu (10.10) on 64-bit proc:
> "Is this a 32-bit machine?"
>
> 64-Bit ubuntu (10.10) on 64-bit proc:
> "Is this a 64-bit machine?"
>
> Regards,
> -mandeep
>   

Hi Mandeep,

Thanks a lot.

So is there any other way available to identify the processor 
architecture using c code?? . The program needs to return correct
processor architecture(32bit or 64bit) irrespective to the OS architecture.

Thanks,
Prabhu
>> Enrico Granata
>> Computer Science & Engineering Department (EBU3B) - Room 3240
>> office phone 858 534 9914
>> University of California, San Diego
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>>     
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/22de50ff/attachment.html 

How to identity processor architecture

[Enrico Granata]

Enrico Granata
Computer Science & Engineering Department (EBU3B) - Room 3240
office phone 858 534 9914
University of California, San Diego

On Jan 27, 2011, at 12:20 AM, prabhu wrote:

> Mandeep Sandhu wrote:
>> 
>>> I guess a 64bit processor does need 64bit addresses to reference memory. But
>>> at the same time, if 32 bit programs are to run unmodified on 64 bit
>>> architectures there needs to be ways in which 32bit pointers can still work.
>>> So, I am almost 100% sure that compiling 32bit code, even on a 64bit
>>> processor, should yield 4 for sizeof(void*)
>>>     
>> 
>> You are 100% right. Tried this on  2 laptops:
>> 
>> printf("Is this a %s-bit machine?\n", ((sizeof(void*) == 4) ? "32" : "64"));
>> 
>> 32-Bit ubuntu (10.10) on 64-bit proc:
>> "Is this a 32-bit machine?"
>> 
>> 64-Bit ubuntu (10.10) on 64-bit proc:
>> "Is this a 64-bit machine?"
>> 
>> Regards,
>> -mandeep
>>   
> 
> Hi Mandeep,
> 
> Thanks a lot.
> 
> So is there any other way available to identify the processor architecture using c code?? . The program needs to return correct 
> processor architecture(32bit or 64bit) irrespective to the OS architecture.
> 
> Thanks,
> Prabhu
>>> Enrico Granata
>>> Computer Science & Engineering Department (EBU3B) - Room 3240
>>> office phone 858 534 9914
>>> University of California, San Diego
>>> 
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>> 
>>> 
>>>     
>> 
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>> 
>> 
>>   
> 

Someone already hinted at it, I guess:

>  64-bit processors  have lm ("long mode") in the flags section of cpuinfo whereas   32-bit processors have not.
> regards
> Dharmvir Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/6bbf5427/attachment.html 

How to identity processor architecture

[prabhu]

>>  64-bit processors  have lm ("long mode") in the flags section 
>> of cpuinfo whereas   32-bit processors have not.
>> regards
>> Dharmvir Kumar
Thanks a lot folks.

Adding more detail on this.

Below detail helps to understand CPU architecture.
_*
*__*Finding CPU Arch*_

    $ grep flags /proc/cpuinfo | uniq | egrep -o -w "rm|tm|lm"

    Under "Flags" section in /proc/cpuinfo, you will find any of the 
flags "tm" or

    "rm" or "lm"

        * rm (Real Mode) means it is a 16 bit processor
        * tm (Transparent Mode) means it is a 32 bit processor
        * lm (Long Mode) means it is a 64 bit processor


Is this only way to find the processor architecture ????

Any C programming technique apart from using this /proc/cpuinfo detail?

Thanks,
Prabhu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/732cd8c0/attachment.html 

How to identity processor architecture

[Henry Gebhardt]

On Thu, Jan 27, 2011 at 03:23:28PM +0530, prabhu wrote:
> Any C programming technique apart from using this /proc/cpuinfo detail?

What about using the machine field of uname(2):

   $ man 2 uname

Quoting from that man page:

   [...] the operating system  presumably  knows  its name,  release
   and version.   It also knows what hardware it runs on.

Perhaps a downside, it returns the machine type as a string.  Does that
do what you want?

I also find "man linux32" rather interesting:

    setarch  -  change reported architecture in new program environment
    and set personality flags

Might be useful for testing.


Greetings,
Henry

How to identity processor architecture

[Thirugnanam Balamurugan]

Also , the below one could help.

$ getconf LONG_BIT
64
$

Regards,
Bala


-----Original Message-----
From: kernelnewbies-bounces@kernelnewbies.org
[mailto:kernelnewbies-bounces at kernelnewbies.org] On Behalf Of Henry
Gebhardt
Sent: Thursday, January 27, 2011 4:46 PM
To: prabhu
Cc: Enrico Granata; kernelnewbies
Subject: Re: How to identity processor architecture

On Thu, Jan 27, 2011 at 03:23:28PM +0530, prabhu wrote:
> Any C programming technique apart from using this /proc/cpuinfo
detail?

What about using the machine field of uname(2):

   $ man 2 uname

Quoting from that man page:

   [...] the operating system  presumably  knows  its name,  release
   and version.   It also knows what hardware it runs on.

Perhaps a downside, it returns the machine type as a string.  Does that
do what you want?

I also find "man linux32" rather interesting:

    setarch  -  change reported architecture in new program environment
    and set personality flags

Might be useful for testing.


Greetings,
Henry

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

How to identity processor architecture

[Pravin Shedage]

Hi,

This C program might help you.

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <sys/utsname.h>

int main()
{
    struct utsname *buf = NULL;



    buf = malloc(sizeof(struct utsname));
    if (buf == NULL) {
        fprintf(stderr,"Memory Allocation Error: %s \n", strerror(errno));
        exit(-1);
    }

    if (uname(buf) < 0) {
        fprintf(stderr,"UName Error: %s \n", strerror(errno));
        exit(-1);
    }

    printf ("Processor arch =:>) %s \n", buf->machine);

    return 0;
}




On Thu, Jan 27, 2011 at 4:45 PM, Henry Gebhardt
<hsggebhardt@googlemail.com>wrote:

> On Thu, Jan 27, 2011 at 03:23:28PM +0530, prabhu wrote:
> > Any C programming technique apart from using this /proc/cpuinfo detail?
>
> What about using the machine field of uname(2):
>
>   $ man 2 uname
>
> Quoting from that man page:
>
>   [...] the operating system  presumably  knows  its name,  release
>   and version.   It also knows what hardware it runs on.
>
> Perhaps a downside, it returns the machine type as a string.  Does that
> do what you want?
>
> I also find "man linux32" rather interesting:
>
>    setarch  -  change reported architecture in new program environment
>    and set personality flags
>
> Might be useful for testing.
>
>
> Greetings,
> Henry
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 


Thanks & Regards,
---------PraviN---------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/39c367d2/attachment.html 

How to identity processor architecture

[prabhu]

Pravin Shedage wrote:
> Hi,
>
> This C program might help you.
>
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> #include <errno.h>
> #include <sys/utsname.h>
>
> int main()
> {
>     struct utsname *buf = NULL;
>
>
>
>     buf = malloc(sizeof(struct utsname));
>     if (buf == NULL) {
>         fprintf(stderr,"Memory Allocation Error: %s \n", strerror(errno));
>         exit(-1);
>     }
>
>     if (uname(buf) < 0) {
>         fprintf(stderr,"UName Error: %s \n", strerror(errno));
>         exit(-1);
>     }
>
>     printf ("Processor arch =:>) %s \n", buf->machine);
>
>     return 0;
> }
>
>
>
>
> On Thu, Jan 27, 2011 at 4:45 PM, Henry Gebhardt 
> <hsggebhardt at googlemail.com <mailto:hsggebhardt@googlemail.com>> wrote:
>
>     On Thu, Jan 27, 2011 at 03:23:28PM +0530, prabhu wrote:
>     > Any C programming technique apart from using this /proc/cpuinfo
>     detail?
>
>     What about using the machine field of uname(2):
>
>       $ man 2 uname
>
>     Quoting from that man page:
>
>       [...] the operating system  presumably  knows  its name,  release
>       and version.   It also knows what hardware it runs on.
>
>     Perhaps a downside, it returns the machine type as a string.  Does
>     that
>     do what you want?
>
>     I also find "man linux32" rather interesting:
>
>        setarch  -  change reported architecture in new program environment
>        and set personality flags
>
>     Might be useful for testing.
>
>
>     Greetings,
>     Henry
>

Both Ideas give the  Kernel architecture not cpu architecture.

You can get exact cpu architecture through lshw command.

*-cpu
          product: Intel(R) Pentium(R) Dual  CPU  E2160  @ 1.80GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu at 0
          version: 6.15.13
          serial: 0000-06FD-0000-0000-0000-0000
          size: 1200MHz
          capacity: 1200MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx x86-64 constant_tsc arch_perfmon pebs bts pni dtes64 
monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm cpufreq
          configuration: id=1
        *-logicalcpu:0
             description: Logical CPU
             physical id: 1.1
             width: 64 bits
             capabilities: logical
        *-logicalcpu:1
             description: Logical CPU
             physical id: 1.2
             width: 64 bits
             capabilities: logical

>     _______________________________________________
>     Kernelnewbies mailing list
>     Kernelnewbies at kernelnewbies.org
>     <mailto:Kernelnewbies@kernelnewbies.org>
>     http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
>
>
> -- 
>
>
> Thanks & Regards,
> ---------PraviN---------
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/e8f6faf3/attachment.html 

How to identity processor architecture

[prabhu]

Hi Mulyadi,
> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
>   
>> No, because 32bit code will tell the datatype size and i think pointer
>> variable depends on architecture.
>> So 64 bit processor needs 64 address line to point the data location. So
>> pointer variable needs to be 8 byte.
>>     
>
> Please don't top post and please use the new list address, ok? :)
>   
Sure, Thanks for your reply.
> IMO, I second your opinion. And as addition, I think it's worth to
> check /proc/cpuinfo too  in "address sizes" field
>   
I am getting below output for /proc/cpuinfo . I hope *cpu family : 6 
*means x86 family(32 bit processor). What if its 64 bit processor. ( I 
dont have system to check this.)

processor : 0
vendor_id : GenuineIntel
*cpu family : 6*
model : 15
model name : Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz
stepping : 13
cpu MHz : 1200.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr 
pdcm lahf_lm
bogomips : 3591.05
clflush size : 64
power management:

processor : 1
vendor_id : GenuineIntel
*cpu family : 6*
model : 15
model name : Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz
stepping : 13
cpu MHz : 1200.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat 
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr 
pdcm lahf_lm
bogomips : 3590.97
clflush size : 64
power management:
> NB: I was thinking, if in x64, it is operating in full 32 bit mode
> (not hybrid one), it is supposed to yield 32 bit address too, right?
>   
I'm sorry . I have no idea about this.

Thanks,
Prabhu

How to identity processor architecture

[Mulyadi Santosa]

Hi...

On Thu, Jan 27, 2011 at 14:07, prabhu <prabhum@msys-tech.com> wrote:
> I am getting below output for /proc/cpuinfo . I hope *cpu family : 6 *means
> x86 family(32 bit processor). What if its 64 bit processor. ( I dont have
> system to check this.)
>
> processor : 0
> vendor_id : GenuineIntel
> *cpu family : 6*
> model : 15
> model name : Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz

according to http://en.wikipedia.org/wiki/Pentium_Dual-Core, yours
falls into Allendale core category, which is already using Intel 64
technology. So, unless I am mistaken somewhere, yours is x64. The
problem is, is it working in hybrid 64/32 bit or in full 32 bit ....?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

How to identity processor architecture

[mindentropy]

On Thursday 27 Jan 2011 12:15:47 pm Mulyadi Santosa wrote:
> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
> > No, because 32bit code will tell the datatype size and i think pointer
> > variable depends on architecture.
> > So 64 bit processor needs 64 address line to point the data location. So
> > pointer variable needs to be 8 byte.
> 
> Please don't top post and please use the new list address, ok? :)
> 
> IMO, I second your opinion. And as addition, I think it's worth to
> check /proc/cpuinfo too  in "address sizes" field
> 
> NB: I was thinking, if in x64, it is operating in full 32 bit mode
> (not hybrid one), it is supposed to yield 32 bit address too, right?
Why not simply use CPUID ?

How to identity processor architecture

[Denis Kirjanov]

On Thu, Jan 27, 2011 at 10:27 PM, mindentropy <mindentropy@gmail.com> wrote:
> On Thursday 27 Jan 2011 12:15:47 pm Mulyadi Santosa wrote:
>> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
>> > No, because 32bit code will tell the datatype size and i think pointer
>> > variable depends on architecture.
>> > So 64 bit processor needs 64 address line to point the data location. So
>> > pointer variable needs to be 8 byte.
>>
>> Please don't top post and please use the new list address, ok? :)
>>
>> IMO, I second your opinion. And as addition, I think it's worth to
>> check /proc/cpuinfo too ?in "address sizes" field
>>
>> NB: I was thinking, if in x64, it is operating in full 32 bit mode
>> (not hybrid one), it is supposed to yield 32 bit address too, right?
> Why not simply use CPUID ?

In this case solution is not portable and uses arch specific methods.
I think most 64-bit systems today use LP64 data model.

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Regards,
Denis