| Age | Commit message (Collapse) | Author |
|---|
|
pool_setipl(9) has been called. This avoids the panic introduced in rev 1.139
(which was subsequently backed out) while still effectively guaranteeing a
consistent snapshot. Pools used from interrupt handlers should use the
appropriate pool IPL.
ok dlg@, deraadt@
|
|
falsely triggered the added panic. revert the panic for now while a
better solution is being worked on
as reported by Bjorn Ketelaars on misc@ via jsing@
|
|
committing the printfs. revert.
|
|
malloc bucket isn't precise, it can have anything in it.
should fix recent panics. sorry for inconvenience.
ok deraadt millert
|
|
it multiple times. Also remove an unused variable. OK deraadt@ tedu@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ordering regions mapped executable, so remove those permissions.
ok deraadt@
|
|
isnt descriptive enough for me.
ok deraadt@
|
|
later on
ok deraadt@
|
|
|
|
|
|
gets only allocated when needed. This way struct socket shrinks
from 472 to 392 bytes on amd64. When splicing gets active, another
88 bytes are allocated for struct sosplice.
OK dlg@
|
|
|
|
ok doug tedu
|
|
ok deraadt, kettenis
|
|
|
|
|
|
|
|
|
|
doesn't need to hold an extra reference during the call
ok deraadt@ millert@
|
|
causes a deadlock between reaper and zerothread I am currently investigating.
|
|
Both sys_mkfifo(2) and sys_mkfifoat(2) could be replace by libc wrappers
using mknodat(2) at a later date if we desire. OK guenther@
|
|
|
|
redundant copies of the same information. No functional change.
Also add some comments as to how these globals are used.
|
|
construct ELF executables for which ep_daddr ends up not being properly
aligned. Sanitize the addresses before setting up the address space for the
new executable. Should fix the panic discovered by Alejandro Hernandez.
ok miod@
|
|
MD code needs excess #ifndef SMALL_KERNEL
|
|
introduce a new sysctl, hw.perfpolicy, that governs the policy.
when set to anything other than manual, hw.setperf then becomes read only.
phessler was heading in this direction, but this is slightly different. :)
|
|
hibernate anymore.
|
|
|
|
|
|
tweaks and ok millert@ deraadt@
|
|
i couldnt measure a significant performance difference with or
without it. this is likely a function of the memory involved being
close to bits that are already being touched, the implemention being
simple macros that mean registers can stay hot, and a lack of
conditionals that would cause a cpu pipeline to crash.
this means we're unconditionally poisoning the first two u_longs
of pool items on all kernels. i think it also makes the code easier
to read.
discussed with deraadt@
|
|
|
|
enabled by setting hw.setperf=-1. some other bugs preventing this from
going in before have been fixed. my thanks to phessler for keeping the
diff alive in the mean time. tested by several to not regress.
|
|
previously they were ints, but this bumps them to long sized words.
in the pool item headers they were followed by the XSIMPLEQ entries,
which are basically pointers which got long word alignment. this
meant there was a 4 byte gap on 64bit architectures between the
magic and list entry that wasnt being poisoned or checked.
this change also uses the header magic (which is sourced from
arc4random) with an xor of the item address to poison the item magic
value. this is inspired by tedu's XSIMPLEQ lists, and means we'll
be exercising memory with more bit patterns.
lastly, this takes more care around the handling of the pool_debug
flag. pool pages read it when theyre created and stash a local copy
of it. from then on all items returned to the page will be poisoned
based on the pages local copy of the flag. items allocated off the
page will be checked for valid poisoning only if both the page and
pool_debug flags are both set.
this avoids a race where pool_debug was not set when an item is
freed (so it wouldnt get poisoned), then gets set, then an item
gets allocated and fails the poison checks because pool_debug wasnt
set when it was freed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok deraadt@ dlg@ phessler@
|
|
to see if we've hogged the cpu for >1 second.
okay miod@
|
|
way we can do some useful kernel lock in parallel with other things and create
a reservoir of zeroed pages ready for use elsewhere. This should reduce
latency. The thread runs at the absolutel lowest priority such that we don't
keep other kernel threads or userland from doing useful work.
Can be easily disabled by disabling the kthread_create(9) call in main().
Which perhaps we should do for non-MP kernels.
ok deraadt@, tedu@
|
|
coordinate with other mbufs so you can add all the pointers without
taking the extref lock.
looks good deraadt@
|
