Adjust VM_MAX_KERNEL_ADDRESS to the max address, not the minimum next.
VM_MAX_KERNEL_ADDERESS is the maximum KVA address. 0xf8000000 is the start of device mapping space. Since several conditional checks use '<=' against VM_MAX_KERNEL_ADDRESS, bad things could feasibly happen.
This commit is contained in:
parent
6185680860
commit
95c357cb5b
@ -111,7 +111,7 @@
|
||||
#define KERNBASE 0xc0000000 /* start of kernel virtual */
|
||||
|
||||
#define VM_MIN_KERNEL_ADDRESS KERNBASE
|
||||
#define VM_MAX_KERNEL_ADDRESS 0xf8000000
|
||||
#define VM_MAX_KERNEL_ADDRESS 0xf7ffffff
|
||||
#define VM_MAX_SAFE_KERNEL_ADDRESS VM_MAX_KERNEL_ADDRESS
|
||||
|
||||
#endif /* AIM/E500 */
|
||||
@ -129,7 +129,7 @@ struct pmap_physseg {
|
||||
* The physical address space is densely populated on 32-bit systems,
|
||||
* but may not be on 64-bit ones.
|
||||
*/
|
||||
#ifdef __powerpc64__
|
||||
#ifdef __powerpc__
|
||||
#define VM_PHYSSEG_SPARSE
|
||||
#else
|
||||
#define VM_PHYSSEG_DENSE
|
||||
|
Loading…
Reference in New Issue
Block a user