summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove GLOBAL -- it has moved to Ports.obrien2000-10-1583-15250/+0
| | | | Approved by: unanimous response on arch@freebsd.org (June time frame)
* Change the "in use" percentage metric to actually display a realbmilekic2000-10-151-9/+14
| | | | "in use" percentage. In other words, show how much of mb_map is in use.
* While I'm here:bmilekic2000-10-151-1/+1
| | | | | Small change (remove tab in one of the MEXT* macros) - probably slipped through (accidently?) in dwmalone's KASSERT() addition (rev 1.58).
* Fix nullfs breakage caused by incomplete migration of v_interlock frombp2000-10-152-6/+10
| | | | | | simple_lock to mutex. Reset LK_INTERLOCK flag when interlock released manually.
* Add nmbcnt sysctl and make it tunable at boottime; nmbcnt is thebmilekic2000-10-151-1/+5
| | | | | | | | | | | | | number of ext_buf counters that are possibly allocatable. Do this because: (i) It will make it easier to influence EXT_COUNTERS for if_sk, if_ti (or similar) users where the driver allocates its own ext_bufs and where it is important for the mbuf system to take it into account when reserving necessary space for counters. (ii) Facilitate some percentile calculation for netstat(1)
* Fixed warnings.nyan2000-10-1514-51/+70
|
* Merged from sys/boot/i386/loader/main.c revision 1.21.nyan2000-10-151-10/+0
|
* I don't think we'll ever take any input (or send output) to aobrien2000-10-155-0/+15
| | | | Diamond Rio 500 MP3 player during an installation.
* Use rad_acct_open() instead of rad_auth_open().brian2000-10-151-1/+1
| | | | Suggested by: Victor Ivanov <v0rbiz@icon.bg>
* Don't define NOATM now that /usr/include/netnatm/ is created properly.brian2000-10-151-1/+0
|
* Redefine __word_swap_long, __byte_swap_long and __byte_swap_wordbrian2000-10-151-34/+31
| | | | | | | | as inline functions, renaming them to __uint16_swap_uint32, __uint8_swap_uint32 and __uint8_swap_uint16. Doing it properly suggested by: msmith Reviewed by: msmith
* Add /usr/include/netnatm/brian2000-10-151-0/+2
|
* Since -e and -r are right next to each other prompt before clobberingpaul2000-10-151-0/+10
| | | | a crontab you were planning to edit.
* Change the text for the ServerWorks north bridge chips. RCC is nowalc2000-10-142-8/+8
| | | | officially listed as ServerWorks by www.pcisig.com.
* Recognize the ServerWorks IB6566 south bridge.alc2000-10-141-0/+4
|
* Add another security configuration profile, call it "high" andjkh2000-10-149-3/+84
| | | | | | | rename the previous one to indicate that it's not just high, it's extreme (everything off, secure level raised). Submitted mostly by: Tony Finch <dot@dotat.at>
* Remove the HPFPLIB copyright which we have never used.phk2000-10-141-10/+1
|
* Remove even more unneeded #includes.phk2000-10-1413-280/+0
|
* Initial libc port for ia64.dfr2000-10-1445-0/+3022
|
* CSU code for ia64.dfr2000-10-141-0/+115
|
* Add a man page for part of the PRNG API.markm2000-10-142-1/+137
|
* Remove even more nneeded #includes.phk2000-10-149-188/+0
|
* Reseed the random device as early as possible to prevent hangs,markm2000-10-141-14/+25
| | | | | and provide some form of entropy in case there is no seed file to prevent a reboot from hanging unnecessarily.
* After some complaints about the dir names, the random device ismarkm2000-10-1415-1110/+147
| | | | | | | | | | | | | | | | | | | | now in dirs called sys/*/random/ instead of sys/*/randomdev/*. Introduce blocking, but only at startup; the random device will block until the first reseed happens to prevent clients from using untrustworthy output. Provide a read_random() call for the rest of the kernel so that the entropy device does not need to be present. This means that things like IPX no longer need to have "device random" hardcoded into thir kernel config. The downside is that read_random() will provide very poor output until the entropy device is loaded and reseeded. It is recommended that developers do NOT use the read_random() call; instead, they should use arc4random() which internally uses read_random(). Clean up the mutex and locking code a bit; this makes it possible to unload the module again.
* Duh! LINT is called NOTES these days.phk2000-10-143-0/+9
| | | | Make sure LINT checks profiling code as well.
* Fix compilation of profiled kernels by including <machine/lock.h>phk2000-10-141-0/+1
|
* Make it possible to specify profiling in the kernel config file.phk2000-10-148-6/+10
| | | | Do so for LINT.
* Document the ptrace() PT_STEP request.jwd2000-10-141-1/+10
| | | | | | | | Add references to the newly added hardware debug register support functions i386_clr_watch(3) and i386_set_watch(3). Reviewed by: Sean Eric Fagan <sef@kithrup.com> and no other response to the review request.
* Remove the signal value check from the PT_STEP codepath. Itjwd2000-10-141-1/+1
| | | | | | | can cause an bogus failure. Reviewed by: Sean Eric Fagan <sef@kithrup.com> and no other response to the review request.
* Initial commit of IFS - a inode-namespaced FFS. Here is a shortadrian2000-10-1413-7/+1345
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | description: How it works: -- Basically ifs is a copy of ffs, overriding some vfs/vnops. (Yes, hack.) I didn't see the need in duplicating all of sys/ufs/ffs to get this off the ground. File creation is done through a special file - 'newfile' . When newfile is called, the system allocates and returns an inode. Note that newfile is done in a cloning fashion: fd = open("newfile", O_CREAT|O_RDWR, 0644); fstat(fd, &st); printf("new file is %d\n", (int)st.st_ino); Once you have created a file, you can open() and unlink() it by its returned inode number retrieved from the stat call, ie: fd = open("5", O_RDWR); The creation permissions depend entirely if you have write access to the root directory of the filesystem. To get the list of currently allocated inodes, VOP_READDIR has been added which returns a directory listing of those currently allocated. -- What this entails: * patching conf/files and conf/options to include IFS as a new compile option (and since ifs depends upon FFS, include the FFS routines) * An entry in i386/conf/NOTES indicating IFS exists and where to go for an explanation * Unstaticize a couple of routines in src/sys/ufs/ffs/ which the IFS routines require (ffs_mount() and ffs_reload()) * a new bunch of routines in src/sys/ufs/ifs/ which implement the IFS routines. IFS replaces some of the vfsops, and a handful of vnops - most notably are VFS_VGET(), VOP_LOOKUP(), VOP_UNLINK() and VOP_READDIR(). Any other directory operation is marked as invalid. What this results in: * an IFS partition's create permissions are controlled by the perm/ownership of the root mount point, just like a normal directory * Each inode has perm and ownership too * IFS does *NOT* mean an FFS partition can be opened per inode. This is a completely seperate filesystem here * Softupdates doesn't work with IFS, and really I don't think it needs it. Besides, fsck's are FAST. (Try it :-) * Inodes 0 and 1 aren't allocatable because they are special (dump/swap IIRC). Inode 2 isn't allocatable since UFS/FFS locks all inodes in the system against this particular inode, and unravelling THAT code isn't trivial. Therefore, useful inodes start at 3. Enjoy, and feedback is definitely appreciated!
* Pre-IFS commit. Commit IFS-aware fsck and mount utilities.adrian2000-10-1410-302/+37
| | | | | | | | | | | | | | | | | | | mount_ifs: repocopy of sbin/mount, with most of the intelligence ripped out and "ufs" replaced with "ifs" in the right places. It will only mount a single filesystem, rather than the -t <type> magic that our real mount does. fsck_ifs: repocopy of sbin/fsck_ffs, but the directory structure stuff (pass2 and some refcount checks) has been #ifdef'ed out. src/sbin/Makefile: Build these two utilities There is probably cruft code left in both which can be removed at a later date, especially in mount_ifs, but I trust that people will not try mount_ifs -a .. Note: there are no man pages installed for these two commands as I haven't actually written them yet.
* Whoops, add the 'twe' files.msmith2000-10-141-0/+2
| | | | Submitted by: Chris Faulhaber <jedgar@fxp.org>
* Clean up a few things in dc_setcfg() pointed out to be me bywpaul2000-10-142-8/+18
| | | | aaron@openbsd.com on IRC earlier today.
* Look at both the vendor and subvendor information when determiningjlemon2000-10-131-32/+25
| | | | | | | whether this is a Smart Array. This fixes a problem where the driver would incorrectly match a Dell RAID device. Reviewed by: msmith
* Enable _PTHREADS_INVARIANTS until the recent libc_r changes aredeischen2000-10-133-3/+3
| | | | shaken out.
* Adjust to reflect recent changes in the internal layout of a structdeischen2000-10-131-26/+46
| | | | | | pthread in libc_r. Reviewed by: dfr
* Implement zero system call thread switching. Performance ofdeischen2000-10-1377-3389/+5243
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | thread switches should be on par with that under scheduler activations. o Timing is achieved through the use of a fixed interval timer (ITIMER_PROF) to count scheduling ticks instead of retrieving the time-of-day upon every thread switch and calculating elapsed real time. o Polling for I/O readiness is performed once for each scheduling tick instead of every thread switch. o The non-signal saving/restoring versions of setjmp/longjmp are used to save and restore thread contexts. This may allow the removal of _THREAD_SAFE macros from setjmp() and longjmp() - needs more investigation. Change signal handling so that signals are handled in the context of the thread that is receiving the signal. When signals are dispatched to a thread, a special signal handling frame is created on top of the target threads stack. The frame contains the threads saved state information and a new context in which the thread can run. The applications signal handler is invoked through a wrapper routine that knows how to restore the threads saved state and unwind to previous frames. Fix interruption of threads due to signals. Some states were being improperly interrupted while other states were not being interrupted. This should fix several PRs. Signal handlers, which are invoked as a result of a process signal (not by pthread_kill()), are now called with the code (or siginfo_t if SA_SIGINFO was set in sa_flags) and sigcontext_t as received from the process signal handler. Modify the search for a thread to which a signal is delivered. The search algorithm is now: o First thread found in sigwait() with signal in wait mask. o First thread found sigsuspend()'d on the signal. o Current thread if signal is unmasked. o First thread found with signal unmasked. Collapse machine dependent support into macros defined in pthread_private.h. These should probably eventually be moved into separate MD files. Change the range of settable priorities to be compliant with POSIX (0-31). The threads library uses higher priorities internally for real-time threads (not yet implemented) and threads executing signal handlers. Real-time threads and threads running signal handlers add 64 and 32, respectively, to a threads base priority. Some other small changes and cleanups. PR: 17757 18559 21943 Reviewed by: jasone
* Remember to assign an_dev to device_t before calling an_attach().wpaul2000-10-133-0/+13
|
* savectx() is now used exclusively by the crash dump system. Move thepeter2000-10-134-3/+9
| | | | | i386 specific gunk (copy %cr3 to the pcb) from the MI dumpsys() to the MD savectx().
* Convert the Aironet driver to use mutexes instead of spls.wpaul2000-10-134-28/+59
|
* Do not allocate a callout for all crashdumps, not just when you panic.ps2000-10-133-2/+4
|
* Update the wi driver to use mutexes instead of spls.wpaul2000-10-134-36/+86
|
* Add #include <machine/mutex.h> since these files need it and don'twpaul2000-10-134-0/+4
| | | | | include anything else that includes mutex.h. Needed to resolve struct mtx from struct dc_softc.
* Make mutex name reflect device driver name.cp2000-10-132-2/+4
| | | | | Destroy mutex when detaching the device. Submitted by: John Baldwin <jhb@FreeBSD.ORG>
* Use device_get_nameunit(dev) as the mutex string when callingwpaul2000-10-1318-49/+70
| | | | | mtx_init() instead of hard-coded string constant. Also remember to do the mutex changes to the ste driver, which I forgot in the first commit.
* o Introduce cap_from_text() and cap_to_text() implementations.rwatson2000-10-134-2/+1146
| | | | | | Reviewed by: green Obtained from: TrustedBSD Project Security audited by: imp, green
* First round of converting network drivers from spls to mutexes. Thiswpaul2000-10-1332-399/+788
| | | | | | | | takes care of all the 10/100 and gigE PCI drivers that I've done. Next will be the wireless drivers, then the USB ones. I may pick up some stragglers along the way. I'm sort of playing this by ear: if anyone spots any places where I've screwed up horribly, please let me know.
* o Simplify capability types away from an array of ints to a singlerwatson2000-10-136-88/+107
| | | | | | | | | | | | | | | | | | u_int64_t flag field, bounding the number of capabilities at 64, but substantially cleaning up capability logic (there are currently 43 defined capabilities). o Heads up to anyone actually using capabilities: the constant assignments for various capabilities have been redone, so any persistent binary capability stores (i.e., '$posix1e.cap' EA backing files) must be recreated. If you have one of these, you'll know about it, so if you have no idea what this means, don't worry. o Update libposix1e to reflect this new definition, fixing the exposed functions that directly manipulate the flags fields. Obtained from: TrustedBSD Project
* Do not override BINDIR settings from subdirectory Makefiles.gshapiro2000-10-131-1/+1
| | | | Submitted by: bde
* Note on the last commit that the problem was actually in the secure versiongshapiro2000-10-130-0/+0
| | | | | | but bde recommended explicitly setting BINDIR in both Makefiles. Submitted by: bde
OpenPOWER on IntegriCloud