rokicki@polya.Stanford.EDU (Tomas G. Rokicki) (09/03/88)
Worried about programs breaking because they didn't MEMF_PUBLIC? Fine. We need to add a MEMF_DMA flag anyway (the 2090 can't touch at least the Hurricane '020 memory; the software works, though, just fine, in copying the data, so don't think it breaks) so why not add a MEMF_PRIVATE flag, where the default is MEMF_PUBLIC? All current programs would be loaded completely shared, as they are now, and could stomp on each other. New versions, though, could MEMF_PRIVATE to get safe areas . . . It's just a thought. -tom
jesup@cbmvax.UUCP (Randell Jesup) (09/04/88)
In article <3813@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes: >Worried about programs breaking because they didn't MEMF_PUBLIC? ... >so why not add a MEMF_PRIVATE flag, where the default is MEMF_PUBLIC? Exactly. New programs use it, old ones don't (by default, user should be able to override at their own risk, or maybe some trick of changing the default if a protection violation occurs, though it's risky). -- Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup