public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Rik Bobbaers <Rik.Bobbaers@icts.kuleuven.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to tell i386 from x86-64 kernel
Date: Sat, 2 Feb 2008 12:06:52 +0100	[thread overview]
Message-ID: <20080202110652.GA5362@elf.ucw.cz> (raw)
In-Reply-To: <1201862849.6193.22.camel@lois>

On Fri 2008-02-01 11:47:29, Rik Bobbaers wrote:
> 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

That tells you if _init_ is 32 or 64 bit, not kernel.

I'm running 32-bit distro on 64-bit kernel here. It works fine (as it
should).

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-02-02 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 10:47 how to tell i386 from x86-64 kernel Rik Bobbaers
2008-02-02 11:06 ` Pavel Machek [this message]
     [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=20080202110652.GA5362@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=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