Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <f78a4b55513a35eed5eaa1173ff0d4e9@freescale.com>
Content-Transfer-Encoding: 7bit
Cc: Becky Gill <bgill@freescale.com>
From: Kumar Gala <kumar.gala@freescale.com>
Subject: use of TASK_SIZE to determine user/kernel
Date: Fri, 18 Feb 2005 11:04:20 -0600
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 741
Lines: 17

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/