| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.
ok tedu@ deraadt@
|
|
|
|
| |
define in sys/limits.h. OK guenther@
|
| |
|
|
|
|
| |
to include that than rdnvar.h. ok deraadt dlg
|
|
|
|
|
|
|
| |
PROT_NONE, PROT_READ, PROT_WRITE, and PROT_EXEC from mman.h.
PROT_MASK is introduced as the one true way of extracting those bits.
Remove UVM_ADV_* wrapper, using the standard names.
ok doug guenther kettenis
|
|
|
|
|
|
| |
malloc bucket isn't precise, it can have anything in it.
should fix recent panics. sorry for inconvenience.
ok deraadt millert
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ok mpi@ kspillner@
|
| |
|
|
|
|
| |
after discussions with beck deraadt kettenis.
|
|
|
|
| |
ok deraadt
|
|
|
|
|
|
|
| |
While here, change malloc(9)'s size argument from "unsigned long" to
"size_t".
ok tedu
|
| |
|
| |
|
|
|
|
| |
ok deraadt@
|
| |
|
|
|
|
|
|
| |
(then immediately reacquire it). this has the effect of giving interrupts
on other CPUs to a chance to run and reduces latency in many cases.
ok deraadt
|
|
|
|
|
|
| |
<uvm/uvm.h> if possible and remove double inclusions.
ok beck@, mlarkin@, deraadt@
|
| |
|
|
|
|
| |
tested on vax (gcc3) ok miod@
|
| |
|
|
|
|
| |
ok miod
|
|
|
|
| |
this adds a tiny bit more protection from list manipulation.
|
|
|
|
|
| |
allow some more pool debug code to be enabled if not compiled in
bump poison size back up to 64
|
|
|
|
| |
ok deraadt
|
|
|
|
| |
ok deraadt mpi
|
| |
|
|
|
|
| |
ok deraadt
|
|
|
|
|
|
| |
in MI code; gcc 2.95 does not accept such annotation for function pointer
declarations, only function prototypes.
To be uncommented once gcc 2.95 bites the dust.
|
|
|
|
|
|
| |
function pointer arguments which are {used as,} wrappers around the kernel
printf function.
No functional change.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
no oks (it is really a pain to review properly)
extensively tested, I'm confident it'll be stable
'now is the time' from several icb inhabitants
Diff provides:
- ability to specify different allocators for different regions/maps
- a simpler implementation of the current allocator
- currently in compatibility mode: it will generate similar addresses
as the old allocator
|
|
|
|
| |
ok deraadt@
|
|
|
|
| |
outside the tree.
|
|
|
|
|
|
| |
appears to be safe now. If not, we'll know soon where the bugs lie, so
that we can fix them. This diff has been in snapshots for many months.
ok oga miod
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
vmmap is designed to perform address space randomized allocations,
without letting fragmentation of the address space go through the roof.
Some highlights:
- kernel address space randomization
- proper implementation of guardpages
- roughly 10% system time reduction during kernel build
Tested by alot of people on tech@ and developers.
Theo's machines are still happy.
|
|
|
|
|
| |
have real values, no 0 values anymore.
ok deraadt kettenis krw matthew oga thib
|
|
|
|
|
|
|
|
|
|
| |
Currently only checks that we're not in an interrupt context, but will
soon check that we're not holding any mutexes either.
Update malloc(9) and pool(9) to use assertwaitok(9) as appropriate.
"i like it" art@, oga@, marco@; "i see no harm" deraadt@; too trivial
for me to bother prying actual oks from people.
|
|
|
|
|
|
| |
so no point in reserving space for kmemstats unless it's enabled.
ok thib@, deraadt@
|
|
|
|
|
|
|
|
|
| |
Use uvm_km_kmemalloc_pla with the dma constraint to allocate kernel stacks.
Yes, that means DMA is possible to kernel stacks, but only until we've fixed
all the scary drivers.
deraadt@ ok
|
|
|
|
|
|
|
| |
Do this by calling uvm_km_kmemalloc_pla with the dma_constraint.
ok art@ (ofcourse, he eats his cereal and okeys everything).
OK beck@, deraadt@
|
|
|
|
|
|
|
|
| |
uvm_map_checkprot() call, if the memory we're about to return has just been
allocated with uvm_km_kmemalloc() instead of coming from the freelist.
No functional change but a very small speedup when the freelist for the given
bucket is empty.
|
|
|
|
|
|
|
|
|
| |
input, in order to pick the appropriate malloc() bucket.
Replace it with an inline function in kern_malloc.c, which will either
do a tightest-but-slower loop (if option SMALL_KERNEL), or a geometric search
equivalent to what the macro does, but producing smaller code (especially on
platforms which can not load large constants in one instruction).
|
|
|
|
|
|
|
| |
value (based on physmem) is below NKMEMPAGES_MIN, we are on a low memory
machine and can not afford more anyway.
ok deraadt@ tedu@
|