History log of /openbsd-src/sys/arch/macppc/include/vmparam.h (Results 1 – 25 of 33)
Revision Date Author Comments
# ed3b9130 30-Jan-2024 deraadt <deraadt@openbsd.org>

the clang binary never shrinks, especially since it is statically
linked (for performance). in this case, it grew larger than the
maximum text segment size; increase that size.


# 08e7272b 15-Mar-2021 deraadt <deraadt@openbsd.org>

Don't put an extern variable (ppc_kvm_stolen) into vmparam.h, other instances
of this file are only doing cpp #define


# 3a91b465 01-Nov-2015 miod <miod@openbsd.org>

Remove the definition of USRTEXT. It has no relevance outside of the non-PIE
a.out world.
ok deraadt@ kettenis@


# a201ab69 10-Feb-2015 tedu <tedu@openbsd.org>

increase min address to page size for all remaining min == 0 systems.
not necessary, but consistent with other platforms. ok deraadt


# 46c64855 09-Oct-2014 tedu <tedu@openbsd.org>

revert unintentional commit unrelated to LKM


# 16272b53 09-Oct-2014 tedu <tedu@openbsd.org>

remove LKM devices


# cfd52802 02-Jun-2014 brad <brad@openbsd.org>

Bump DFLSSIZ to 2MB to match most of the other platforms.

ok miod@


# 62fe2d4b 30-Jan-2014 miod <miod@openbsd.org>

Move declaration of struct vm_page_md from <machine/vmparam.h> to
<machine/pmap.h> where it belongs, and compensate in <uvm/uvm_extern.h>
by including <uvm/uvm_pmap.h> before <uvm/uvm_page.h>. Tested

Move declaration of struct vm_page_md from <machine/vmparam.h> to
<machine/pmap.h> where it belongs, and compensate in <uvm/uvm_extern.h>
by including <uvm/uvm_pmap.h> before <uvm/uvm_page.h>. Tested on all
MACHINE_ARCH but amd64 and i386 (and hppa64).

show more ...


# 22c9ca0c 24-Jan-2014 miod <miod@openbsd.org>

Do not protect struct vm_page_md with defined(_KERNEL), for userland uvm
grovellers need to know it to be able to get the right size for struct
vm_page.


# 736608ca 23-Jan-2014 miod <miod@openbsd.org>

unifdef -D__HAVE_VM_PAGE_MD - no functional change.


# 2ce3b4a8 30-May-2011 oga <oga@openbsd.org>

Remove the freelist member from vm_physseg

The new world order of pmemrange makes this data completely redundant
(being dealt with by the pmemrange constraints instead). Remove all code
that messes

Remove the freelist member from vm_physseg

The new world order of pmemrange makes this data completely redundant
(being dealt with by the pmemrange constraints instead). Remove all code
that messes with the freelist.

While touching every caller of uvm_page_physload() anyway, add the flags
argument to all callers (all but one is 0 and that one already used
PHYSLOAD_DEVICE) and remove the macro magic to allow callers to continue
without it.

Should shrink the code a bit, as well.

matthew@ pointed out some mistakes i'd made.
``freelist death, I like. Ok.' ariane@
`I agree with the general direction, go ahead and i'll fix any fallout
shortly'' miod@ (68k 88k and vax i could not check would build)

show more ...


# 4e38a0c4 03-Mar-2011 ajacoutot <ajacoutot@openbsd.org>

Crank MAXDSIZ up to 2G on macppc and socppc.

ok miod@ drahn@ kettenis@


# 01d0831f 15-Dec-2010 tedu <tedu@openbsd.org>

oops, i forgot to check in the BRKSIZ define in uvm, but deraadt thinks
its better as a per arch MD define anyway. all default to MAXDSIZ as before.


# c62276a4 18-Jul-2008 kurt <kurt@openbsd.org>

Add new uvm function called uvm_map_pie() which takes align as a
parameter and returns an aligned random load address for position
independent executables to use. This also adds three new vmparam.h
d

Add new uvm function called uvm_map_pie() which takes align as a
parameter and returns an aligned random load address for position
independent executables to use. This also adds three new vmparam.h
defines to specify the maximum address, minimum address and minimum
allowed alignment for uvm_map_pie() to use. The PIE address range
for i386 was carefully selected to work well within the i386 W^X
framework.

With much help and feedback from weingart@.
okay weingart@, miod@, kettenis@, drahn@

show more ...


# 69b9ef50 14-Jun-2007 drahn <drahn@openbsd.org>

When macppc was switched to __HAVE_VM_PAGE_MD, data structures were incorrectly
exposed to userland, protect with _KERNEL. Tested by Antoine Jacoutot


# a60c61ef 27-May-2007 drahn <drahn@openbsd.org>

Move powerpc to vm_page_md, 'throw it in' kettenis@


# 65a37b56 18-Sep-2006 marco <marco@openbsd.org>

Extend the .text and .data segments to 64MB. This allows programs with
large .text segments, like xmame, to run.

ok drahn


# e02071cf 17-Dec-2005 miod <miod@openbsd.org>

Get rid of deprecated vm_{offset,size}_t types for good, use {p,v}{addr,size}_t
instead; looked at millert@


# a489ea08 11-Apr-2005 deraadt <deraadt@openbsd.org>

use MD #define to choose stackgap size per-architecture. on sparc, special
case sun4c/sun4 -- because address space is more constrained


# 6b00896d 28-Nov-2004 mickey <mickey@openbsd.org>

MAXSLP is not really an MD-configurable define so move it to param.h; miod@ testing


# 3d1403a8 24-Jun-2004 drahn <drahn@openbsd.org>

Do a better job at containing powerpc specific #defines to PPC_...
ok deraadt@


# 47adadef 23-Jan-2004 millert <millert@openbsd.org>

Crank SHMMAXPGS to 32mb; deraadt@ OK for all, drahn@ OK for macppc + pegasos


# 6a1aaa0f 15-Sep-2002 deraadt <deraadt@openbsd.org>

backout premature


# e1f7838a 15-Sep-2002 deraadt <deraadt@openbsd.org>

KNF


# e8788ae9 13-Mar-2002 drahn <drahn@openbsd.org>

Complete rewrite of the powerpc pmap handling, Instead of keeping
the spill list for each PTEG, the V->P translations are stored in
trees for each pmap. All valid kernel mappings are preallocated
in

Complete rewrite of the powerpc pmap handling, Instead of keeping
the spill list for each PTEG, the V->P translations are stored in
trees for each pmap. All valid kernel mappings are preallocated
in 1-1 memory so that tlb spill/loads for kernel accesses can be
looked up while physical, user mappings are not guaranteed to
be 1-1 mapped, thus the kernel must go virtual to look up user
mappings. While this is more expensive, the tree search is much
lower cost than the long linked list search. Also on each pmap_remove()
it was necessary to search the linked lists for each possible mapping,
now it just looks up the entry in the tree.
This change gives a 25-36% speedup in 'make build' time. What was
around 2:50 is now around 1:55 on a 733MHz G4.

This change causes a likely existing bug to appear quite often,
it deals with the segment register invalidation in kernel mode.
Because of that problem, currently this change limits the physical
memory used to 256MB. This limitation will be fixed soon, it is not
an error in the pmap code.

* Effort sponsored in part by the Defense Advanced Research Projects
* Agency (DARPA) and Air Force Research Laboratory, Air Force
* Materiel Command, USAF, under agreement number F30602-01-2-0537.

show more ...


12