summaryrefslogtreecommitdiffstats
path: root/sys/miscfs/procfs/procfs_cmdline.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Actually remove the procfs filesguenther2014-09-081-186/+0
|
* add a size argument to free. will be used soon, but for now default to 0.tedu2014-07-121-4/+4
| | | | after discussions with beck deraadt kettenis.
* decouple struct uvmexp into a new file, so that uvm_extern.h and sysctl.hderaadt2014-07-081-2/+1
| | | | | don't need to be married. ok guenther miod beck jsing kettenis
* Track whether a process is a zombie or not yet fully built via flagsguenther2014-07-041-4/+5
| | | | | | | | | | | PS_{ZOMBIE,EMBRYO} on the process instead of peeking into the process's thread data. This eliminates the need for the thread-level SDEAD state. Change kvm_getprocs() (both the sysctl() and kvm backends) to report the "most active" scheduler state for the process's threads. tweaks kettenis@ feedback and ok matthew@
* Add PS_EXITING to better differentiate between the process exiting andguenther2012-03-101-2/+2
| | | | the main thread exiting. c.f. regress/sys/kern/main-thread-exited/
* same vmspace song and dance as in kern_sysctl.c 1.167; ok kurtderaadt2008-11-101-6/+8
|
* ansify/de-register.jasper2007-06-181-6/+2
| | | | no binary change
* Kernel stack can be swapped. This means that stuff that's on the stackmiod2006-11-291-3/+1
| | | | | | | | | | should never be referenced outside the context of the process to which this stack belongs unless we do the PHOLD/PRELE dance. Loads of code doesn't follow the rules here. Instead of trying to track down all offenders and fix this hairy situation, it makes much more sense to not swap kernel stacks. From art@, tested by many some time ago.
* Replace procfs_domem() with a similar interface, process_domem(), which livesmiod2005-12-111-2/+2
| | | | | | | out of procfs and gets a ptrace request PT_{READ,WRITE}_{I,D} as argument; also procfs_checkioperm() becomes process_checkioperm(). From art@ some time ago; ok kettenis@ pedro@
* Add an extra flags argument to uvm_io(), to specify whether we want to fixmiod2005-11-041-4/+4
| | | | | | | | | the protection of the memory mapping we're doing I/O on, or if we want to leave them as they are. This should only be necessary for breakpoint insertion in code, so we'll only use it for ptrace requests. Initially from art@ after discussion with kettenis@ millert@ and I, tested by many.
* make sure uio_offset is a safe value, with suggestions from millert@tedu2004-05-051-4/+3
| | | | | ok deraadt@ millert@ problem noticed by deprotect.com
* Replace inclusion of <vm/foo.h> with the correct <uvm/bar.h> when necessary.miod2001-11-061-3/+1
| | | | (Look ma, I might have broken the tree)
* Remove old vm.art2001-06-271-23/+1
|
* Add procfs/cmdline; to help with linux emulation.jasoni2000-08-121-0/+215
From NetBSD.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.