summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Use humanize_number(3) to format sizes into a human readable form.pjd2004-05-244-157/+30
|
* Add humanize_number(3) to libutil for formating numbers into a humanpjd2004-05-244-4/+312
| | | | | | readable form. Obtained from: NetBSD
* Mark du(1) as WARNS6 clean.pjd2004-05-241-0/+1
| | | | Tested on: alpha, amd64, i386, ia64, sparc64
* Use NG_NODESIZ instead of (NG_NODELEN + 1)julian2004-05-241-1/+1
| | | | Noted by: jhb
* Use NG_HOOKSIZ instead of the deprecated (NG_HOOKLEN + 1)julian2004-05-241-1/+1
|
* Use PCI_BAR() rather than PCIR_MAPS.jhb2004-05-241-5/+5
| | | | Noticed by: phk
* Wrap the code to save/restore PCI config registers on suspend/resume injhb2004-05-243-0/+18
| | | | | | #ifndef BURN_BRIDGES. Noticed by: phk
* Change a if (...) panic() to a KASSERT().mux2004-05-241-2/+2
|
* Use PCI_BAR() in preference to PCI_MAPS + x * 4.imp2004-05-241-2/+2
| | | | Submitted by: jhb
* Grammar.maxim2004-05-241-1/+1
|
* Don't declare spectHex() inside a function, use a real prototype.stefanf2004-05-241-1/+2
| | | | Approved by: das (mentor)
* Use the correct types for the functions rst_opendir(), glob_readdir() andstefanf2004-05-243-9/+11
| | | | | | | rst_closedir() which are called by glob(). Reviewed by: md5 Approved by: das (mentor)
* Include <timeconv.h> for time conversion functions.stefanf2004-05-242-0/+2
| | | | Approved by: das (mentor)
* Do not write to those config registers that are unambiguously definedimp2004-05-241-19/+0
| | | | | | | | | | | | | | | | | | | | | | | | in the various pci specifications as readonly. vendor, subvendor, device and subdevice are required to be loaded in hardware by some means that isn't the system BIOS or other system software (although some devices do have ways of accomplishing this). class and subclass are defined to be read-only in section 6.2.1 (v2.2). Apart from the status register, which we weren't touching, these are the only read-only registers I could find in the 2.2 spec. progif is also defined as being read-only in section 6.2.1. However, the PCI IDE programming document specifically states that some of the bits are read/write. Since we may have to restore registers before we have a driver attached, go ahead and restore this one byte when transitioning between D3 and D0. The PCI spec also says that writes to reserved and unimplemented registers must be completed normally. It makes no statements about writes to read-only registers, so be as conservative as possible, while covering the exception to the rule that is documented in a subpart of the standard. Requested by: socttl
* Revert part of rev 1.230 and assume that all EISA IRQs use active highjhb2004-05-241-8/+1
| | | | | | | | | polarity rather than assuming that level triggered IRQs use active low and edge triggered IRQs use active high. Both the MultiProcessor 1.4 and ACPI 2.0 Specifications state in their examples that level triggered EISA IRQs are active low, but in practice they seem to be active high. Reported by: Nik Azim Azam nskyline_r35 at yahoo dot com
* Install nsswitch.des2004-05-241-1/+1
|
* Include <sys/linker.h> for kldload().stefanf2004-05-241-0/+1
| | | | Approved by: das (mentor)
* Add option '-o' for one-line output in combination with '-d'.le2004-05-242-7/+24
| | | | | PR: bin/62911 (patch slightly adopted) Submitted by: Corris Randall <corris@line6.net>
* Include <stdlib.h> for exit() and abort() prototypes.stefanf2004-05-243-0/+3
| | | | Approved by: das (mentor)
* Include <string.h> for prototypes of various string functions.stefanf2004-05-245-0/+8
| | | | Approved by: das (mentor)
* Oops, ".align 4" for the data section in the previous commit shouldbde2004-05-241-3/+3
| | | | | have been ".p2align 4". This bug is cosmetic since the data section happens to be empty.
* Diff reduction to NetBSD.le2004-05-241-3/+3
| | | | | | | | | | MFNetBSD 1.21; author: itojun use bounded string op MFNetBSD 1.22; author: grant s/netbsd.org/NetBSD.org/i Obtained from: NetBSD
* Include <rpc/rpc_com.h> for a _rpc_dtablesize() prototype.stefanf2004-05-242-0/+2
| | | | Approved by: das (mentor)
* Fixed profiling of trap, syscall and interrupt handlers and somebde2004-05-244-9/+43
| | | | | | | | | | | | | | | ordinary functions, essentially by backing out half of rev.1.115 of amd64/exception.S. The handlers must be between certain labels for the purposes of profiling, and this was broken by scattering them in separately compiled .S files, especially for ordinary functions that ended up between the labels. Merge the files by #including them as before, except with different pathnames and better comments and organization. Changes to the scattered files are minimal -- just move the labels to the file that does the #includes. This also partly fixes profiling of IPIs -- all IPI handlers are now correctly classified as interrupt handlers, but many are still missing mcount calls.
* Include <netinet/in.h> for ntoh*() and hton*() prototypes.stefanf2004-05-245-0/+6
| | | | Approved by: das (mentor)
* If nsswitch.conf does not exist, create it with the default settings.des2004-05-241-7/+30
| | | | | | | The reason for doing this is that (at least some) 4.x binaries are very unhappy if host.conf does not exist, and if we create host.conf but not nsswitch.conf, nsswitch.conf will be created at the next reboot, so it is better to create a correct nsswitch.conf right away.
* Move the task of updating nsswitch.conf / host.conf into a separatedes2004-05-242-64/+108
| | | | script called nsswitch.
* Don't repeat the definition of IDTVEC(). It is in asmacros.h.bde2004-05-241-3/+0
|
* Remove another redundant if_output initialization.mux2004-05-241-1/+0
|
* Include <stdio.h> for a sprintf() prototype.stefanf2004-05-241-0/+2
| | | | Approved by: das (mentor)
* Fixed insertion sort error in previous commit (prof_machdep.c).bde2004-05-241-4/+4
| | | | | | Fixed apparently-intentional disorder of the crypto files. Lists of files should be sorted first on the pathname, not on the option name or subsystem.
* Include <stdlib.h> for exit() and add a prototype for yyparse().stefanf2004-05-241-0/+4
| | | | Approved by: das (mentor)
* drop packet which has ::1 as src or dst via other than lo0ume2004-05-241-0/+2
| | | | | | like as rc.firewall does. MFC after: 1 week
* Store the target handles in a separate list from normal commands. Add anjl2004-05-246-15/+125
| | | | | | CTIO fast post routine to handle CTIO completions. Submitted by: mjacob
* /usr is not really the ideal place for a ports application to storecjc2004-05-247-28/+28
| | | | | | | a frequently updated database. /var/db is a much more reasonable place for this kind of thing. Set a good example. Reviewed by: -arch
* Add support for BCM5705Kps2004-05-242-0/+3
| | | | | Submitted by: candy@kgc.co.jp PR: kern/67110
* The socket code upcalls into the NFS server using the so_upcallrwatson2004-05-247-84/+642
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mechanism so that early processing on mbufs can be performed before a context switch to the NFS server threads. Because of this, if the socket code is running without Giant, the NFS server also needs to be able to run the upcall code without relying on the presence on Giant. This change modifies the NFS server to run using a "giant code lock" covering operation of the whole subsystem. Work is in progress to move to data-based locking as part of the NFSv4 server changes. Introduce an NFS server subsystem lock, 'nfsd_mtx', and a set of macros to operate on the lock: NFSD_LOCK_ASSERT() Assert nfsd_mtx owned by current thread NFSD_UNLOCK_ASSERT() Assert nfsd_mtx not owned by current thread NFSD_LOCK_DONTCARE() Advisory: this function doesn't care NFSD_LOCK() Lock nfsd_mtx NFSD_UNLOCK() Unlock nfsd_mtx Constify a number of global variables/structures in the NFS server code, as they are not modified and contain constants only: nfsrvv2_procid nfsrv_nfsv3_procid nonidempotent nfsv2_repstat nfsv2_type nfsrv_nfsv3_procid nfsrvv2_procid nfsrv_v2errmap nfsv3err_null nfsv3err_getattr nfsv3err_setattr nfsv3err_lookup nfsv3err_access nfsv3err_readlink nfsv3err_read nfsv3err_write nfsv3err_create nfsv3err_mkdir nfsv3err_symlink nfsv3err_mknod nfsv3err_remove nfsv3err_rmdir nfsv3err_rename nfsv3err_link nfsv3err_readdir nfsv3err_readdirplus nfsv3err_fsstat nfsv3err_fsinfo nfsv3err_pathconf nfsv3err_commit nfsrv_v3errmap There are additional structures that should be constified but due to their being passed into general purpose functions without const arguments, I have not yet converted. In general, acquire nfsd_mtx when accessing any of the global NFS structures, including struct nfssvc_sock, struct nfsd, struct nfsrv_descript. Release nfsd_mtx whenever calling into VFS, and acquire Giant for calls into VFS. Giant is not required for any part of the operation of the NFS server with the exception of calls into VFS. Giant will never by acquired in the upcall code path. However, it may operate entirely covered by Giant, or not. If debug.mpsafenet is set to 0, the system calls will acquire Giant across all operations, and the upcall will assert Giant. As such, by default, this enables locking and allows us to test assertions, but should not cause any substantial new amount of code to be run without Giant. Bugs should manifest in the form of lock assertion failures for now. This approach is similar (but not identical) to modifications to the BSD/OS NFS server code snapshot provided by BSDi as part of their SMPng snapshot. The strategy is almost the same (single lock over the NFS server), but differs in the following ways: - Our NFS client and server code bases don't overlap, which means both fewer bugs and easier locking (thanks Peter!). Also means NFSD_*() as opposed to NFS_*(). - We make broad use of assertions, whereas the BSD/OS code does not. - Made slightly different choices about how to handle macros building packets but operating with side effects. - We acquire Giant only when entering VFS from the NFS server daemon threads. - Serious bugs in BSD/OS implementation corrected -- the snapshot we received was clearly a work in progress. Based on ideas from: BSDi SMPng Snapshot Reviewed by: rick@snowhite.cis.uoguelph.ca Extensive testing by: kris
* Support basename and path based constrained matches.mdodd2004-05-242-15/+71
| | | | | | | | | | | | | | | | | | eg: [foo] ... matches any executable 'foo' [/usr/bin/foo/] ... matches any executable under the directory /usr/bin/foo/ Exact matches continue to function as before. PR: bin/66769 Submitted-by: Dan Nelson
* Consult parent's if_capenable for active VLAN-related capabilities.yar2004-05-231-1/+8
| | | | | | | | | | This change is possible since all the relevant drivers have been fixed to set if_capenable properly. The field if_capabilities tracks supported capabilities, which may be disabled administratively. Inheriting checksum offload support from the parent interface isn't that easy because the checksumming capabilities of the parent may be toggled on the fly. Disable the code for now.
* Only initialize the if_sis callout as MPSAFE if debug.mpsafenet is setrwatson2004-05-231-1/+4
| | | | | | | true. Otherwise, assertion checks for Giant in the network stack will fail causing a panic. Reported by: simon
* Add the 'sid' info to the output of `ps -j', to make up for the 'sess'gad2004-05-232-2/+2
| | | | | | | (session-pointer) info which was dropped from `ps' earlier in 5.x. PR: bin/59423 Submitted by: Jilles Tjoelker
* Fix the kludge-old-options processing so `ps tpt' will be treated thegad2004-05-231-4/+5
| | | | | | | | same as `ps -tpt', instead of being changed into `ps -tpT'. PR: bin/52489 Submitted by: Jilles Tjoelker MFC after: 1 week
* A handler for ioctl(SIOCSIFCAP) should not alter a bit inyar2004-05-238-8/+17
| | | | | | | if_capenable unless the interface driver is actually able to toggle the respective capability on and off. Reviewed by: ru
* According to the design of checksum offloading framework,yar2004-05-231-2/+5
| | | | | if_hwassist should be in accord with the IFCAP_TXCSUM bit of if_capenable.
* Mark the VLAN_MTU capability as initially enabled since it'syar2004-05-232-0/+2
| | | | hardcoded to "ON" for these interfaces.
* Added profiling support for Xint0x80_syscall.bde2004-05-231-0/+2
|
* o Fix usage example.maxim2004-05-231-1/+1
| | | | | PR: docs/67065 Submitted by: David Syphers
* Don't try to copy out the result payload if there isn't one. This ioctldfr2004-05-231-6/+14
| | | | | interface really needs changing to split out the various async request types.
* Build prof_machdep.c if profiling.bde2004-05-231-0/+1
| | | | | | | | | | | | | Kernel profiling for amd64's (normal and high resolution) should now compile and work as (un)well as on i386's. It works better than user profiling because: - it uses _cyg_profile_func_*() instead of .mcount(), so it doesn't suffer from gcc misspelling .mcount as mcount. - it doesn't neglect saving %rax in .mcount(). The SMP case hasn't been tested. The high resolution subcase of this uses the i8254, and as on i386's, the locking for this is deficient and the i8254 is too inefficient. The acpi timer is also too inefficient.
* Build kgmon for amd64.bde2004-05-231-1/+1
|
OpenPOWER on IntegriCloud