summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ciss doesn't like scsi SYNC CACHE. turn it offps2003-12-081-0/+8
|
* Forced commit:imp2003-12-080-0/+0
| | | | | | Last commit moved info about the aha-1640 card. It also added notes about the fact that the A card is busted (and likely will never be fixed) and the B card doesn't work well on heavy load.
* Add the meteor driver man page back. It has moved up a level from theimp2003-12-083-5/+886
| | | | | | | | | | | | man4.i386. It documents that meteor no longer works, but keeps the extensive documentation on the meteor interface, which the bktr driver implements also. This should be merged into tha man page, but such a merging seems to be planned by others. # we really need something like video4bsd to define these sorts of # things for all video capture drivers. Requested by: rwatson and obrien
* Remove trailing whitespace.kan2003-12-081-7/+7
|
* Diff to vendor reduction.obrien2003-12-081-0/+1
|
* The last argument to mtx_init() should be MTX_DEF, not 0. This is not atruckman2003-12-082-5/+10
| | | | functional change since MTX_DEF happens to be defined as 0.
* The last argument to mtx_init() should be MTX_DEF, not 0. This is not atruckman2003-12-082-2/+2
| | | | functional change since MTX_DEF happens to be defined as 0.
* Addendum to revision 1.174: In the case where vm_pager_allocate() is calledalc2003-12-081-2/+6
| | | | | | | to create a vnode-backed object, the vnode lock must be held by the caller. Reported by: truckman Discussed with: kan
* Copy the old dgb man page to digi.4, plus very minor hacking. Add aimp2003-12-082-0/+383
| | | | | | note that says that this man page is sub-optimal. Bruce Mah should be happier about this, but someone that groks the cards supported by the digi driver is encouraged to make this man page suck less.
* Lock and unlock sched_lock when walking through thread list, current wedavidxu2003-12-071-1/+11
| | | | | insert kse upcall thread into thread list at mi_switch time, process lock is not enough.
* Correct usage of mtx_init() API. This is not a functional change sincetruckman2003-12-071-1/+1
| | | | | | the code happened to work because MTX_DEF and NULL are both defined as 0. Reviewed by: phk
* Correct usage of mtx_init() API. This is not a functional change sincetruckman2003-12-072-3/+3
| | | | | | the code happened to work because MTX_DEF and NULL are both defined as 0. Reviewed by: phk
* Try a little harder to catch when fixate finishes.sos2003-12-071-2/+4
| | | | | On the <QSI CD-RW/DVD-ROM SBW-242> that failed causing burncd to wait forever...
* Urk, add arch attributes to items from my previous commit.bmah2003-12-072-8/+8
|
* Style changetrhodes2003-12-072-2/+2
|
* New release notes: Record the demise of the lmc, dgb, hea, meteor,bmah2003-12-072-6/+28
| | | | and loran drivers.
* Don't remove the virtual-to-physical mapping when an sf_buf is freed.alc2003-12-072-9/+11
| | | | | | | | | | | | | | | Instead, allow the mapping to persist, but add the sf_buf to a free list. If a later sendfile(2) or zero-copy send resends the same physical page, perhaps with the same or different contents, then the mapping overhead is avoided and the sf_buf is simply removed from the free list. In other words, the i386 sf_buf implementation now behaves as a cache of virtual-to-physical translations using an LRU replacement policy on inactive sf_bufs. This is similar in concept to a part of http://www.cs.princeton.edu/~yruan/debox/ patch, but much simpler in implementation. Note: none of this is required on alpha, amd64, or ia64. They now use their direct virtual-to-physical mapping to avoid any emphemeral mapping overheads in their sf_buf implementations.
* The lmc, meteor, and loran drivers have been removed from the sourcebmah2003-12-072-20/+8
| | | | | | | | tree, so remove them from the hardware notes. The dgb driver has been replaced by the digi driver. The hea driver has been replaced by the en driver.
* Bump various entities for 5.2-CURRENT, trim release notes and errata.bmah2003-12-074-1620/+34
|
* Pass MTX_DEF as the last argument to mtx_init() instead of 0. Thistruckman2003-12-072-3/+3
| | | | | is not a functional change. The code happened to work properly only because MTX_DEF is defined as 0.
* bandaid LOR in rt_setgate; a proper fix requires code refactoringsam2003-12-071-4/+7
|
* add install rulesam2003-12-072-0/+11
|
* o report 0 instead of -1 for xmit rate when in transitionsam2003-12-071-4/+39
| | | | | o report rssi in running display o futz with column widths in running display
* fix commentsam2003-12-071-1/+1
|
* The uuidgen(1) program is WARNS=6 clean, so flag it as such.mux2003-12-072-2/+2
| | | | Tested on: i386, sparc64
* Change the definition of NULL on ia64 (for LP64 compilations) frommarcel2003-12-0714-50/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | an int constant to a long constant. This change improves consistency in the following two ways: 1. The first 8 arguments are always passed in registers on ia64, which by virtue of the generated code implicitly widens ints to longs and allows the use of an 32-bit integral type for 64-bit arguments. Subsequent arguments are passed onto the memory stack, which does not exhibit the same behaviour and consequently do not allow this. In practice this means that variadic functions taking pointers and given NULL (without cast) work as long as the NULL is passed in one of the first 8 arguments. A SIGSEGV is more likely the result if such would be done for stack-based arguments. This is due to the fact that the upper 4 bytes remain undefined. 2. All 64-bit platforms that FreeBSD supports, with the obvious exception of ia64, allow 32-bit integral types (specifically NULL) when 64-bit pointers are expected in variadic functions by way of how the compiler generates code. As such, code that works correctly (whether rightfully so or not) on any platform other than ia64, may fail on ia64. To more easily allow tweaking of the definition of NULL, this commit removes the 12 definitions in the various headers and puts it in a new header that can be included whenever NULL is to be made visible. This commit fixes GNOME, emacs, xemacs and a whole bunch of ports that I don't particularly care about at this time...
* Add a manual page for the consolidated debugging commit.scottl2003-12-072-0/+77
|
* Simplify the contexts created by the kernel and remove the relatedmarcel2003-12-074-56/+41
| | | | | | | | | flags. We now create asynchronous contexts or syscall contexts only. Syscall contexts differ from the minimal ABI dictated contexts by having the scratch registers saved and restored because that's where we keep the syscall arguments and syscall return values. Since this change affects KSE, have it use kse_switchin(2) for the "new" syscall context.
* Make the DIAGNOSTIC code which complains about long {call|time}out(9)phk2003-12-071-5/+11
| | | | | | functions less noisy: We printf if a new function took longer than the previous record holder, or of the previous record holder took more than twice as long as the current record.
* Regen due to kse_switchin(2).marcel2003-12-075-7/+17
|
* Add kse_switchin(2). This syscall can be used by KSE implementationsmarcel2003-12-074-0/+51
| | | | | | | | to have the kernel switch to a new thread, instead of doing it in userland. It is in fact needed on ia64 where syscall restarts do not return to userland first. It's completely handled inside the kernel. As such, any context created by the kernel as part of an upcall and caused by some syscall needs to be restored by the kernel.
* Finish the transition from libkvm to sysctl that I started a while ago.des2003-12-073-118/+249
| | | | | | | | | The use of libkvm for post-mortem analysis is still supported (though it could use more testing). We can now remove vmstat's setgid bit. While I'm here, hack the interrupt listing code to not display interrupts that haven't occurred unless the -a option was given on the command line, and document this change.
* Log all results to a history file in the log directory.des2003-12-071-0/+38
|
* Constify, and add an API function to find a named node in a directory.des2003-12-072-6/+21
|
* Minor whitespace and style issues.des2003-12-077-21/+16
|
* Use mp_ncpus instead of the hw.ncpu sysctl.des2003-12-071-22/+11
|
* Remove useless SMP check code.des2003-12-072-22/+0
|
* Forced commit: previous log entry should have said "fix some warnings anddes2003-12-070-0/+0
| | | | style issues, no functional changes"
* Use WARNS level 2 instead of setting CFLAGS explicitly to -Wall.des2003-12-072-22/+22
|
* Print out the file system access statistics using uintmax_t typesiedowse2003-12-071-4/+7
| | | | | | instead of casting the unsigned 64-bit values to longs. Suggested by: bde
* MFR: Bump manpages revision to 5.2.ru2003-12-071-1/+1
|
* Add support for timeout: and attempts: resolver options.murray2003-12-073-1/+37
| | | | | Submitted by: Paul Vixie <paul@vix.com> / ISC MFC After: 1 week
* use callout_*() rather than timeout().ume2003-12-071-2/+5
|
* link-local multicast address must be converted to KAME specificume2003-12-071-1/+1
| | | | | | | embeded scopeid form. Reported by: dwmalone MFC after: 3 days
* KASSERT against multiple orphanings of providers.phk2003-12-072-0/+5
|
* A too good Feynman quote to pass up.phk2003-12-071-0/+4
|
* rqb_bits[] may be an int64_t (eg: on alpha, and recently on amd64).peter2003-12-071-1/+1
| | | | | | | Be sure to shift (long)1 << 33 and higher, not (int)1. Otherwise bad things happen(TM). This is why beast.freebsd.org paniced with ULE. Reviewed by: jeff
* Add PowerPC CFLAGS.obrien2003-12-071-0/+9
| | | | Submitted by: gallatin
* Add IPv6 support to pppctl by using getaddrinfo() and trying each addresstjr2003-12-071-89/+115
| | | | | | | it returns. This allows it to connect to the server side again, which has been listening on IPv6 addresses exclusively for more than 2 years. PR: 59369
* Update to reflect eni removalimp2003-12-074-442/+1
|
OpenPOWER on IntegriCloud