> Date: Sat, 26 Mar 2016 23:02:52 +0100
> From: Martin Pieuchot
>
> On 26/03/16(Sat) 19:19, Stefan Kempf wrote:
> > Stefan Kempf wrote:
> > > amap_extend is called when merging two adjacent areas of virtual address
> > > space. However, merging is done only for kernel
> > >
Martin Pieuchot wrote:
> On 26/03/16(Sat) 19:19, Stefan Kempf wrote:
> > Stefan Kempf wrote:
> > > amap_extend is called when merging two adjacent areas of virtual address
> > > space. However, merging is done only for kernel
> > > virtual address space. It's not done for user space:
> > >
> > >
On 26/03/16(Sat) 19:19, Stefan Kempf wrote:
> Stefan Kempf wrote:
> > amap_extend is called when merging two adjacent areas of virtual address
> > space. However, merging is done only for kernel
> > virtual address space. It's not done for user space:
> >
> > uvm/uvm_map.c:1359
> > /*
> >
Stefan Kempf wrote:
> amap_extend is called when merging two adjacent areas of virtual address
> space. However, merging is done only for kernel
> virtual address space. It's not done for user space:
>
> uvm/uvm_map.c:1359
> /*
>* Try to merge entry.
>*
>* Userland
amap_extend is called when merging two adjacent areas of virtual address
space. However, merging is done only for kernel
virtual address space. It's not done for user space:
uvm/uvm_map.c:1359
/*
* Try to merge entry.
*
* Userland allocations are kept separated