summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Generate another function for the DTrace syscall provider to specifyjb2008-03-271-2/+14
| | | | | | | the syscall argument types. This code is only compiled into the systrace kernel modul and has no effect otherwise.
* Allow awk (the one true one!) to handle 64 files instead of just 20.jb2008-03-271-1/+1
| | | | | | | | | | | The current FreeBSD syscall generation script uses all 20 and I need another open file. It's a shame that something named as the 'one-true-awk' is so limited by an old denition like FOPEN_MAX when it could just make the file handling dynamic. This is done to avoid touching contrib sources on a vendor branch.
* Really, smb_iod_main() is not totally MPSAFE, so just acquire and dropattilio2008-03-271-0/+3
| | | | | | | Giant around it in order to assume MPSAFETY. Reported by: jhb, rwatson Pointy hat to: attilio
* Allow an application to define FOPEN_MAX (like we allow for OPEN_MAXjb2008-03-261-0/+2
| | | | in sys/syslimits.h).
* Removed no longer existing CTL_MACHDEP defines.ru2008-03-261-12/+1
| | | | Inspired by: phk
* Back in the good old days, PC's had random pieces of rock forphk2008-03-2611-601/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | frequency generation and what frequency the generated was anyones guess. In general the 32.768kHz RTC clock x-tal was the best, because that was a regular wrist-watch Xtal, whereas the X-tal generating the ISA bus frequency was much lower quality, often costing as much as several cents a piece, so it made good sense to check the ISA bus frequency against the RTC clock. The other relevant property of those machines, is that they typically had no more than 16MB RAM. These days, CPU chips croak if their clocks are not tightly within specs and all necessary frequencies are derived from the master crystal by means if PLL's. Considering that it takes on average 1.5 second to calibrate the frequency of the i8254 counter, that more likely than not, we will not actually use the result of the calibration, and as the final clincher, we seldom use the i8254 for anything besides BEL in syscons anyway, it has become time to drop the calibration code. If you need to tell the system what frequency your i8254 runs, you can do so from the loader using hw.i8254.freq or using the sysctl kern.timecounter.tc.i8254.frequency.
* Further cleanup of sound generation in syscons:phk2008-03-262-17/+1
| | | | | | | | The timer_spkr_*() functions take care of the enabling/disabling of the speaker. Test on the existence of timer_spkr_*() functions, rather than architectures.
* Allow the characters .-+/ to appear in ppp profile names by folding thembrooks2008-03-262-5/+31
| | | | | | | | to _ when evaluating ppp_<profile>_nat and ppp_<profile>_mode. Document the per-profile variables. PR: conf/121452, conf/122127 (partial) MFC after: 1 week
* Make speaker a pseudo device driver instead of attaching to a PnP id.phk2008-03-261-90/+19
| | | | | If somebody cleaned this code up to proper style(9), it could become a great educational starting point for aspiring kernel hackers.
* Add a comment explaining that we initialize the 'a' buffer forrwatson2008-03-261-0/+5
| | | | | | | | | zero-copy to the store buffer position on the BPF descriptor, and the 'b' buffer as the free buffer in order to fill them in the order documented in bpf(4). MFC after: 4 months Suggested by: csjp
* Some minor code and math optimizations.mav2008-03-261-40/+21
|
* Fix a nit with the 'nofoo' options where 'foo' is mapped to 'nonofoo'jhb2008-03-262-4/+4
| | | | | | | | | | | | | (such as 'atime' vs 'noatime'). The filesystems will always see either 'nofoo' or 'nonofoo', never plain 'foo'. As such, their list of valid mount options should include 'nofoo' instead of 'foo'. With this fix, you can do 'mount -u -o atime' on a FFS filesystem that isn't marked as noatime without getting an error. You can also update a noatime FFS filesystem mounted via mount(2) (e.g. 6.x /sbin/mount binary) to 'atime' using nmount(2) (e.g. 7.x /sbin/mount binary). MFC after: 1 week Reviewed by: crodig
* Remove two variables which are handled MI now.phk2008-03-261-3/+0
|
* Eliminate unnecessary #includesphk2008-03-261-9/+0
|
* The "free-lance" timer in the i8254 is only used for the speakerphk2008-03-2626-332/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | these days, so de-generalize the acquire_timer/release_timer api to just deal with speakers. The new (optional) MD functions are: timer_spkr_acquire() timer_spkr_release() and timer_spkr_setfreq() the last of which configures the timer to generate a tone of a given frequency, in Hz instead of 1/1193182th of seconds. Drop entirely timer2 on pc98, it is not used anywhere at all. Move sysbeep() to kern/tty_cons.c and use the timer_spkr*() if they exist, and do nothing otherwise. Remove prototypes and empty acquire-/release-timer() and sysbeep() functions from the non-beeping archs. This eliminate the need for the speaker driver to know about i8254frequency at all. In theory this makes the speaker driver MI, contingent on the timer_spkr_*() functions existing but the driver does not know this yet and still attaches to the ISA bus. Syscons is more tricky, in one function, sc_tone(), it knows the hz and things are just fine. In the other function, sc_bell() it seems to get the period from the KDMKTONE ioctl in terms if 1/1193182th second, so we hardcode the 1193182 and leave it at that. It's probably not important. Change a few other sysbeep() uses which obviously knew that the argument was in terms of i8254 frequency, and leave alone those that look like people thought sysbeep() took frequency in hertz. This eliminates the knowledge of i8254_freq from all but the actual clock.c code and the prof_machdep.c on amd64 and i386, where I think it would be smart to ask for help from the timecounters anyway [TBD].
* Fix the __FreeBSD_version check.dfr2008-03-261-1/+1
|
* Bump __FreeBSD_version for the addition of 'l_sysid' to the flock structure.dfr2008-03-261-1/+1
|
* Add some regression tests for posix record locks.dfr2008-03-262-0/+1356
|
* Add \n to the end of a printf string and remove it from panic strings.emaste2008-03-261-6/+6
|
* Regen.dfr2008-03-2610-13/+33
|
* Add the new kernel-mode NFS Lock Manager. To use it instead of thedfr2008-03-2680-525/+20923
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | user-mode lock manager, build a kernel with the NFSLOCKD option and add '-k' to 'rpc_lockd_flags' in rc.conf. Highlights include: * Thread-safe kernel RPC client - many threads can use the same RPC client handle safely with replies being de-multiplexed at the socket upcall (typically driven directly by the NIC interrupt) and handed off to whichever thread matches the reply. For UDP sockets, many RPC clients can share the same socket. This allows the use of a single privileged UDP port number to talk to an arbitrary number of remote hosts. * Single-threaded kernel RPC server. Adding support for multi-threaded server would be relatively straightforward and would follow approximately the Solaris KPI. A single thread should be sufficient for the NLM since it should rarely block in normal operation. * Kernel mode NLM server supporting cancel requests and granted callbacks. I've tested the NLM server reasonably extensively - it passes both my own tests and the NFS Connectathon locking tests running on Solaris, Mac OS X and Ubuntu Linux. * Userland NLM client supported. While the NLM server doesn't have support for the local NFS client's locking needs, it does have to field async replies and granted callbacks from remote NLMs that the local client has contacted. We relay these replies to the userland rpc.lockd over a local domain RPC socket. * Robust deadlock detection for the local lock manager. In particular it will detect deadlocks caused by a lock request that covers more than one blocking request. As required by the NLM protocol, all deadlock detection happens synchronously - a user is guaranteed that if a lock request isn't rejected immediately, the lock will eventually be granted. The old system allowed for a 'deferred deadlock' condition where a blocked lock request could wake up and find that some other deadlock-causing lock owner had beaten them to the lock. * Since both local and remote locks are managed by the same kernel locking code, local and remote processes can safely use file locks for mutual exclusion. Local processes have no fairness advantage compared to remote processes when contending to lock a region that has just been unlocked - the local lock manager enforces a strict first-come first-served model for both local and remote lockers. Sponsored by: Isilon Systems PR: 95247 107555 115524 116679 MFC after: 2 weeks
* Rename timer0_max_count to i8254_max_count.phk2008-03-2612-253/+258
| | | | | Rename timer0_real_max_count to i8254_real_max_count and make it static. Rename timer_freq to i8254_freq and make it a loader tunable.
* The RTC related pscnt and psdiv variables have no business being public.phk2008-03-267-14/+6
|
* Remove old sysctl stuff which is long gone in other arch's.phk2008-03-261-21/+0
|
* Fix some "in in" typos in comments.brueffer2008-03-2612-12/+12
| | | | | | | PR: 121490 Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com> Approved by: rwatson (mentor), jkoshy MFC after: 3 days
* Document the removal data for usbdevs.h and usbdevs_data.h,remko2008-03-261-2/+3
| | | | | | | | | sort the entry into it's correct place (behind 200407XX before 200406XX because we have an explicit date here). PR: misc/122098 Submitted by: "John Hein" <jhein@timing.com> MFC after: 3 days
* Enable the automatic creation of superpage reservations.alc2008-03-261-2/+2
|
* split out tty create part of ucom_attach into ucom_attach_tty sosam2008-03-252-7/+13
| | | | | | | derived drivers can use it Submitted by: Jared Go MFC after: 3 weeks
* add some CDMA modemssam2008-03-251-0/+9
| | | | | Submitted by: Jared Go MFC after: 1 week
* Implement taskqueue_block() and taskqueue_unblock(). These functions allowscottl2008-03-252-1/+30
| | | | | | | | | | the owner of a queue to block and unblock execution of the tasks in the queue while allowing tasks to continue to be added queue. Combining this with taskqueue_drain() allows a queue to be safely disabled. The unblock function may run (or schedule to run) the queue when it is called, just as calling taskqueue_enqueue() would. Reviewed by: jhb, sam
* fix botched merge of syslog support to the vendor branch; these filessam2008-03-252-2/+13
| | | | were off the branch so we need to pull the changes back up
* Add 64-bit array support for RAIDs > 2TB. This corresponds to ~ Adaptecemaste2008-03-254-5/+17
| | | | | | | | | | driver build 15317. Tested on: Adaptec 2230S, Firmware 4.2-0 (8205) ICP ICP5085BL, Firmware 5.2-0 (12814) Submitted by: Adaptec
* add __noinlinesam2008-03-251-0/+6
| | | | | | Submitted by: imp Reviewed by: kan (long ago) MFC after: 3 weeks
* expose if_purgemaddrs, it will be used by the vap code unless someonesam2008-03-252-2/+2
| | | | | | redesigns the mcast support code in the next few weeks MFC after: 3 weeks
* IFM_IEEE80211_IBSSMASTER hasn't been used in many years; replace itsam2008-03-251-2/+2
| | | | | | with IFM_IEEE80211_WDS which will be used by the forthcoming vap code MFC after: 3 weeks
* enable dynamic addition of "show all" commandssam2008-03-253-2/+15
| | | | MFC after: 3 weeks
* Bring this manpage more in line with other wlan driver manpages.brueffer2008-03-251-10/+15
|
* Regen.jhb2008-03-254-6/+21
|
* Add entries for the cpuset-related system calls. The existing system callsjhb2008-03-251-0/+12
| | | | | | can be used on little endian systems. Pointy hat to: jeff
* Correct data direction flags in aac_bio_command() in theemaste2008-03-251-2/+2
| | | | | | !AAC_FLAGS_RAW_IO && AAC_FLAGS_SG_64BIT case. Submitted by: Adaptec
* Add code that should catch the most common case when date/time isru2008-03-251-0/+4
| | | | set incorrectly.
* s/M_TRYWAIT/M_WAIT/ru2008-03-252-2/+2
|
* Compile libthr with warnings.ru2008-03-251-0/+3
| | | | (Somehow this file sneaked from initial commit.)
* Add a missing ;.remko2008-03-251-1/+1
| | | | | | | PR: misc/122069 Submitted by: taku@tekipaki.jp MFC after: 3 days Approved by: imp (mentor, implicit trivial change).
* Compile libthr with warnings.ru2008-03-254-6/+12
|
* Fix build.ru2008-03-251-2/+2
| | | | Reported by: ache, tinderbox
* Add /boot/device.hints to the list of files which will have localcperciva2008-03-251-1/+1
| | | | | | | | | modifications merged. I had initially expected that people would put any local changes into /boot/loader.conf, but it turns out that editing /boot/device.hints is something many people do. Suggested by: Jaakko Heinonen MFC after: 1 week
* Adjust recognize-shared-libraries regex to avoid matching symlinks tocperciva2008-03-251-14/+14
| | | | | | | | | | | | | | | | | | | shared libraries. This fixes a problem which resulted in 6.x->7.x upgrades having the /usr/lib/libpthread.so -> libthr.so symlink missing; what happened was that the old libpthread.so symlink pointed to /lib/libpthread.so.2 -- which matched the "/lib/*\.so\.[0-9]+" regex -- but the new symlink didn't, so FreeBSD Update got confused and deleted the symlink as part of its "remove old shared libraries" step. To recreate the symlink (which I understand is necessary for ports like KDE to build) on a 7.x system which FreeBSD Update upgraded from 6.x: # ln -s libthr.so /usr/lib/libpthread.so Reported by: Dmitry RCL Rekman Help diagnosing bug from: kris MFC after: 7 days
* Fixed mis-implementation of pthread_mutex_get{spin,yield}loops_np().ru2008-03-251-4/+7
| | | | Reviewed by: davidxu
* Replaced the misleading uses of a historical artefact M_TRYWAIT with M_WAIT.ru2008-03-2536-264/+125
| | | | | | | | | | Removed dead code that assumed that M_TRYWAIT can return NULL; it's not true since the advent of MBUMA. Reviewed by: arch There are ongoing disputes as to whether we want to switch to directly using UMA flags M_WAITOK/M_NOWAIT for mbuf(9) allocation.
OpenPOWER on IntegriCloud