| Age | Commit message (Collapse) | Author |
|---|
|
marker for which pools are not interrupt safe. ok dlg
|
|
a second.
this basically brings back the functionality that was trimmed in r1.53,
except this version uses ticks instead of very slow hardware clock reads.
ok tedu@
|
|
latter is cheaper, but i forgot to change the thing that pulls pages off
those lists to match the change in direction. the page lists went from LIFO
to FIFO.
this changes pool_update_curpage to use TAILQ_LAST so we go back to LIFO.
pointed out by and ok tedu@
|
|
either end of the lists cheaply.
ok kettenis@ tedu@
|
|
era. fix uvm including c files to include lock.h or atomic.h as necessary.
ok deraadt
|
|
doesn't have all the values and therefore can't be used everywhere.
ok deraadt@ kettenis@
|
|
objective: vnode.h doesn't include uvm_extern.h anymore.
followup changes: include uvm_extern.h or lock.h where necessary.
ok and help from deraadt
|
|
eliminating the must-be-kept-in-sync UVM_INH_* macros
ok deraadt@ tedu@
|
|
ok tedu@ deraadt@
|
|
controls whether you can ptrace any process with appropriate privileges
or only one own's children.
ok deraadt
|
|
Previous version OK'ed by tedu@ deraadt@
|
|
|
|
|
|
|
|
ok deraadt, tests on glxpcib and ok mpi
|
|
|
|
ok deraadt@ tedu@
|
|
|
|
|
|
|
|
OK deraadt@
|
|
This adds a new sysctl KERN_PROC_VMMAP, which returns an array of VM map
entries of a specified process. This prevents debuggers from iterating
vm_map_entry RB tree via kvm(3).
The name KERN_PROC_VMMAP and struct kinfo_vmentry are chosen from the same
function in FreeBSD. struct kinfo_vmentry is revised to reduce size, because
OpenBSD does not keep track of filepaths. The semantic is also changed to
return max buffer size as a hint, and start iteration at the specified base
address.
Much valuable input from deraadt@, guenther@, tedu@
OK tedu@ deraadt@
|
|
pool hasnt had pool_setipl called.
ok kettenis@ ages ago
|
|
|
|
flag if the falloc() fails
reported by Carlin Bingham (cb (at) viennan.net)
ok deraadt@ tedu@
|
|
dynamic clamping mechanism. In the (new? has it already been 20 years?)
world of tty ring buffers, c_cn is the maximum...
There could be some ugly limit elsewhere, which may cause a deadlock
(dug as deep as my patience allows), so please report any sort
of new console or xterm issues that show up, such as tty lockups or high
cpu utilization..
|
|
|
|
hope don't happen. also, always check for errors. ok deraadt
|
|
|
|
kernel struct vnode defintion, and the only consumer (pstat) still needs
kvm to read much of the required information. no great loss to always use
kvm until there's a better replacement interface.
ok deraadt millert uebayasi
|
|
ok miod@
|
|
Regression spotted by tobiasu@.
XXX I wonder if the page zeroing thread shouldn't perform explicit
XXX pmap_update(pmap_kernel()) calls after each page zeroing... but that
XXX might not be enough.
|
|
|
|
to include that than rdnvar.h. ok deraadt dlg
|
|
|
|
vmcmd_map_zero() just returns the result of uvm_map(), so make it a tail call
|
|
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
|
|
in ptsignal(), which broke ptrace() in various circumstances, act more like
sigsuspend() by updating the signal mask and picking off waited for signals
when one occurs. Don't always restart when an unwaited-for-but-handled
signal occurs, as that screws with both timeout calculation and cancellation.
main problem noted by jmatthew@
ok tedu@
|
|
us handle the slowdown where we already give up pr_mtx and gets rid of
an ugly goto.
ok tedu@ who i think has more tweaks coming
|
|
|
|
has been added to the pool, else it doesn't help because the memory isn't
available. lost in locking rework.
tested blambert sthen
|
|
situations where e.g. web browsing is cpu intense but intermittently idle.
subject to further refinement and tuning.
|
|
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@
|
|
|
|
|
|
|
