Searched hist:246926 (Results 1 - 4 of 4) sorted by relevance

/freebsd-11-stable/sys/arm/include/
H A Dvmparam.hdiff 246926 Sun Feb 17 23:18:50 MST 2013 alc On arm, like sparc64, the end of the kernel map varies from one type of
machine to another. Therefore, VM_MAX_KERNEL_ADDRESS can't be a constant.
Instead, #define it to be a variable, vm_max_kernel_address, just like we
do on sparc64.

Reviewed by: kib
Tested by: ian
/freebsd-11-stable/sys/vm/
H A Dvm_kern.cdiff 246926 Sun Feb 17 23:18:50 MST 2013 alc On arm, like sparc64, the end of the kernel map varies from one type of
machine to another. Therefore, VM_MAX_KERNEL_ADDRESS can't be a constant.
Instead, #define it to be a variable, vm_max_kernel_address, just like we
do on sparc64.

Reviewed by: kib
Tested by: ian
/freebsd-11-stable/sys/arm/arm/
H A Dpmap-v4.cdiff 246926 Sun Feb 17 23:18:50 MST 2013 alc On arm, like sparc64, the end of the kernel map varies from one type of
machine to another. Therefore, VM_MAX_KERNEL_ADDRESS can't be a constant.
Instead, #define it to be a variable, vm_max_kernel_address, just like we
do on sparc64.

Reviewed by: kib
Tested by: ian
H A Dmachdep.cdiff 246926 Sun Feb 17 23:18:50 MST 2013 alc On arm, like sparc64, the end of the kernel map varies from one type of
machine to another. Therefore, VM_MAX_KERNEL_ADDRESS can't be a constant.
Instead, #define it to be a variable, vm_max_kernel_address, just like we
do on sparc64.

Reviewed by: kib
Tested by: ian

Completed in 219 milliseconds