From: John Richard Moser <nigelenki@comcast.net>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IA-32 on x86-64
Date: Sat, 20 May 2006 18:09:29 -0400 [thread overview]
Message-ID: <446F9399.7050101@comcast.net> (raw)
In-Reply-To: <20060520214101.GA8413@tachyon.int.mcmartin.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kyle McMartin wrote:
> On Sat, May 20, 2006 at 09:03:11AM -0400, John Richard Moser wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Does anyone know how to check if I'm running an IA-32 process on x86-64?
>
> is_compat_task()
>
>> More importantly, how do I tell how big the user VM space is for
>> current? Like 3GiB for x86 and who knows what (87GiB? 192GiB?) for
>> x86-64 and however much for sparc/ppc ....
>
> TASK_SIZE
>
> You should probably do your own work instead of posting questions everytime
> you hit something you'd have to do a little bit of searching for.
>
Noted. As of late I've had the excuse that I've posted my last question
just before I had to go to bed so everyone else would search for the
answer while I sleep; but point taken ;)
> --
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRG+TmAs1xW0HCTEFAQKtBw/9Gia5K8GLmFo9WB1ePhzfb/tTug/clpoH
iU0AEQgBoFOImKCXLliTdD4r/lr6a68nBei3Aseu9Son0VnIOiB+dI/BuYcpOdN6
b5EdZE9D6vCBR1YHeaMr2lkL6LROlHS4nkb0GPo0IKgWEjhumiK1XK8ojqKQpmh+
2EJ4a0M68LSZJWbw1q58DcAsMACKwj2xtDpcjZsrCRMYwxLrP7wYx3bU6XKiKX2L
u14Q8gMYNaYBYGLm0O7q0AwTwNT+i/tDWtnnuqUCZxiLtTWCLHstZBALEgW2WB6+
pEa+z/JdCuET9Zl3dvqH+5HsJJ7s9tuQA7svDgmatxZ5m0olWFI1Dlg4No2cwoQX
4y2q+a+gYdvgw4BUIh2Tf0XcJ10Sr6turdQc4YoNq2riB5JSH7MS6qedhU38eEKz
30jWv9yRl2CnVn5AzQHWICae4cSMaOP8KxkG3W9fbxJAur3yoAZVz+M3LecNNg5j
GNbObd0COkJTem/eMTsT53WISGkaNG1kDPAkWQZqrusKNXelBwEhjaPhJj/K6isx
v75+S+tJg0gW2mVBxHIw006Z44MnSU6nde9fD+o0C6J8uR42gGHHP2oCTsvtuMQb
6samg/keoAbeXAj3IaL7AgFp+V749U4ISK+3gl1nTxzSnlik4Y6YZ6IT6c1PCQX1
qzhSB5RpOgI=
=NG+P
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-05-20 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 13:03 IA-32 on x86-64 John Richard Moser
2006-05-20 21:37 ` Jan Engelhardt
2006-05-20 21:41 ` Kyle McMartin
2006-05-20 22:09 ` John Richard Moser [this message]
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=446F9399.7050101@comcast.net \
--to=nigelenki@comcast.net \
--cc=kyle@mcmartin.ca \
--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