summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Change the type of vpgqueues::lcnt from "int *" to "int". The indirectionalc1999-07-314-26/+24
| | | | served no purpose.
* Reserve majors for arla.jkh1999-07-312-2/+6
|
* vm_page_queue_init:alc1999-07-311-9/+4
| | | | | | | | | | | | Remove the initialization of PQ_NONE's cnt and lcnt. They aren't used. vm_page_insert: Remove an unnecessary dereference. vm_page_wire: Remove the one and only (and thus pointless) reference to PQ_NONE's lcnt.
* Add parentheses for clarity.alc1999-07-312-4/+4
| | | | Submitted by: dillon
* As described by the submitter:msmith1999-07-312-68/+110
| | | | | | | | | | | | | | | | | | | | I did some tcpdumping the other day and noticed that GETATTR calls were frequently followed by an ACCESS call to the same file. The attached patch changes nfs_getattr to fill the access cache as a side effect. This is accomplished by calling ACCESS rather than GETATTR. This implies a modest overhead of 4 bytes in the request and 8 bytes in the response compared to doing a vanilla GETATTR. ... [The patch comprises two parts] The first is the "real" patch, the second counts misses and hits rather than fills and hits. The difference is subtle but important because both nfs_getattr and nfs_access now fill the cache. It also changes the default value of nfsaccess_cache_timeout to better match the attribute cache. IMHO, file timestamps change much more frequently than protection bits. Submitted by: Bjoern Groenvall <bg@sics.se> Reviewed by: dillon (partially)
* Don't use at_shutdown() now that we have new_bus which lets usmdodd1999-07-312-16/+22
| | | | | | specify a DEVICE_SHUTDOWN method instead. Reviewed by: me, since nobody else seems to run this hardware in -CURRENT
* Reenable the APMIO_BIOS ioctl and translate arguments into the new formatmsmith1999-07-303-3/+51
| | | | | | (which is more like the old than I thought). Requested-by: imp
* Restore the pre-new_bus behavior of printing out the reserved resourcesmdodd1999-07-302-10/+190
| | | | | | during device announcement. (irq, ioport, maddr) Reviewed by: dfr, peter
* Previous commit also removed some 'const' qualifiers on args fornewton1999-07-302-2/+2
| | | | svr4_sys_sendto() which probably shouldn't have been 'const'.
* Previous commit also finished cleaning up some dev_t -> udev_t transformationsnewton1999-07-3010-10/+10
| | | | | | related to the commit for rev 1.3 of svr4_stat.c. svr4_sysvec.c also received a copyright message (which is why it grew by 28 lines).
* Fix svr4_sys_poll(); SysV STREAMS produce return values from poll() whichnewton1999-07-302-12/+4
| | | | | BSD sockets don't. Guess at a correct emulation for those values (it seems to work for telnet, ftp and friends)
* Initial checkinnewton1999-07-301-0/+15
|
* Add $Id$ tags.newton1999-07-303-12/+10
| | | | Clean-up some unused (or to-be-used) variables in svr4_getcontext()
* Clarify use of the 'streams' pseudo-device (i.e.: static or kld).newton1999-07-301-7/+12
| | | | Trust me, this stuff will be in a real manpage before 4.0 ships :-)
* Add $Id$ tagsnewton1999-07-3096-46/+280
|
* Hmm - How did *that* get in there?newton1999-07-301-0/+0
|
* Fix panic caused when *stat64() family of syscalls try to fill-innewton1999-07-306-92/+56
| | | | | | | their svr4_stat64 structures with old dev_t values instead of udev_t's. Panic was caused when major() and minor() were called with args which weren't pointers. The panic was probably introduced in rev 1.51 of kern_conf.c
* Eliminate 'WARNING: "streams" is usurping "streams"'s cdevsw[]' messagesnewton1999-07-301-2/+2
| | | | at boot
* Sync with sys/i386/isa/clock.c revision up to 1.142.kato1999-07-303-33/+18
|
* Sync with sys/i386/i386/machdep.c revision 1.357.kato1999-07-302-14/+50
|
* Removed apm_setup.s.kato1999-07-302-4/+2
|
* Remove all vestiges of APMIO_BIOSmsmith1999-07-303-16/+3
| | | | Submitted by: N. Dudorov <nnd@mail.nsk.ru>
* Close PR #12651: the hash calculation routine has changed in otherwpaul1999-07-302-4/+4
| | | | parts of the kernel but was not updated in nfs_readdirplusrpc().
* Fix two bugs in nfs_readdirplus(). The first is that in some cases,wpaul1999-07-302-6/+12
| | | | | | | | | | | | | | | vnodes are locked and never unlocked, which leads to processes starting to wedge up after doing a mount -o nfsv3,tcp,rdirplus foo:/fs /fs; ls /fs. The second is that sometimes cnp is accessed without having been properly initialized: cnp->cn_nameptr points to an earlier name while "len" contains the length of a current name of different size. This leads to an attempt to dereference *(cn->cn_nameptr + len) which will sometimes cause a page fault and a panic. With these two fixes, client side readdirplus works correctly with FreeBSD, IRIX 6.5.4 and Solaris 2.5.1 and 2.6 servers. Submitted by: Matthew Dillon <dillon@backplane.com>
* Fix install target (install loader.exe, not loader).se1999-07-291-2/+2
|
* Correct the sanity test length calculation in nfsrv_readdirplus(): len iswpaul1999-07-292-4/+4
| | | | | | | | | | | | | | being incremented by 4 bytes too few each time through the loop, which allows more data into the mbuf chain that we really want. In the worst case, when we're using 32K read/write sizes with a TCP client, this causes readdirplus replies to sometimes exceed NFS_MAXPACKET which leads to a panic. This problem cropped up for me using an IRIX 6.5.4 NFSv3 TCP client with 32K read/write sizes, however supposedly it can be triggered by WinNT NFS servers too. In theory, it can probably be triggered by any NFS v3 implementation using TCP as long as it's using the maxiumum block size. Reviewed by: Matthew Dillon <dillon@backplane.com>
* Fix an unbelievably stupid typo that cases as500 & as600 machines bootedgallatin1999-07-291-1/+1
| | | | with a graphics head to panic on boot
* Formatting-only cleanup accidentally omitted from the patch merge in themsmith1999-07-292-396/+392
| | | | | previous major update. Bring new code into style alignment with the existing code. No functional changes.
* No more apm_errno. It breaks the build with APM_DEBUG,iwasaki1999-07-292-6/+6
| | | | uses (sc->bios.r.eax >> 8) & 0xff instead.
* lutimes() bug: FOLLOW should be NOFOLLOW for this one.green1999-07-292-4/+4
| | | | Submitted by: Dan Nelson <dnelson@emsphone.com>
* On an AS 600 5/266 (and possibly others), accessing the configurationgallatin1999-07-291-3/+26
| | | | | | | | | space of PCI devices that don't exist cause PCI master & target aborts rather than returning ~0 or giving a machine check. Bring in some code from NetBSD to handle this properly. obtained from: NetBSD reviewed by: dfr
* Revert rev 1.149. Bruce convinced me that the problem already disappearedjoerg1999-07-292-10/+2
| | | | by the fix in rev 1.120, which i wasn't immediately aware of.
* GBIOSSTACK_SEL is undefined, but OTOH, BSSSEL apparently isn't used either.peter1999-07-292-4/+2
|
* Removed references to a nonexistent variable. This fixes building kernelsbde1999-07-291-4/+1
| | | | without -O.
* Remove some duplicate definitions, as suggested by Alan Cox.msmith1999-07-293-8/+7
|
* Fix for vmspace sharing as per Alan Cox. Thanks!msmith1999-07-292-10/+2
|
* Nuke this, it's not used anymore.msmith1999-07-292-120/+0
|
* Fix a typo.mdodd1999-07-292-7/+7
| | | | | | Back out a few lines that I haven't dealt with properly yet. Snickered at by: Mike Smith
* Major update to the kernel's BIOS-calling ability.msmith1999-07-2915-724/+1311
| | | | | | | | | - Add support for calling 32-bit code in other segments - Add support for calling 16-bit protected mode code Update APM to use this facility. Submitted by: jlemon
* Remove XXX from the headers (broke the build, I'm betting.)green1999-07-295-10/+5
|
* Alter the behavior of sys/kern/subr_bus.c:device_print_child()mdodd1999-07-2941-289/+321
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - device_print_child() either lets the BUS_PRINT_CHILD method produce the entire device announcement message or it prints "foo0: not found\n" Alter sys/kern/subr_bus.c:bus_generic_print_child() to take on the previous behavior of device_print_child() (printing the "foo0: <FooDevice 1.1>" bit of the announce message.) Provide bus_print_child_header() and bus_print_child_footer() to actually print the output for bus_generic_print_child(). These functions should be used whenever possible (unless you can just use bus_generic_print_child()) The BUS_PRINT_CHILD method now returns int instead of void. Modify everything else that defines or uses a BUS_PRINT_CHILD method to comply with the above changes. - Devices are 'on' a bus, not 'at' it. - If a custom BUS_PRINT_CHILD method does the same thing as bus_generic_print_child(), use bus_generic_print_child() - Use device_get_nameunit() instead of both device_get_name() and device_get_unit() - All BUS_PRINT_CHILD methods return the number of characters output. Reviewed by: dfr, peter
* 8 -> NBBygreen1999-07-281-3/+3
|
* Correct a really gross comment format.green1999-07-281-5/+7
|
* Activate "arc" (ARC / AlphaBIOS loader) on Alpha.se1999-07-281-0/+5
|
* Fix some typos.nik1999-07-282-14/+14
| | | | | PR: docs/11955 Submitted by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
* This commit was generated by cvs2svn to compensate for changes in r49187,se1999-07-2828-0/+3009
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * The ARC BIOS / AlphaBIOS specific primary boot loader. This code is these1999-07-2828-0/+3009
| | | | | | | | | | | | result of a joined effort with parts contributed by Doug Rabson, Warner Losh and Stefan Esser (hope I did not forget anybody). Part of the sources is obtained from NetBSD with modifications. This code is work in progress: As of the time of the initial import, a loader.exe executable is built, which can be loaded on an Alpha with NT only firmware, but no attempt is made to switch to OSF PAL code as required to start an actual kernel.
* We're called too early to have any idea whether APM is going to bemsmith1999-07-285-55/+35
| | | | | | | | | | | active or not. The only sane thing we can do here is assume that if APM is supported it might be active at some point, and bail. In reality, even this isn't good enough; regardless of whether we support APM or not, the system may well futz with the CPU's clock speed and throw the TSC off. We need to stop using it for timekeeping except under controlled circumstances. Curse the lack of a dependable high-resolution timer.
* Remove unused real-mode APM setup support. We've been using the vm86msmith1999-07-286-378/+34
| | | | mode initialiser for a while now, and it's looking happy.
* Remove unused real-mode APM init functions.msmith1999-07-2816-1518/+0
|
OpenPOWER on IntegriCloud