Chris Gilbert wrote:

> On Saturday 13 January 2001 16:59, Ben Harris wrote:
> 
> > It's also worth noting that libkvm currently has the value of
> > VM_MAXUSER_ADDRESS compiled into it, so changing it may cause
> > compatibility issues there.
> 
> Well if we break it we break it.  don't get me wrong, I just prefer the view 
> that if we can improve the code.  current is pretty broken as it stands for 
> arm32 without doing these changes. breaking top, ps and progs of that ilk is 
> not too bad.  (they are the progs that use libkvm aren't they?)

I _think_ that the only thing that uses VM_MAXUSER_ADDRESS is the kvm
routines that fetch argv/envp strings, and these are only used by ps
(and nothing else?) when used on a crash dump.  On a live kernel, sysctl
calls are used for this info.  In short, changing VM_MAXUSER_ADDRESS
shouldn't really affect very much at all.

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD CDs, Support and Service:    http://www.wasabisystems.com/