From: Rik Bobbaers <Rik.Bobbaers@icts.kuleuven.be>
To: linux-kernel@vger.kernel.org
Subject: Re: how to tell i386 from x86-64 kernel
Date: Fri, 01 Feb 2008 11:47:29 +0100 [thread overview]
Message-ID: <1201862849.6193.22.camel@lois> (raw)
hi there,
since i'm not on the list... how about:
tail /proc/1/smaps and check the address size...
on 32 bit: ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
on 64 bit: ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vdso]
there you can clearly see that your address space is double... so
there's your 32 bit vs 64 bit
as a normal user, you can do the same but with your own processes
greetings,
> Hi!
>
> Quiz: on a booted system, how do you tell 32bit from 64bit kernel?
>
> A1: zcat /proc/config.gz | grep CONFIG_64
> ...but config.gz is optional
>
> A2: cat /proc/meminfo | grep High
> ...but i386 kernel could have highmem disabled
>
> What is _your_ answer? ;-)>
--
harry
aka Rik Bobbaers
K.U.Leuven - LUDIT -=- Tel: +32 485 52 71 50
Rik.Bobbaers@icts.kuleuven.be -=- http://harry.enzoverder.be
Don't steal - the government hates competition.
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
next reply other threads:[~2008-02-01 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 10:47 Rik Bobbaers [this message]
2008-02-02 11:06 ` how to tell i386 from x86-64 kernel Pavel Machek
[not found] <960D0E79B4E503448AD14B5E40A5C1C7BB54CE@USX1.corp.bb>
2008-02-01 1:37 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2008-02-01 0:42 Pavel Machek
2008-02-01 0:46 ` Ray Lee
2008-02-01 0:59 ` Jan Engelhardt
2008-02-01 11:53 ` Alejandro Riveira Fernández
2008-02-09 20:13 ` Jan Engelhardt
2008-02-09 22:34 ` Arjan van de Ven
2008-02-10 1:27 ` Pavel Machek
2008-02-01 1:03 ` Pavel Machek
2008-02-01 4:51 ` H. Peter Anvin
2008-02-01 10:07 ` Jiri Kosina
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=1201862849.6193.22.camel@lois \
--to=rik.bobbaers@icts.kuleuven.be \
--cc=linux-kernel@vger.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