Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!ucsd!hub!yosemite!bijan
From: bijan@yosemite.ucsb.edu (Bijan Forutanpour)
Newsgroups: comp.os.mach
Subject: VM_ALLOCATE question.
Message-ID: <3611@hub.UUCP>
Date: 17 Jan 90 02:36:51 GMT
Sender: news@hub.UUCP
Reply-To: bijan@yosemite.ucsb.edu (Bijan Forutanpour)
Distribution: usa
Organization: University of California, Santa Barbara
Lines: 24

I had a question for those who use vm_allocate and/or have read the 
"Mach Kernel Interface Manual".
The manual specifies the call to vm_allocate as:

#include <mach.h>
kern_return_t vm_allocate(target_task, address, size, anywhere)
     vm_task_t	target_task;
     ...etc ...etc...
---------------------------------------------------------------------------
I needed to know how the function works so I dug up the source code from
vm/vm_user.c. The CODE looks like:

kern_return_t vm_allocate(map, address, size, anywhere)
     vm_map_t	map;
     ...etc ...etc...

There is no vm_map_t anywhere in the O.S.!!  But task_t DOES include
a field    vm_map_t   map;  which I suppose must be extracted and passed to
vm_allocate.  Has anyone else noticed this apparent "inconsistency"? 
How do YOU call vm_allocate?

Bijan

bijan%cs@hub.ucsb.edu