Author: nwhitehorn
Date: Mon May 14 04:00:52 2018
New Revision: 333599
URL: https://svnweb.freebsd.org/changeset/base/333599
Log:
Final fix for alignment issues with the page table first patched with
r333273 and partially reverted with r333594.
Older CPUs implement addition of offsets into the page table by a
bitwise OR rather than actual addition, which only works if the table is
aligned at a multiple of its own size (they also require it to be aligned
at a multiple of 256KB). Newer ones do not have that requirement, but it
hardly matters to enforce it anyway.
The original code was failing on newer systems with huge amounts of RAM
(> 512 GB), in which the page table was 4 GB in size. Because the
bootstrap memory allocator took its alignment parameter as an int, this
turned into a 0, removing any alignment constraint at all and making
the MMU fail. The first round of this patch (r333273) fixed this case by
aligning it at 256 KB, which broke older CPUs. Fix this instead by widening
the alignment parameter.
Modified:
head/sys/powerpc/aim/mmu_oea64.c
head/sys/powerpc/aim/mmu_oea64.h
head/sys/powerpc/aim/moea64_native.c
Modified: head/sys/powerpc/aim/mmu_oea64.c
==============================================================================
--- head/sys/powerpc/aim/mmu_oea64.c Mon May 14 01:08:47 2018
(r333598)
+++ head/sys/powerpc/aim/mmu_oea64.c Mon May 14 04:00:52 2018
(r333599)
@@ -2446,7 +2446,7 @@ moea64_remove_all(mmu_t mmu, vm_page_t m)
* calculated.
*/
vm_offset_t
-moea64_bootstrap_alloc(vm_size_t size, u_int align)
+moea64_bootstrap_alloc(vm_size_t size, vm_size_t align)
{
vm_offset_t s, e;
int i, j;
Modified: head/sys/powerpc/aim/mmu_oea64.h
==============================================================================
--- head/sys/powerpc/aim/mmu_oea64.h Mon May 14 01:08:47 2018
(r333598)
+++ head/sys/powerpc/aim/mmu_oea64.h Mon May 14 04:00:52 2018
(r333599)
@@ -39,7 +39,7 @@ extern mmu_def_t oea64_mmu;
*/
/* Allocate physical memory for use in moea64_bootstrap. */
-vm_offset_t moea64_bootstrap_alloc(vm_size_t, u_int);
+vm_offset_t moea64_bootstrap_alloc(vm_size_t size, vm_size_t align);
/* Set an LPTE structure to match the contents of a PVO */
void moea64_pte_from_pvo(const struct pvo_entry *pvo, struct lpte *lpte);
Modified: head/sys/powerpc/aim/moea64_native.c
==============================================================================
--- head/sys/powerpc/aim/moea64_native.c Mon May 14 01:08:47 2018
(r333598)
+++ head/sys/powerpc/aim/moea64_native.c Mon May 14 04:00:52 2018
(r333599)
@@ -453,10 +453,11 @@ moea64_bootstrap_native(mmu_t mmup, vm_offset_t kernel
}
/*
* PTEG table must be aligned on a 256k boundary, but can be placed
- * anywhere with that alignment. Some of our hash calculations,
- * however, assume that the PTEG table is aligned to its own size
- * (low-order bits are zero in an OR). As such, make alignment
- * bigger than strictly necessary for the time being.
+ * anywhere with that alignment on POWER ISA 3+ systems. On earlier
+ * systems, offset addition is done by the CPU with bitwise OR rather
+ * than addition, so the table must also be aligned on a boundary of
+ * its own size. Pick the larger of the two, which works on all
+ * systems.
*/
moea64_pteg_table = (struct lpte *)moea64_bootstrap_alloc(size,
MAX(256*1024, size));
_______________________________________________
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
