lkml.org 
[lkml]   [2008]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Make LIST_POISON less deadly
Ingo Molnar wrote:
> * Avi Kivity <avi@qumranet.com> wrote:
>
>
>>> i'd suggest to add an ARCH_ILLEGAL_POINTER define instead, which
>>> defaults to zero and gets added to pointer-ish poison values. That
>>> makes it both simpler and also it does not need any include/asm
>>> changes because ARCH_ILLEGAL_POINTER can be set from the Kconfig
>>> space.
>>>
>> Right.
>>
>> How much unmapped space do we have on i386 or other archs? The deltas
>> added to ARCH_ILLEGAL_POINTER will have to be limited to that.
>>
>
> can we get away with having the offset default to zero, and all poison
> values remain unchanged if that? Then 64-bit x86 could just set the
> offset to 2^63 and we wont have to worry about 32-bit x86 at all ...
>
> i.e. start small with this and only have an effect on 64-bit x86.
>

Sure, will post an updated patch.

--
error compiling committee.c: too many arguments to function



\
 
 \ /
  Last update: 2008-05-19 15:43    [W:0.029 / U:0.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site