From: Kumar Gala <kumar.gala@freescale.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Becky Gill <bgill@freescale.com>
Subject: use of TASK_SIZE to determine user/kernel
Date: Fri, 18 Feb 2005 11:04:20 -0600 [thread overview]
Message-ID: <f78a4b55513a35eed5eaa1173ff0d4e9@freescale.com> (raw)
We are looking at a 32-bit architecture implementation were we can have
distinct address spaces for user and kernel, thus allowing 4G's for
each. In doing this we have come across the use of TASK_SIZE to
determine if an address is user vs kernel (example mm/memory.c). I'm
wondering is it just sufficient to set TASK_SIZE to 0xffffffff? This
feels wrong to me, since it would imply that all the places that are
testing will never need access to the kernel memory space.
thanks
- kumar
reply other threads:[~2005-02-18 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f78a4b55513a35eed5eaa1173ff0d4e9@freescale.com \
--to=kumar.gala@freescale.com \
--cc=bgill@freescale.com \
--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
all inboxes | Powered by JetHome®