Gilbert Carl Herschberger II wrote:
> For non-shared RAM, an object has exclusive access to a block of RAM.
> If one object has already opened a block of ram, no other object can
> open the same block.
The system and the garbage collector will need to have access to it...
And what if a custom garbage collector is implemented? What if a
profiling utility is to be used? What if the user wants to allow
arbitrary memory access? He can do it with native code now, why not be
able to do it on JOS? How will security be implemented there? This is a
VERY important matter, and until the security mechanism of this scheme
is resolved and tested, arbitrary memory access should not be
implemented, not even for trusted code.
--
"Learn from others' mistakes, for you won't live long
enough to make them all yourself..."
________________________________________________________________________
[EMAIL: mailto:[EMAIL PROTECTED]] [URL: http://www.outworld.org/people/al]
[TEL1: (30) +31 422392] [TEL2: (30) +31 428154] [CELL: (30) +937 110247]
[ADDRESS: 14 Argonafton St., Kalamaria, 551 31, Thessaloniki, Greece GR]
PLEASE DO NOT SEND ME ANY UNSOLICITED COMMERCIAL EMAIL [DSS: 0xDBEF8ECC]
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
