d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Better handle sparse physical memory: Don't use the address range

Browse Source 
as a measure for available memory to scale the VHPT. Instead, use
the previously determined Maxmem.

Approved by: re (carte blanc)
This commit is contained in:
Marcel Moolenaar 2002-11-29 20:10:21 +00:00
parent fa5d33e242
commit ddc6d86ca3
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=107394
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
sys/ia64/ia64/pmap.c
View File

@ -360,9 +360,12 @@ pmap_bootstrap()
* physical memory and try to locate a region which is large
* enough to contain the VHPT (which must be a power of two in
* size and aligned to a natural boundary).
* Don't use the difference between avail_start and avail_end
* as a measure for memory size. The address space is often
* enough sparse, causing us to (try to) create a huge VHPT.
*/
vhpt_size = 15;
while ((1<<vhpt_size) < ia64_btop(avail_end - avail_start) * 32)
while ((1<<vhpt_size) < ia64_btop(Maxmem) * 32)
vhpt_size++;
vhpt_base = 0;
@ -451,13 +454,6 @@ pmap_bootstrap()
*/
ia64_set_rr(IA64_RR_BASE(6), (6 << 8) | (28 << 2));
ia64_set_rr(IA64_RR_BASE(7), (7 << 8) | (28 << 2));
/*
* Set up proc0's PCB.
*/
#if 0
thread0.td_pcb->pcb_hw.apcb_asn = 0;
#endif
/*
* Reserve some memory for allocating pvs while bootstrapping