summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Enable aac(4) module build for amd64scottl2004-08-301-0/+1
|
* Only compile aac_linux.ko for i386scottl2004-08-301-0/+2
|
* s/ENTRY/ENTRY_NOPROFILE/g for particular functions that do not followmarcel2004-08-304-8/+8
| | | | | the C calling convention or are otherwise not regular functions. This allows us to boot a profiling kernel.
* Add a missing '\n'.pjd2004-08-301-2/+2
|
* Only test return_instead if P_SINGLE_EXIT is set, otherwise a fork()davidxu2004-08-291-1/+1
| | | | | | | | | | syscall can interrupt other thread's syscall in sleepq_catch_signals(). Current, all callers know thread_suspend_check may suspend thread itself, so we need't to check return_instead for normal suspension flags (no P_SINGLE_EXIT set). Tested by: deischen Reported by: Maarten L. Hekkelman <m.hekkelman@cmbi.kun.nl>
* Move the acquisition and release of the lock on the object at the head ofalc2004-08-291-4/+12
| | | | | the shadow chain outside of the loop in vm_object_madvise(), reducing the number of times that this lock is acquired and released.
* Remove the last remnants of HW_WDOG (no, really!)des2004-08-291-15/+0
|
* In alpha_pci_alloc_resource(), when allocating a memory resource,marcel2004-08-291-1/+1
| | | | | | | | | | | do not set the virtual address to the bus address when the bus doesn't have either of the PCI_RF_DENSE or PCI_RF_BWX flags set. The TGA driver uses the virtual address to access the registers, which on some machines can cause a memory management fault. Map the bus address as K0SEG virtual memory instead. Note that with some hardware combinations involving the TGA2 adapter this change merely results that the memory management fault is replaced by a machine check.
* Initial support (disabled) for rebidding devices. I've been runningimp2004-08-291-4/+36
| | | | | | | | | | this in my tree for a while and in its disabled state there are no issues. It isn't enabled yet because some drivers (in acpi) have side effects in their probe routines that need to be resolved in some manner before this can be turned on. The consensus at the last developer's summit was to provide a static method for each driver class that will return characteristics of the driver, one of which is if can be reprobed idempotently.
* MFp4: Merge in the patches, submitted long ago by someone whose emailimp2004-08-291-12/+26
| | | | | | | | | address I've lost, that move the location information to the atttach routine as well. While one could use devinfo to get this data, that is difficult and error prone and subject to races for short lived devices. Would make a good MT5 candidate.
* Finish the removal of the HW_WDOG option.ru2004-08-291-6/+0
| | | | Hopefully, we'll finally have the compilable LINT kernels again. ;)
* GCC, ehh.pjd2004-08-292-0/+2
|
* Remove an unused variable.simokawa2004-08-291-1/+1
|
* Back out previous commit, ichwd is i386-only.des2004-08-291-1/+0
|
* Add a section for hardware watchdog timers, initially populated by ichwd.des2004-08-291-0/+7
| | | | MFC after: 3 days
* Remove the HW_WDOG option; it serves no purpose.des2004-08-295-20/+0
| | | | MFC after: 3 days
* Back out the two previous commits; ichwd is i386-only.des2004-08-291-6/+0
|
* Enable more modules on AMD64:obrien2004-08-291-0/+14
| | | | ciss em ext2fs i2c ida iir ips lnc mly safe scsi_low smbfs sppp twa
* Enable sound modules.obrien2004-08-291-0/+1
|
* Fixed the module name (macros don't work here).ru2004-08-291-1/+1
|
* Add an entry for ichwd to hopefully unbreak the LINT build.iedowse2004-08-291-0/+1
|
* Do not match TGA2 adapters. They are not compatible with TGA adapters,marcel2004-08-291-2/+0
| | | | | | | | nor are they 3D accelarators as the description would like us to believe. Since the TGA2 adapter has a VGA mode (unlike the TGA adapter), one can use the VGA driver instead. This fixes GENERIC kernels on alpha with TGA2 adapters.
* Fix two cases where a successful return from usbd_transfer() wouldiedowse2004-08-291-2/+2
| | | | | | be treated as an error and cause a transfer to be freed twice. This can probably only happen at boot time when transfers are processed synchronously.
* Unconditionally add `-fno-omit-frame-pointer' to CFLAGS when buildingiedowse2004-08-291-0/+3
| | | | | modules on the amd64 platform. Without this, ddb stack traces cannot follow module function calls, which makes debugging very difficult.
* Add support for completing the installation of ELF relocatableiedowse2004-08-291-3/+208
| | | | | object format modules that were read in by the loader. Loading modules via the loader should now work on the amd64 platform.
* Prevent vm_page_zero_idle_wakeup() from attempting to wake up theiedowse2004-08-291-2/+5
| | | | | | | | | | page zeroing thread before it has been created. It was possible for calls to free() very early in the boot process to panic here because the sleep queues were not yet initialised. Specifically, sysinit_add() running at SI_SUB_KLD would trigger this if the array of pointers became big enough to require uma_large_alloc() allocations. Submitted by: peter
* Add the loader side of support for preloading ELF relocatable objectiedowse2004-08-298-1/+550
| | | | | | | | | | format modules, which are currently only used on the amd64 platform. This initial implementation just parses enough of the module to allow it to extract dependencies and load all the bits into the right place in memory, so the kernel must still do the full relocation and linking. The details of the loaded sections are passed to the kernel by supplying a copy of the ELF section header table as module metadata with the MODINFOMD_SHDR tag.
* Separate out the ELF relocation code from the ELF loader, and addiedowse2004-08-286-35/+294
| | | | | | | | | better relocation support for the amd64 and i386 platforms. This should not result in any change in functionality, but moves a step towards supporting the relocatable object file modules on amd64. The same hack/trick as load_elf*.c uses is used here to simultaneously support both elf32 and elf64 on amd64 and i386.
* Stop pretending: TurboLaser support is really brokenwilko2004-08-281-1/+2
| | | | MFC after: 2 days
* Stop pretending: TurboLaser support is really broken.wilko2004-08-281-1/+2
| | | | MFC after: 2 days
* Eliminate unnecessary indirection.alc2004-08-283-6/+6
|
* Fixed untested change.ru2004-08-281-1/+1
|
* Correct typo in printf() warning.rwatson2004-08-281-1/+1
| | | | Submitted by: Pawel Worach <pawel.worach at telia.com>
* Add the Intel ICH watchdog timer driver.netchild2004-08-281-0/+6
| | | | Approved by: des
* Mark Netgraph TTY, KAME IPSEC, and IPX/SPX as requiring Giant for correctrwatson2004-08-283-0/+10
| | | | | | | operation using NET_NEEDS_GIANT(). This will result in a boot-time restoration of Giant-enabled network operation, or run-time warning on dynamic load (applicable only to the Netgraph component). Additional components will likely need to be marked with this in the future.
* Change the default disposition of debug.mpsafenet from 0 to 1, whichrwatson2004-08-283-3/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | will cause the network stack to operate without the Giant lock by default. This change has the potential to improve performance by increasing parallelism and decreasing latency in network processing. Due to the potential exposure of existing or new bugs, the following compatibility functionality is maintained: - It is still possible to disable Giant-free operation by setting debug.mpsafenet to 0 in loader.conf. - Add "options NET_WITH_GIANT", which will restore the default value of debug.mpsafenet to 0, and is intended for use on systems compiled with known unsafe components, or where a more conservative configuration is desired. - Add a new declaration, NET_NEEDS_GIANT("componentname"), which permits kernel components to declare dependence on Giant over the network stack. If the declaration is made by a preloaded module or a compiled in component, the disposition of debug.mpsafenet will be set to 0 and a warning concerning performance degraded operation printed to the console. If it is declared by a loadable kernel module after boot, a warning is displayed but the disposition cannot be changed. This is implemented by defining a new SYSINIT() value, SI_SUB_SETTINGS, which is intended for the processing of configuration choices after tunables are read in and the console is available to generate errors, but before much else gets going. This compatibility behavior will go away when we've finished the last of the locking work and are confident that operation is correct.
* Tag a last set of PCI network interfaces as IFF_NEEDSGIANT until theyrwatson2004-08-288-8/+16
| | | | are either locked down or demonstrated MPSAFE.
* Add a few helper functions for zeroing kernel space and readingiedowse2004-08-283-37/+82
| | | | from specified file offsets. Make use of these in load_elf.c.
* Add support Corega CG-LAPCIGT Gigabit Ethernet(8169S)sanpei2004-08-282-0/+7
| | | | | | PR: [FreeBSD-users-jp 80667] Submitted by: FUJIMOTO Kou <fujimoto@j.dendai.ac.jp> MFC after: 1 week
* Don't be too smart, just try packet mode of INT13 first.yar2004-08-282-5/+9
| | | | | | | | | | | | | | | This way of operation is more robust than the "AI" used before. Add flags to mbr accessible from make.conf as BOOT_MBR_FLAGS. Only one flag is defined now, "allow using packet mode", which is 0x80 in accord with the rest of i386 boot code. The "packet" flag is on by default. PR: i386/70241 Submitted by: Valentin Nechayev <netch <@> netch.kiev.ua> (inital version) Discussed with: jhb (by Valentin Nechayev) Tested on: bochs (with EDD turned on or off by patching the BIOS), PCs
* Try packet mode of INT13 on a hard disk first if not prohibited byyar2004-08-281-19/+21
| | | | | | | | | | | the flag, fall back to the old INT13/AH=02 function if that fails. This way of operation is less likely to fail with modern BIOSes and large disks of strange geometries. PR: i386/70241 Submitted by: Valentin Nechayev <netch <@> netch.kiev.ua> (inital version) Discussed with: jhb (by Valentin Nechayev) Tested on: bochs (with EDD turned on or off by patching the BIOS), PCs
* 1. try to use existing mailbox address in thread_update_usr_ticks.davidxu2004-08-281-4/+6
| | | | 2. remove '\n' in KASSERT.
* Move TDF_CAN_UNBIND to thread private flags td_pflags, this eliminatesdavidxu2004-08-282-23/+7
| | | | | | | need of sched_lock in some places. Also in thread_userret, remove spare thread allocation code, it is already done in thread_user_enter. Reviewed by: julian
* Use sc->sc_mediasize instead of sc->sc_provider->mediasize which containspjd2004-08-281-4/+3
| | | | exactly the same value, but is shorter.
* Warn the user if we are not going to use whole provider space.pjd2004-08-281-4/+12
| | | | Requested by: Michael Handler <handler@grendel.net>
* Don't allow to insert providers, which are too small.pjd2004-08-281-0/+4
| | | | Reported by: Michael Handler <handler@grendel.net>
* Backout the previous backout (with scott's ok). sched_ule.c:1.122 ispeter2004-08-281-0/+2
| | | | believed to fix the problem with ULE that this change triggered.
* s/smp_rv_mtx/smp_ipi_mtx/gobrien2004-08-286-23/+23
| | | | Requested by: jhb
* Commit Jeff's suggested changes for avoiding a bug that is exposed bypeter2004-08-281-4/+2
| | | | | | | preemption and/or the rev 1.79 kern_switch.c change that was backed out. The thread was being assigned to a runq without adding in the load, which would cause the counter to hit -1.
* remove unused prototypesos2004-08-271-1/+0
|
OpenPOWER on IntegriCloud