summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Implement PAL_HALT_LIGHT now that the kernel halts the processormarcel2003-11-092-0/+18
| | | | when idle. All we have to do is return.
* Do not strip skiload when installed. The stripped binary does not loadmarcel2003-11-092-0/+2
| | | | in the simulator.
* - Rename vm_map_clean() to vm_map_sync(). This better reflects the factalc2003-11-095-61/+78
| | | | | | | | | | that msync(2) is its only caller. - Migrate the parts of the old vm_map_clean() that examined the internals of a vm object to a new function vm_object_sync() that is implemented in vm_object.c. At the same, introduce the necessary vm object locking so that vm_map_sync() and vm_object_sync() can be called without Giant. Reviewed by: tegge
* Port truss(1) to 64-bit architectures:marcel2003-11-0911-113/+84
| | | | | | | | | | | | | | | | | | o Syscall return values do not fit in int on 64-bit architectures. Change the type of retval in <arch>_syscall_exit() to long and change the prototype of said function to return a long as well. o Change the prototype of print_syscall_ret() to take a long for the return address and change the format string accordingly. o Replace the code sequence tmp = malloc(X); sprintf(tmp, format, ...); with X by definition too small on 64-bit platforms by asprintf(&tmp, format, ...); With these changes the output makes sense again, although it does mess up the tabulation on ia64. Go widescreen... Not tested on: alpha, sparc64.
* Sprinkle GIANT_REQUIRED asserts around the xpt layer to aid with locking thescottl2003-11-091-0/+58
| | | | SCSI drivers.
* Update list of supported devices for ahbimp2003-11-091-1/+2
|
* Complete the variants of 1522/1520 cardsimp2003-11-091-2/+3
|
* AHA-1505 also alegedly supportedimp2003-11-091-2/+2
|
* Flesh out the list of supported devices for this driver.imp2003-11-091-3/+15
| | | | | | Add bugs that describe the current state of this driver. # Note: Don't ask me about the driver: I can't get it to work well either :-)
* o Update to closer to the official names for these cards.imp2003-11-091-9/+21
| | | | | | | | o Remove entries for 1510, 152x and 1535. These are supported, for some value of supported, by the aic driver. o Add notes about 1542-CP being plug and play, but it can still conflict with other resources because all the resources it uses are set with the onboard BIOS.
* Alternate version of rev 1.20.obrien2003-11-091-1/+1
| | | | | | | Comment out rather than totally remove the ipfilter pieces that we need reconnected some day. This is now only ipnat as it is for configuring NAT. ipfstat is meant for reporting statistics/filter lists. For /rescue it is enough to configure lists but not view the installed ones.
* Make this driver a little more style(9) compliantimp2003-11-094-206/+176
|
* Synchronize list of supported cards with hardware notes, reformatbmah2003-11-091-5/+20
| | | | as a bullet list.
* If a thread in critical region got a synchronous signal, according currentdavidxu2003-11-092-0/+4
| | | | | | signal handling mode, there is no chance to handle the signal, something must be wrong in the library, just call kse_thr_interrupt to dump its core. I have the code for a long time, but forgot to commit it.
* Mention Olicom OC2220, which is listed in the hardware notes andbmah2003-11-091-0/+1
| | | | driver source.
* Capitalize "Fast Ethernet" and "Ethernet" consistently.bmah2003-11-091-7/+7
|
* Synchronize manual page with hardware notes and reformat list ofbmah2003-11-091-4/+21
| | | | supported devices.
* replace explicit changes to rt_refcnt by RT_ADDREF and RT_REMREFsam2003-11-0812-36/+48
| | | | | | | macros that expand to include assertions when the system is built with INVARIANTS Supported by: FreeBSD Foundation
* Remove the atkbd, psm, sc and vga devices. Most ia64 boxes out theremarcel2003-11-082-16/+0
| | | | | | | | | | | | are zx1 based machines and they don't particularly like it when we poke at them with PC legacy code. The atkbd and psm devices were disabled in the hints file so that one could enable them on machines that support legacy devices, but that's not really something you can expect from a first-time installer. This still leaves syscons (sc) and the vga device, which were enabled by default and wrecking havoc anyway. We could disable them by default like the atkbd and psm devices, but there's really no point in pretending we're in a better shape that way.
* Trim device entries for an(4), ray(4), and awi(4).bmah2003-11-082-96/+2
|
* divert socket fixups:sam2003-11-083-16/+75
| | | | | | | | | | | | o pickup Giant in divert_packet to protect sbappendaddr since it can be entered through MPSAFE callouts or through ip_input when mpsafenet is 1 o add missing locking on output o add locking to abort and shutdown o add a ctlinput handler to invalidate held routing table references on an ICMP redirect (may not be needed) Supported by: FreeBSD Foundation
* assert optional inpcb is passed in lockedsam2003-11-081-0/+2
| | | | Supported by: FreeBSD Foundation
* add locking assertionssam2003-11-081-4/+29
| | | | Supported by: FreeBSD Foundation
* assert inpcb is locked in udp_outputsam2003-11-081-0/+1
| | | | Supported by: FreeBSD Foundation
* o correct locking problem: the inpcb must be held across tcp_respondsam2003-11-084-36/+46
| | | | | | | o add assertions in tcp_respond to validate inpcb locking assumptions o use local variable instead of chasing pointers in tcp_respond Supported by: FreeBSD Foundation
* use local values instead of chasing pointerssam2003-11-081-3/+2
| | | | Supported by: FreeBSD Foundation
* replace mtx_assert by INP_LOCK_ASSERTsam2003-11-081-3/+1
| | | | Supported by: FreeBSD Foundation
* add some missing lockingsam2003-11-081-17/+75
| | | | Supported by: FreeBSD Foundation
* the sbappendaddr call in socket_send must be protected by Giantsam2003-11-081-0/+3
| | | | | | because it can happen from an MPSAFE callout Supported by: FreeBSD Foundation
* add locking assertions that turn into noops if INET6 is configured;sam2003-11-081-0/+17
| | | | | | | this is necessary because the ipv6 code shares the in_pcb code with ipv4 but (presently) lacks proper locking Supported by: FreeBSD Foundation
* Mention Cisco and Xircom devices supported by an driver.bmah2003-11-081-4/+14
|
* o add a flags parameter to netisr_register that is used to specifysam2003-11-0817-57/+81
| | | | | | | | | | | | | | | | whether or not the isr needs to hold Giant when running; Giant-less operation is also controlled by the setting of debug_mpsafenet o mark all netisr's except NETISR_IP as needing Giant o add a GIANT_REQUIRED assertion to the top of netisr's that need Giant o pickup Giant (when debug_mpsafenet is 1) inside ip_input before calling up with a packet o change netisr handling so swi_net runs w/o Giant; instead we grab Giant before invoking handlers based on whether the handler needs Giant o change netisr handling so that netisr's that are marked MPSAFE may have multiple instances active at a time o add netisr statistics for packets dropped because the isr is inactive Supported by: FreeBSD Foundation
* Add /usr/share/security to reflect recent hookup of Makefile andrwatson2003-11-081-0/+3
| | | | | | mtree entry for share/security/lomac-policy.contexts. Pointed out by: ru
* Makefile.inc wasn't needed; this is a left-over of other files presentrwatson2003-11-082-3/+1
| | | | | | | | in share/security in the trustedbsd_sebsd branch that are not present in the main tree. Also, .include Makefile.inc from the parent directory so that BINDIR is set right. Pointed out by: bde
* If available, also print the lomac label by default for processes, files,rwatson2003-11-081-3/+3
| | | | | | | and interfaces. This avoids the need to manually add these when setting up LOMAC. Pointed out by: tjr
* Trim the following device sections and refer to device lists inbmah2003-11-082-382/+6
| | | | | | | | | | manpages: ahd(4), mly(4), vpo(4), rl(4), bktr(4), uscanner(4). Tweak mlx(4) entry slightly. Also trim USB hubs, ukbd(4) and ums(4). We can't seriously expect a device list for these classes of devices that is inclusive enough to be useful to anybody.
* Remove trailing commas from device list.bmah2003-11-081-3/+3
|
* Add SOHO(PRAGMATIC) UE-1211C from the pc98 hardware notes.bmah2003-11-081-0/+2
|
* Capitalize "Ethernet" and "Fast Ethernet" consistently. No otherbmah2003-11-081-5/+5
| | | | content changes.
* Sort devices. In the process, remove a duplicate entry for the Acctonbmah2003-11-081-25/+23
| | | | EN1207D. No other content changes.
* People are blindly coping this example refuse file. Doing so breaksgshapiro2003-11-082-6/+3
| | | | | | | | | buildworld as src/etc/sendmail/freebsd.mc is missing. That example was added 3 years ago, before the /etc/mail/ infrastructure was in place for customized configurations. It is time to remove this example. Noticed by: Robert Gray <bob@boulderlabs.com> in freebsd-stable MFC after: 1 day
* Move post dmamap_load processes into the callback function.simokawa2003-11-081-19/+20
|
* Cross-reference pgfind(9) and pfind(9) from each others manual pages.jkoshy2003-11-082-0/+4
|
* I've had a couple of reports that the Sony Clie_40 doesn't need thejoe2003-11-081-1/+1
| | | | | | | | | | | | | PALM_4 initialisation hack. I've not confirmed it myself, but seeing as we already don't use it for the Sony Clie_41, let's drop it from the Clie_40 also and see what happens. (Question: What about the Clie_S360 and Clie_NX60 devices? Do we need to drop Palm4 from those as well? Possibly, but I've not had any reports about those so I don't know.) PR: kern/56575 MFC after: 3 days
* Don't be so chatty when performing manual sense. This should make ATAPICAMscottl2003-11-081-2/+2
| | | | devices a lot more quiet.
* Add manpage link wd.4 -> wdc.4rushani2003-11-082-1/+3
|
* Remove the NOGIANT flag again, it was premature.sos2003-11-081-1/+1
|
* 1. Fixed leakage of a file descriptor for every non-fatal failure inbde2003-11-081-1/+3
| | | | | | | | | | | | | | | rm_overwrite() (for rm -P). 2. Print the file name in the error message for (fatal) malloc() failures in rm_overwrite(). I first thought that malloc() failures should be non-fatal since they don't prevent proceeding the the next file, but making them non-fatal would normally give too much output for rm -Pr on a large tree in the unlikely event that even one occurs, since the malloc()ed amounts are usually the same. Just print the file name since the malloc()ed amounts are not always the same and it doesn't hurt to know where rm was when it quit. Submitted by: guido ((1) and original version of (2))
* Move a MD 32 bit binary support routine into the MD areas. exec_setregspeter2003-11-083-45/+43
| | | | | | | is highly MD in an emulation environment since it operates on the host environment. Although the setregs functions are really for exec support rather than signals, they deal with the same sorts of context and include files. So I put it there rather than create yet another file.
* Regenpeter2003-11-084-7/+7
|
OpenPOWER on IntegriCloud