summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Use bus_space functions rather than inb/outb.imp2001-05-245-20/+28
| | | | | | | Add defines for PCIC_INDEX and PCIC_DATA offsets. Change PCIC_INDEX_0 to PCIC_PORT_0 Add define for PCIC_NPORT. Document why the vadem probe works.
* Produce a config-time warning about EXT2FS and GPL_MATH_EMULATEpeter2001-05-242-2/+4
|
* Remove DEV_SNP -> opt_snp.hpeter2001-05-241-1/+0
| | | | Forgotten by: dd
* Do what we should have done a long time ago:imp2001-05-241-0/+10
| | | | | | | | | | | o If the class is PCIC_BRIDGE, subclass is PCIS_BRIDGE_PCMCIA and programming interface is 0, assume that it is a generic PCMCIA PCI chip we can program. I don't think there are any of these that we don't know about, but you never know. o If the class is PCIC_BRIDGE, subclass is PCIS_BRIDGE_CARDBUS and programming interface is 0, assume that it is a YENTA cardbus bridge that we know how to cope with. There are likely some cardbus bridges that haven't it made it in here yet.
* Move getb1 and putb1 from pcic_isa.c to pcic.c. Rename them toimp2001-05-243-22/+24
| | | | | | pcic_{get,put}b_io. There are some pci bridges (the CL-PD6729 and maybe others) that do not have memory mapped registers, so we'll need these in both places. Declare them in pcicvar.h.
* Spelling police: insure -> ensuredd2001-05-241-1/+1
| | | | | PR: 27600 Submitted by: Iain Templeton <iain@ugh.net.au>
* Use pw(8) instead of grep'ing through /etc/passwd. This fixesdd2001-05-241-3/+3
| | | | | | automatic filling of the "Originator" field for NIS users. PR: 24372
* Add snp_olddisc member to struct snoop; the linedisc'ized snp(4) uses this.dd2001-05-241-0/+1
| | | | Pointy hat to: dd
* Oops, forgot the 'u' in the getopt for the previous commit.dillon2001-05-242-2/+2
|
* Correct style bugs with regards to long lines and comments.dd2001-05-231-15/+22
| | | | Reviewed by: bde
* Build snp(4) as a module.dd2001-05-231-2/+2
|
* *sigh* We can't remove VINUMDEBUG entirely, since we include kernelgrog2001-05-231-3/+2
| | | | | header files and sources which depend on it. For userland, define VINUMDEBUG here. Also remove a now superfluous #ifdef.
* Remove cruft.grog2001-05-231-3/+0
|
* Change #if VINUMDEBUG to #ifdef VINUMDEBUG. This is a flag, not a variable.grog2001-05-238-31/+27
|
* define _KERNEL before including <sys/conf.h>phk2001-05-231-1/+1
|
* We don't need to include <sys/conf.h>phk2001-05-231-1/+0
|
* Don't acquire Giant just to call trap_fatal(), we are about to panicjhb2001-05-233-12/+0
| | | | | anyway so we'd rather see the printf's then block if the system is hosed.
* Don't release Giant around vm_oject_page_clean() in fsync() as the pagerjhb2001-05-232-4/+0
| | | | putpages called will need Giant.
* A feature to allow one to telnet to a unix domain socket. (MFC fromdillon2001-05-236-6/+102
| | | | | | | | | non-crypto version) Also update the crypto telnet's man page to reflect other options ported from the non-crypto version. Obtained from: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
* - Assert Giant is held in the vnode pager methods.jhb2001-05-231-14/+18
| | | | | - Lock the VM while walking down a vm_object's backing_object list in vnode_pager_lock().
* - Add in several asserts of vm_mtx.jhb2001-05-231-5/+42
| | | | | | | | | - Assert Giant in vm_pageout_scan() for the vnode hacking that it does. - Don't hold vm_mtx around vget() or vput(). - Lock Giant when calling vm_pageout_scan() from the pagedaemon. Also, lock curproc while setting the P_BUFEXHAUST flag. - For now we still hold Giant for all of the vm_daemon. When process limits are locked we will be only need Giant for swapout_procs().
* A feature to allow one to telnet to a unix domain socket.dillon2001-05-233-4/+44
| | | | Obtained from: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
* - Assert that the vm lock is held for all of _vm_object_allocate().jhb2001-05-231-31/+48
| | | | | | | | | | | | | | - Restore the previous order of setting up a new vm_object. The previous had a small bug where we zero'd out the flags after we set the OBJ_ONEMAPPING flag. - Add several asserts of vm_mtx. - Assert Giant is held rather than locking and unlocking it in a few places. - Add in some #ifdef objlocks code to lock individual vm objects when vm objects each have their own lock someday. - Don't bother acquiring the allproc lock for a ddb command. If DDB blocked on the lock, that would be worse than having an inconsistent allproc list.
* - Add lots of vm_mtx assertions.jhb2001-05-231-2/+39
| | | | | | | - Add a few KTR tracepoints to track the addition and removal of vm_map_entry's and the creation adn free'ing of vmspace's. - Adjust a few portions of code so that we update the process' vmspace pointer to its new vmspace before freeing the old vmspace.
* - Lock the VM around the pmap_swapin_proc() call in faultin().jhb2001-05-231-15/+16
| | | | | | | | | | | | | | | - Don't lock Giant in the scheduler() function except for when calling faultin(). - In swapout_procs(), lock the VM before the proccess to avoid a lock order violation. - In swapout_procs(), release the allproc lock before calling swapout(). We restart the process scan after swapping out a process. - In swapout_procs(), un #if 0 the code to bump the vmspace reference count and lock the process' vm structures. This bug was introduced by me and could result in the vmspace being free'd out from under a running process. - Fix an old bug where the vmspace reference count was not free'd if we failed the swap_idle_threshold2 test.
* - Fix the sw_alloc_interlock to actually lock itself when the lock isjhb2001-05-231-16/+20
| | | | | | | acquired. - Assert Giant is held in the strategy, getpages, and putpages methods and the getchainbuf, flushchainbuf, and waitchainbuf functions. - Always call flushchainbuf() w/o the VM lock.
* Assert Giant is held for the device pager alloc and getpages methods sincejhb2001-05-231-3/+3
| | | | we call the mmap method of the cdevsw of the device we are mmap'ing.
* Assert Giant is held by the caller rather than getting it and releasingjhb2001-05-232-20/+4
| | | | it in getpages/putpages.
* - Always call bfreekva() w/o vm_mtx held.jhb2001-05-231-28/+12
| | | | | | | - Always call vfs_setdirty() with vm_mtx held. - Fix an old comment: vm_hold_unload_pages is called vm_hold_free_pages() nowadays. - Always call vm_hold_free_pages() w/o vm_mtx held.
* Don't acquire/release Giant around some of the places that need it injhb2001-05-231-2/+1
| | | | spec_getpages(). Instead, assert that Giant is held by the caller.
* - Obtain Giant in mmap() syscall while messing with file descriptors andjhb2001-05-231-18/+32
| | | | | | | | | | | vnodes. - Fix an old bug that would leak a reference to a fd if the vnode being mmap'd wasn't of type VREG or VCHR. - Lock Giant in vm_mmap() around calls into the VM that can call into pager routines that need Giant or into other VM routines that need Giant. - Replace code that used a goto to jump around the else branch of a test to use an else branch instead.
* pmap_mapdev needs the vm_mtx, aquire it if not already lockedalfred2001-05-232-0/+16
|
* lock vm while playing with pmapalfred2001-05-232-0/+18
|
* Acquire Giant around vm_map_remove() inside of the obreak() syscall forjhb2001-05-231-2/+7
| | | | vm_object_terminate().
* Regeneratewpaul2001-05-231-1/+6
|
* Tweak the xmphy driver a little bit based on something I learned aboutwpaul2001-05-233-8/+23
| | | | | | | | | | | | | | | | | | | | | | | the built-in 1000baseX interface in the Level 1 LXT1001 chip. The Level 1 PHY comes up with the isolate bit in the control register set by default, but it also has the autonegotiate bit set. When you tell the xmphy driver to select IFM_AUTO mode, it sees that the autoneg bit is already on, and thus doesn't bother updating the control register. However this means that the isolate bit is never turned off (unless you manually select 1000baseSX full or half duplex mode, which does result in the control register being modified and the ISO bit being turned off). This subtle and unusual behavioral difference stopped me from being able to receive packets on the SMC9462TX card for several days, since isolating the PHY disconnects it from the MAC's data interface. The fix is to omit the 'is the autoneg big set?' test, since it doesn't really provide much of an optimization anyway. This commit also updates the xmphy driver to support the Jato/Level 1 internal PHY. (I'm not sure how Jato Technologies is related to Level 1: all I know is the OUI from the PHY ID registers maps to Jato in the OUI database.) This will be used once I add the if_lge driver to support the LXT10010 chip.
* Take a more conservative approach and still lock Giant around VM faultsjhb2001-05-231-8/+6
| | | | for now.
* - Lock the VM when initializing the vmspace for proc0.jhb2001-05-231-2/+2
| | | | | | - Don't bother releasing Giant while doing a lookup on the vm_map of initproc while starting up init. We have to grab it again right after the lookup anyways.
* Lock the VM while twiddling the vmspace.jhb2001-05-231-1/+2
|
* When a game ends that makes the top 10, the function insert_score inphk2001-05-231-1/+1
| | | | | | | | | | score.c is called to make the new score file. But the case for KFIRE (killed by fire) incorrectly uses strcpy instead of strcat (all the other cases use strcat). This puts the string in the wrong place and corrupts the score file. PR: 13278 Submitted by: Mark W. Krentel krentel@dreamscape.com
* Increment mbstat.m_mpfail, not mbstat.m_mcfail, when m_pullup() fails.bmilekic2001-05-231-1/+1
| | | | This slipped in accidently a few commits back.
* Fix memory leak.ume2001-05-231-0/+2
| | | | Submitted by: itojun
* Polish getnano{up}*time() prototypes.phk2001-05-231-2/+2
| | | | | PR: 15908 Submitted by: Kelly Yancey kbyanc@posi.net
* fdformat prompts for user confirmation. it exits 0 if the userphk2001-05-231-1/+1
| | | | | | | | doesn't confirm, which needlessly complicates scripts. PR: 15339 Submitted by: richard winkel rich@math.missouri.edu MFC after: 1 week
* Set the phys_pager_alloc_lock to 1 when it is acquired so that it isjhb2001-05-231-1/+2
| | | | actually locked.
* Don't release the vm lock just to turn around and grab it again.jhb2001-05-231-3/+0
|
* Make sure that all resource allocation is handled in the pcib device, notdfr2001-05-2312-119/+90
| | | | | | | | the chipset. This is already how the multi-hose systems handle resource allocation and it fixes a bug where dense and bwx memory allocations were not handled properly. Reviewed by: gallatin
* Add in assertions to ensure that we always call msleep or mawait withjhb2001-05-231-0/+4
| | | | | | | either a timeout or a held mutex to detect unprotected infinite sleeps that can easily lead to deadlock. Submitted by: alfred
* Vlan tags are 12 bits, mask off anything above since the chip doesn'tphk2001-05-232-4/+4
| | | | | | | | seem to do so for us. PR: 27567 Submitted by: Koji HINO hino@ccm.cl.nec.co.jp MFC after: 1 week
* syslogd gets kernel log messages only once every 30 seconds orphk2001-05-231-4/+7
| | | | | | | | | | | at the top of the minute, whichever comes first. It seems logtimeout() is only called once after the kernel log is opened and then never again after that. So I guess syslogd only gets kernel log messages by virtue of syncer(4)'s flushes ...? PR: 27361 Submitted by: pkern@utcc.utoronto.ca MFC after: 1 week
OpenPOWER on IntegriCloud