summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove the requirement for the FreeBSD keyword as it no longermtm2004-10-07132-134/+92
| | | | | | | makes any sense. Discussed with: dougb, brooks MFC after: 3 days
* Follow kernel change, restore signal mask correctly by using a commanddavidxu2004-10-072-42/+34
| | | | of kse_thr_interrupt.
* Add an execve command for kse_thr_interrupt to allow libpthread todavidxu2004-10-074-3/+32
| | | | | | restore signal mask correctly, this is required by POSIX. Reviewed by: deischen
* Add a minimal altq.4 manpage to tell about the kernel options and where tomlaier2004-10-073-30/+142
| | | | | | | | find more information. Also move the "SUPPORTED DEVICES" section from altq.9 to altq.4, where is belongs. Requested by: green MFC after: 2 days
* Add SHARP to the pool of drives that doesn not need byteswapping ofsos2004-10-071-5/+7
| | | | the model etc fields from identify.
* Mdoc and grammar fixes.glebius2004-10-071-7/+9
| | | | Submitted by: ru
* - note that RTF_PRCLONING is obsoletedglebius2004-10-071-19/+47
| | | | | | | | - explain locking differencies between rtalloc(), rtalloc_ign(), rtalloc1() and rtfree(), RTFREE(). Reviewed by: andre (1.5 months ago) OK'd by: ru
* - Be more userfriendly and allow to specify gbde device name in those forms:pjd2004-10-071-10/+13
| | | | | | | | | | | device device.bde /dev/device /dev/device.bde - Fix stop routine: + There don't have to be file system mounted on gbde device, so ignore errors from umount(8). + Only detach existing gbde devices.
* Add support for Pentium M, Pentium 3M and Pentium 4M.des2004-10-071-2/+14
| | | | | | PR: i386/72340 Submitted by: Rong-En Fan <rafan@infor.org> MFC after: 2 weeks
* Use generic ttycode instead of local copy.phk2004-10-071-183/+32
|
* Only try to attach if parent device actually exists.pjd2004-10-071-1/+1
| | | | | | | I used ugly "/dev/${parent}" instead of "${parentdev}", because "/dev/" prefix for devices listed in gbde_devices variable is optional. Reported by: Sean McNeil <sean@mcneil.com>
* Note libthr ABI breakage.mtm2004-10-071-0/+5
|
* Regen to unbreak world.davidxu2004-10-073-3/+3
| | | | Pointy hat to: mtm
* Back out rev 1.240; it is unnecessary. In particular,das2004-10-061-8/+3
| | | | | | | p1 == curthread, so _PHOLD(p1) will not have to block to swap in p1. Noticed by: jhb
* Don't set the BIO_ONQUEUE debugging flag until we actually put the biophk2004-10-061-1/+1
| | | | onto a queue. This made the ENOMEM handling an instant panic.
* Use generic tty code instead of local copies.phk2004-10-062-571/+199
|
* Back out v1.49. Recent findings suggest sparc64 may not be ready forkensmith2004-10-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | -O2 on kernel compiles after all. While working on adding a KASSERT to sparc64/sparc64/rwindow.c I found that it was "position sensitive", putting it above a call to flushw() instead of below caused corruption of processes on the system. jake and jhb have both confirmed there is no obvious explanation for that. The exact same kernel code does not have the process corruption problem if compiled with -O instead of -O2. There have been signs of similar issues floated on the sparc64@ mailing list, lets see if this helps make them go away. Note this isn't an optimal fix as far as the file format goes, if this disgusts too many people I'll fix it the right way. Since compiling with something other than -O is a known problem this format would prevent a change to the default causing grief. And this may also help motivate finding out what the compiler is doing wrong so we can shift back to using -O2. :-) My turn for the pointy hat... One of the florescent ones... MFC after: 2 days
* Fix the PC98 lockups on boot.sos2004-10-069-70/+135
| | | | | The interchannel locking for PC98 needed to be updated to match the rest of the locking in ATA.
* Geoms without softc are geoms which are initialized, so wait for them.pjd2004-10-061-2/+4
|
* Correct grammos. Added BUGS: may mishandle nonstandard manual pages,schweikh2004-10-061-3/+5
| | | | especially third party junk^Wpages, like emulators/mtools(1) and friends.
* - Fix the compile to chase the p_rux changes.jhb2004-10-061-1/+7
| | | | | | | - Add a comment noting that the ru_[us]times values being read aren't actually valid and need to be computed from the raw values. Submitted by: many (1)
* Add missing 'static'imp2004-10-061-2/+1
|
* Lock file for gbde devices is optional.pjd2004-10-061-2/+6
|
* Close a race between a thread exiting and the freeing of it's stack.mtm2004-10-068-11/+14
| | | | | | | | | After some discussion the best option seems to be to signal the thread's death from within the kernel. This requires that thr_exit() take an argument. Discussed with: davidxu, deischen, marcel MFC after: 3 days
* Look out for geoms without softc.pjd2004-10-061-0/+2
| | | | Reported by: tegge
* Allocate red zone and stack space together and then split red zone fromdavidxu2004-10-062-14/+34
| | | | | allocated space, orignal code left red zone unallocated, but those space can be allocated by user code, and result was providing no protection.
* For older systems with ACPI which don't have a pci <-> pci bridge,imp2004-10-061-3/+3
| | | | | | | allocate unallocated memory resources from the top 32MB of the address space rather than the top 2GB. While the latter works on some chipsets, it fails badly on others. 32MB is more conservative and matches what cheap harware from this era is hardwired to pass.
* For legacy PCI bridges, limit memory allocation to the top 32MB ofimp2004-10-061-4/+24
| | | | | | | | | | | RAM. Many older, legacy bridges only allow allocation from this range. This only appies to devices who don't have their memory assigned by the BIOS (since we allocate the ranges so assigned exactly), so should have minimal impact. Hoewver, for CardBus bridges (cbb), they rarely get the resources allocated by the BIOS, and this patch helps them greatly. Typically the 'bad Vcc' messages are caused by this problem.
* Mention "-d directory" in usage().brooks2004-10-061-1/+1
| | | | Pointy hat to: brooks
* Don't recurse the BPF descriptor lock during the BIOCSDLT operationgreen2004-10-061-1/+1
| | | | | | | | | (and panic). To try to finish making BPF safe, at the very least, the BPF descriptor lock really needs to change into a reader/writer lock that controls access to "settings," and a mutex that controls access to the selinfo/knote/callout. Also, use of callout_drain() instead of callout_stop() (which is really a much more widespread issue).
* fixed too delayed routing cache expiry. (tvtohz() converts a time interval ↵suz2004-10-061-4/+4
| | | | | | to ticks, whereas hzto() converts an absolute time to ticks) Obtained from: KAME
* Add the Madison II, which is the second generation Madison. The Madison IImarcel2004-10-061-0/+3
| | | | | is model 2 in the Itanium 2 family and has up to 9MB of L3 cache and clocks higher than 1.5Ghz. There's no LV variant AFAICT.
* Close a race between thr_create and sysctl -w, the thr_scope_sys coulddavidxu2004-10-061-7/+10
| | | | be changed when thr_create is running, and we tested it for several times.
* vtryrecycle: Don't rely on type VBAD alone to mean that we don't needgrog2004-10-061-1/+1
| | | | | | to clean the vnode. If v_data is set, we still need to clean it. This code change should catch all incidents of the previous commit (INVARIANTS only).
* getnewvnode: Weaken the panic "cleaned vnode isn't" to a warning.grog2004-10-061-1/+3
| | | | | | | | | | | | | | Discussion: this panic (or waning) only occurs when the kernel is compiled with INVARIANTS. Otherwise the problem (which means that the vp->v_data field isn't NULL, and represents a coding error and possibly a memory leak) is silently ignored by setting it to NULL later on. Panicking here isn't very helpful: by this time, we can only find the symptoms. The panic occurs long after the reason for "not cleaning" has been forgotten; in the case in point, it was the result of severe file system corruption which left the v_type field set to VBAD. That issue will be addressed by a separate commit.
* Restore some code removed in revision 1.193 and 1.194, julian saiddavidxu2004-10-061-4/+23
| | | | he'd like to keep these code.
* In original kern_execve() code, at the start of the function, it forcesdavidxu2004-10-063-38/+111
| | | | | | | | | | | | | | | | | all other threads to suicide, problem is execve() could be failed, and a failed execve() would change threaded process to unthreaded, this side effect is unexpected. The new code introduces a new single threading mode SINGLE_BOUNDARY, in the mode, all threads should suspend themself at user boundary except the singler. we can not use SINGLE_NO_EXIT because we want to start from a clean state if execve() is successful, suspending other threads at unknown point and later resuming them from there and forcing them to exit at user boundary may cause the process to start from a dirty state. If execve() is successful, current thread upgrades to SINGLE_EXIT mode and forces other threads to suicide at user boundary, otherwise, other threads will be resumed and their interrupted syscall will be restarted. Reviewed by: julian
* Forced commit to note the submitter.green2004-10-050-0/+0
| | | | Submitted by: stefanf
* Make sure to return 0 from kernel_getnfile() since if there were angreen2004-10-051-0/+1
| | | | error, it would exit() (and it needs to return a value).
* Don't prepend the directory specified by -d when the file is a relativebrooks2004-10-051-1/+1
| | | | | path. Doing so makes no sense. I'm not sure allowing relative paths makes sense either, but I'm not going to break that now.
* Fix whitespace botch that only showed up in the commit message diff :-/julian2004-10-051-1/+1
| | | | MFC after: 4 days
* Bump __FreeBSD_version for addition of newsyslog -d.brooks2004-10-051-1/+1
|
* Slight cleanup in the single threading code.julian2004-10-051-6/+5
| | | | MFC after: 4 days
* When preempting a thread, put it back on the HEAD of its run queue.julian2004-10-055-39/+53
| | | | | | (Only really implemented in 4bsd) MFC after: 4 days
* Oops. left out part of the diff.julian2004-10-051-0/+2
| | | | MFC after: 4 days
* Update a comment that was outdated.njl2004-10-051-1/+1
|
* Use some macros to trach available scheduler slots to allowjulian2004-10-053-23/+64
| | | | | | easier debugging. MFC after: 4 days
* light rearrangement of some code to get some lockingjulian2004-10-051-15/+27
| | | | | | more correct MFC after: 4 days
* Back out the -s flag and go back to dumping the SSDTs by default.njl2004-10-054-22/+6
|
* Update the man page with new info about overriding your DSDT.njl2004-10-051-10/+12
| | | | MFC after: 3 days
OpenPOWER on IntegriCloud