summaryrefslogtreecommitdiffstats
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* Add GEOM_MULTIPATH so LINT will build.des2007-02-271-0/+1
| | | | Pointy hat to: mjacob
* Further improvements to LOCK_PROFILING:kmacy2007-02-271-0/+1
| | | | | | | | | | | | - Fix missing initialization in kern_rwlock.c causing bogus times to be collected - Move updates to the lock hash to after the lock is released for spin mutexes, sleep mutexes, and sx locks - Add new kernel build option LOCK_PROFILE_FAST - only update lock profiling statistics when an acquisition is contended. This reduces the overhead of LOCK_PROFILING to increasing system time by 20%-25% which on "make -j8 kernel-toolchain" on a dual woodcrest is unmeasurable in terms of wall-clock time. Contrast this to enabling lock profiling without LOCK_PROFILE_FAST and I see a 5x-6x slowdown in wall-clock time.
* First cut at GEOM based multipath. This is an active/passive{/passive...}mjacob2007-02-272-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | arrangement that has no intrinsic internal knowledge of whether devices it is given are truly multipath devices. As such, this is a simplistic approach, but still a useful one. The basic approach is to (at present- this will change soon) use camcontrol to find likely identical devices and and label the trailing sector of the first one. This label contains both a full UUID and a name. The name is what is presented in /dev/multipath, but the UUID is used as a true distinguishor at g_taste time, thus making sure we don't have chaos on a shared SAN where everyone names their data multipath as "Fred". The first of N identical devices (and N *may* be 1!) becomes the active path until a BIO request is failed with EIO or ENXIO. When this occurs, the active disk is ripped away and the next in a list is picked to (retry and) continue with. During g_taste events new disks that meet the match criteria for existing multipath geoms get added to the tail end of the list. Thus, this active/passive setup actually does work for devices which go away and come back, as do (now) mpt(4) and isp(4) SAN based disks. There is still a lot to do to improve this- like about 5 of the 12 recommendations I've received about it, but it's been functional enough for a while that it deserves a broader test base. Reviewed by: pjd Sponsored by: IronPort Systems MFC: 2 months
* Build ipx_ip.c only if options IPXIP is defined. No functional change.rwatson2007-02-261-1/+1
|
* Make IPv6 multicast forwarding dynamically loadable from a GENERIC kernel.bms2007-02-241-2/+2
| | | | | | It is built in the same module as IPv4 multicast forwarding, i.e. ip_mroute.ko, if and only if IPv6 support is enabled for loadable modules. Export IPv6 forwarding structs to userland netstat(1) via sysctl(9).
* Add two new options, FLASHADDR, which defines the address the flash iscognet2007-02-191-0/+2
| | | | | | | mapped at, and LOADERRAMADDR, the address at which the loader maps the ram at at the time the kernel is booted. They are used to detect if the kernel is booted from the onboard flash. Define those for the IQ31244
* Teach DDB how to print sockets, socket buffers, protosw's, and domainrwatson2007-02-151-0/+1
| | | | structures given pointers to them.
* Makefile changes to reflect moving sys/isofs/cd9660 to sys/fs/cd9660.rodrigc2007-02-111-8/+8
| | | | | Continue to install userland include files in /usr/include/isofs/cd9660 so as not to break userland applications such as libstand.
* Build PIM by default as part of the IPv4 multicast forwarding path.bms2007-02-102-6/+1
| | | | | | | | Make PIM dynamically loadable by using encap_attach_func(). PIM may now be loaded into a GENERIC kernel. Tested with: ports/net/pimdd && tcpreplay && wireshark Reviewed by: Pavlin Radoslavov
* Evolve the ctlreq interface added to geom_gpt into a genericmarcel2007-02-074-7/+8
| | | | | | | | | | | partitioning class that supports multiple schemes. Current schemes supported are APM (Apple Partition Map) and GPT. Change all GEOM_APPLE anf GEOM_GPT options into GEOM_PART_APM and GEOM_PART_GPT (resp). The ctlreq interface supports verbs to create and destroy partitioning schemes on a disk; to add, delete and modify partitions; and to commit or undo changes made.
* The path to the mmc/mmcbus_if.m file is wrong. Correct it byimp2007-02-031-1/+1
| | | | | | prepending dev/ Submitted by: Andrea Bittau
* Mark mmc *_if.m files as standard to allow for mmc/sd being compiledimp2007-02-031-2/+2
| | | | | | as a module. Submitted by: Andrea Bittau
* Remove MSDOSFS_LARGE compile time option. It has been convertedrodrigc2007-01-302-15/+0
| | | | | | | to a run time "-o large" mount option. PR: 105964 MFC after: 2 weeks
* Add a "-o large" mount option for msdosfs. Convert compile-time checks forrodrigc2007-01-301-1/+1
| | | | | | | | | | | | | | | | #ifdef MSDOSFS_LARGE to run-time checks to see if "-o large" was specified. Test case provided by Oliver Fromme: truncate -s 200G test.img mdconfig -a -t vnode -f test.img -u 9 newfs_msdos -s 419430400 -n 1 /dev/md9 zip250 mount -t msdosfs /dev/md9 /mnt # should fail mount -t msdosfs -o large /dev/md9 /mnt # should succeed PR: 105964 Requested by: Oliver Fromme <olli lurza secnetix de> Tested by: trhodes MFC after: 2 weeks
* Add support for serial communication with Windows CE based Handheld Computer.takawata2007-01-282-0/+3
| | | | Obtained from: NetBSD
* Add front-ends for the 'lebuffer' variants found on some SBus cards.marius2007-01-201-0/+2
| | | | | | | | | These are shared-memory variants based on Am79C90-compatible chips that apart from the missing DMA engine are similar to the 'ledma' variant including using a (pseudo-)bus/device for the buffer that the actual LANCE device hangs off from. The performance of these is close to that of the 'ledma' one, like expected at a few times the CPU load though.
* Remove remnants from the sparc64 origin of this file and which aremarius2007-01-191-5/+0
| | | | unlikely to be ever used and misplaced on sun4v respectively.
* Wrap the EISA-specific parts of the dpt(4) and si(4) back-ends inmarius2007-01-181-0/+2
| | | | | | | the newly added DEV_EISA. This is done so that these back-ends can be compiled on platforms not providing in{b,w,l}()/out{b,w,l}() and friends (but may wish to use them together with bus front-ends other than the EISA one).
* Resurrect upa(4), now used for the subordinate/slave UPA bridge andmarius2007-01-161-0/+1
| | | | | | | | bus hanging off from the Fireplane/Safari bus in some USIII machines. This is part 3/4 of allowing creator(4) to work in these machines. The little info needed on how to configure the bridge and to work around the incorrect values contained in the `interrupts' properties of its children were obtained form OpenSolaris.
* - Merge sys/sparc64/creator/creator_upa.c into sys/dev/fb/creator.c.marius2007-01-161-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The separate bus front-end was inherited from the OpenBSD creator(4), which at that time had a mainbus(4) (for USI/II machines, which use an UPA interconnection bus as the nexus) and an upa(4) (for USIII machines, which use a subordinate/slave UPA bus hanging off from the Fireplane/Safari interconnection bus) front-end. With FreeBSD and newbus there is/will be no need to have two separate bus front-ends for these busses, so we can easily coallapse the shared front-end and the back-end into a single source file (note that the FreeBSD creator_upa.c was misnomer anyway; based on what it actually attached to that should have been creator_nexus.c), actually OpenBSD meanwhile also has moved to a shared front-end and a single source file. Due to the low-level console support creator.c also wasn't free from bus related things before. While at it, also split sys/sparc64/creator/creator.h into a sys/dev/fb/creatorreg.h that only contains register macros and move the structures to the top of sys/dev/fb/creator.c as suggested by style(9) so creator(4) is no longer scattered over two directories. - Use OF_decode_addr()/sparc64_fake_bustag() to obtain the bus tags and handles for the low-level console support instead of hardcoding support for AFB/FFB hanging off from nexus(4) only. This is part 2/4 of allowing creator(4) to work in USIII machines (which have a UPA bus hanging off from the Fireplane/Safari bus reflected by the nexus), which already makes it work as the low-level console there. - Allocate resources in the bus attach routine regardless of whether creator(4) is used as for the low-level console and thus the required bus tags and handles have been already obtained or not so the resources are marked as taken in the respective RMAN. - For both obtaining the bus tags and handles for the low-level console support as well as allocating the corresponding resources in the regular bus attach routine don't bother to get all for the maximum of 24 register banks but only (for) the two tag/handle pairs required for providing the video interface for syscons(4) support. If we can't allocate the rest of them just limit the memory range accessible via creator_fb_mmap() accordingly. - Sanity check the memory range spanned by the first and last resources and the resources in between as far as possible, as the XFree86/Xorg sunffb(4) expects to be able to access the whole region, even though the backing resources are actually non-continuous. Limit and check the memory range accessible via creator_fb_mmap() accordingly. - Reduce the size of buffers for OFW properties to what they actually need to hold. - Rename some tables to creator_<foo> for consistency. - Also for the sizes in the creator_fb_mmap() mapping table entries use macros for consistency, add macros for the remaining register banks for completeness.
* Add missing SC_NO_MODE_CHANGE option. Disable it in the powerpcmarius2007-01-102-0/+2
| | | | | | | NOTES though, as ofw_syscons(4) doesn't properly interface with syscons(4) regarding loading the font specified with SC_DFLT_FONT, causing a kernel with both options SC_OFWFB and SC_NO_MODE_CHANGE to not link.
* MFp4: add BWCT kernel configurationticso2007-01-051-0/+1
|
* MFp4: add basic driver for RTL8305SC switch in PHY emulationticso2007-01-051-0/+1
|
* Wrap ipfw nat support in a new kernel config option namedpiso2007-01-032-0/+6
| | | | | | | "IPFIREWALL_NAT": this way nat is turned off by default and POLA is preserved. Reviewed by: rwatson
* now that MFS_IMAGE is in the FULLKERNEL section, use FULLKERNEL instead ofjmg2006-12-301-4/+4
| | | | | | KERNEL_KO, this fixes MFS_IMAGE on a debugging kernel... Submitted by: Neelkanth Natu
* Work around a long standing LOR with user/group rules by doing the socketmlaier2006-12-292-0/+5
| | | | | | | | | | lookup early. This has some performance implications and should not be enabled by default, but might help greatly in certain setups. After some more testing this could be turned into a sysctl. Tested by: avatar LOR ids: 17, 24, 32, 46, 191 (conceptual) MFC after: 6 weeks
* Build bits for ng_deflate(4) and ng_pred1(4).glebius2006-12-293-0/+6
|
* Break contents of kern_mac.c out into two files following a repo-copy:rwatson2006-12-281-1/+2
| | | | | | | | | | | mac_framework.c Contains basic MAC Framework functions, policy registration, sysinits, etc. mac_syscalls.c Contains implementations of various MAC system calls, including ENOSYS stubs when compiling without options MAC. Obtained from: TrustedBSD Project
* Connect vfs_extattr.c to build by default.rwatson2006-12-231-0/+1
|
* build new mdesc filekmacy2006-12-181-1/+3
|
* opt_ah.h ends up copied into a kernelcompile directory in somemjacob2006-12-186-6/+6
| | | | | | | | | | | aches as a read-only file. In a number of cases this has led to compiles failing- usually due to some strange NFS drift which thinks that the opt_ah.h in the compile directory is out of date wrt the source it is copied from. When the copy is executed again, it fails because the target is read-only. Oops. Modify the compile hooks avoid this. Discussed with a while back with: Sam Leffler
* spelling nitmjacob2006-12-181-1/+1
|
* Hook up msk(4) to the build.yongari2006-12-132-0/+5
|
* Make MAXPHYS and DFLTPHYS options (finally).mjacob2006-12-102-0/+17
|
* As Bernd Walter points out, the rlphy is used for more things thanimp2006-12-101-1/+0
| | | | | | | just the intenral phy on parts supported by the rl and re drivers, the RTL8201BL for example. He also sent me a nice picture of hundreds of these chips in a tray to boulder his claim. :-) Therefore remove a comment that suggested that they were...
* fls was missingsam2006-11-301-0/+1
| | | | MFC after: 1 week
* Turn console printf buffering into a kernel option and only onjb2006-11-301-0/+3
| | | | | | | | | | | | | | | | | by default for sun4v where it is absolutely required. This change moves the buffer from struct pcpu to the stack to avoid using the critical section which created a LOR in a couple of cases due to interaction with the tty code and kqueue. The LOR can't be fixed with the critical section and the pcpu buffer can't be used without the critical section. Putting the buffer on the stack was my initial solution, but it was pointed out that the stress on the stack might cause problems depending on the call path. We don't have a way of creating tests for those possible cases, so it's best to leave this as an option for the time being. In time we may get enough data to enable this option more generally.
* Build glue for at45d flash support.imp2006-11-291-1/+1
|
* Fix module loading for sparc on machines with greater than 1GB of RAMkmacy2006-11-261-1/+1
| | | | | | | | | | | | | t1# uname -m sparc64 t1# sysctl hw.physmem hw.physmem: 17150509056 t1# kldload reiserfs t1# kldstat Id Refs Address Size Name 1 3 0xc0000000 58cc38 kernel 2 1 0xcbe70000 234000 xfs.ko 3 1 0xcc0b6000 110000 reiserfs.ko
* device-independent implementation of AMRR tx rate control algorithmsam2006-11-261-0/+1
| | | | | Obtained from: openbsd (w/ mods) MFC after: 1 month
* move CDDL licensed machine description support routine files to cddl directorykmacy2006-11-241-9/+9
| | | | update files.sun4v accordingly
* Remove the KDTRACE option because I can't implement it thejb2006-11-211-1/+0
| | | | | | | | | way I intended due to licensing restrictions. I had intended that it would be defaulted on, with opt-out possible for companies that don't accept the CDDL. The FreeBSD GENERIC kernel has to be entirely BSD licensed, so the only alternative would have been to make KDTRACE an opt-in option. That isn't a design I favour.
* add CPU_XSCALE_IXP425sam2006-11-191-0/+1
| | | | | Reviewed by: cognet, imp MFC after: 1 month
* hookup ad7418 and ds1672 driverssam2006-11-191-0/+2
| | | | MFC after: 1 month
* Remove two more duplicated fileskmacy2006-11-181-2/+2
| | | | Reviewed by: jb (mentor is rwatson)
* remove 13 (largely) redundant files and switch to the sparc64/sparc64 versionkmacy2006-11-181-14/+12
| | | | Reviewed by: jb (mentor rwatson)
* o Add uark(4), a driver for Arkmicro Technologies ARK3116 based serialmaxim2006-11-152-0/+3
| | | | | | | | | adapters. Submitted by: Alex Rodin Obtained from: OpenBSD Reviewed by: -usb MFC after: 6 weeks
* Unbreak pc98.ru2006-11-141-0/+1
|
* MD support for PCI Message Signalled Interrupts on amd64 and i386:jhb2006-11-132-0/+2
| | | | | | | | | | | | | | | | | | | - Add a new apic_alloc_vectors() method to the local APIC support code to allocate N contiguous IDT vectors (aligned on a M >= N boundary). This function is used to allocate IDT vectors for a group of MSI messages. - Add MSI and MSI-X PICs. The PIC code here provides methods to manage edge-triggered MSI messages as x86 interrupt sources. In addition to the PIC methods, msi.c also includes methods to allocate and release MSI and MSI-X messages. For x86, we allow for up to 128 different MSI IRQs starting at IRQ 256 (IRQs 0-15 are reserved for ISA IRQs, 16-254 for APIC PCI IRQs, and IRQ 255 is reserved). - Add pcib_(alloc|release)_msi[x]() methods to the MD x86 PCI bridge drivers to bubble the request up to the nexus driver. - Add pcib_(alloc|release)_msi[x]() methods to the x86 nexus drivers that ask the MSI PIC code to allocate resources and IDT vectors. MFC after: 2 months
* Add time-of-day support to sun4vkmacy2006-11-131-0/+1
|
OpenPOWER on IntegriCloud