summaryrefslogtreecommitdiffstats
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* Move uma_small_alloc() and uma_small_free() out of the pmap and into theiralc2004-06-111-0/+1
| | | | | own machine-dependent file. This makes alpha consistent with amd64, ia64, and powerpc.
* Deorbit COMPAT_SUNOS.phk2004-06-112-7/+0
| | | | | We inherited this from the sparc32 port of BSD4.4-Lite1. We have neither a sparc32 port nor a SunOS4.x compatibility desire these days.
* Add esp(4) to NOTES.scottl2004-06-101-0/+2
|
* Add the esp(4) files. Two of them are sbus-specific and therefore onlyscottl2004-06-102-0/+3
| | | | apply to sparc64.
* Step 1 in moving EISA devices to kobj/newbus. Use kobj methods forimp2004-06-092-1/+2
| | | | | | | | | | | | | | all of the interface between the driver and the bus. This will enable us to stop special casing eisa bus attachments in modules and treat them like we treat all other busses. In the longer run, we need to eliminate much (all?) of these interfaces and switch to using the standard bus_alloc_resource(), but that's not done right now. # I've not updated the modules to include eisa, etc, just yet Tested on: Compaq Proliant 3000/333 purchased for eisa work
* Remove references to L1 in the comments, according to Alan they arenetchild2004-06-071-5/+5
| | | | | | historical leftovers. Approved by: alc
* Split kern_thread.c into 2 parts. kern_kse.c and kern_thread.cjulian2004-06-071-0/+1
| | | | | Kern_kse has already been committed. This separates out the KSE threading ABI from generic thread support.
* Axe the old midi drivers and framework. matk has developed a newtanimura2004-06-012-35/+0
| | | | module-friendly midi subsystem to be merged soon.
* Bring in mbuma to replace mballoc.bmilekic2004-05-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mbuma is an Mbuf & Cluster allocator built on top of a number of extensions to the UMA framework, all included herein. Extensions to UMA worth noting: - Better layering between slab <-> zone caches; introduce Keg structure which splits off slab cache away from the zone structure and allows multiple zones to be stacked on top of a single Keg (single type of slab cache); perhaps we should look into defining a subset API on top of the Keg for special use by malloc(9), for example. - UMA_ZONE_REFCNT zones can now be added, and reference counters automagically allocated for them within the end of the associated slab structures. uma_find_refcnt() does a kextract to fetch the slab struct reference from the underlying page, and lookup the corresponding refcnt. mbuma things worth noting: - integrates mbuf & cluster allocations with extended UMA and provides caches for commonly-allocated items; defines several zones (two primary, one secondary) and two kegs. - change up certain code paths that always used to do: m_get() + m_clget() to instead just use m_getcl() and try to take advantage of the newly defined secondary Packet zone. - netstat(1) and systat(1) quickly hacked up to do basic stat reporting but additional stats work needs to be done once some other details within UMA have been taken care of and it becomes clearer to how stats will work within the modified framework. From the user perspective, one implication is that the NMBCLUSTERS compile-time option is no longer used. The maximum number of clusters is still capped off according to maxusers, but it can be made unlimited by setting the kern.ipc.nmbclusters boot-time tunable to zero. Work should be done to write an appropriate sysctl handler allowing dynamic tuning of kern.ipc.nmbclusters at runtime. Additional things worth noting/known issues (READ): - One report of 'ips' (ServeRAID) driver acting really slow in conjunction with mbuma. Need more data. Latest report is that ips is equally sucking with and without mbuma. - Giant leak in NFS code sometimes occurs, can't reproduce but currently analyzing; brueffer is able to reproduce but THIS IS NOT an mbuma-specific problem and currently occurs even WITHOUT mbuma. - Issues in network locking: there is at least one code path in the rip code where one or more locks are acquired and we end up in m_prepend() with M_WAITOK, which causes WITNESS to whine from within UMA. Current temporary solution: force all UMA allocations to be M_NOWAIT from within UMA for now to avoid deadlocks unless WITNESS is defined and we can determine with certainty that we're not holding any locks when we're M_WAITOK. - I've seen at least one weird socketbuffer empty-but- mbuf-still-attached panic. I don't believe this to be related to mbuma but please keep your eyes open, turn on debugging, and capture crash dumps. This change removes more code than it adds. A paper is available detailing the change and considering various performance issues, it was presented at BSDCan2004: http://www.unixdaemons.com/~bmilekic/netbuf_bmilekic.pdf Please read the paper for Future Work and implementation details, as well as credits. Testing and Debugging: rwatson, brueffer, Ketrien I. Saihr-Kesenchedra, ... Reviewed by: Lots of people (for different parts)
* Provide the _start_ctors and _stop_ctors symbols. As on i386, the addressestjr2004-05-291-0/+4
| | | | of these are the start and end of the .ctors section.
* First release of ixgb driver for the Intel(R) PRO/10GbE Family of Adapters. ↵tackerman2004-05-281-0/+3
| | | | | | | | | | | This driver has been developed for use with FreeBSD, version 4.8 and later. Submitted by: Hema Joyce Reviewed by: Prafulla Deuskar Approved by: Prafulla Deuskar MFC after: 1 week
* Add pccarddevs.h and usbdevs.h as depends, ala miidevs.h, in the rightimp2004-05-261-5/+5
| | | | | | | places. This should have been committed last night with the rest of my changes, but wasn't. Pointy hat to: imp
* MFi386: revision 1.493.nyan2004-05-261-2/+2
|
* MFamd64:bde2004-05-261-2/+2
| | | | | | | | | | | | | | | | | | | | Fixed profiling of trap, syscall and interrupt handlers and some ordinary functions, essentially by backing out half of rev.1.106 of i386/exception.s. The handlers must be between certain labels for the purposes of profiling, and this was broken by scattering them in separately compiled .s files, especially for ordinary functions that ended up between the labels. Merge the files by #including them as before, except with different pathnames and better comments and organization. Changes to the scattered files are minimal -- just move the labels to the file that does the #includes. This also partly fixes profiling of IPIs -- all IPI handlers are now correctly classified as interrupt handlers, but many are still missing mcount calls. vm86bios.s is included as before, but it is now between the labels for interrupt handlers again, which seems to be wrong since half of it is for a non-interrupt handler.
* Move to generating pccarddevs.h on the fly, both for the kernel andimp2004-05-262-5/+17
| | | | | | | the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
* Fix disorder introduce in 1.862 by sorting emu10k before miidevs.h,imp2004-05-261-5/+5
| | | | | | rather than after. bde inspired words: disorder
* devlist2h.awk is too generic a name for what it does. It reallyimp2004-05-262-4/+4
| | | | | | | | converts miidevs to a .h file, so rename to reflect that. The usb and pccard versions have also been renamed and will be hooked into the build system shortly (I've made the conversion in my p4 tree).
* Fixed profiling of trap, syscall and interrupt handlers and somebde2004-05-241-3/+3
| | | | | | | | | | | | | | | ordinary functions, essentially by backing out half of rev.1.115 of amd64/exception.S. The handlers must be between certain labels for the purposes of profiling, and this was broken by scattering them in separately compiled .S files, especially for ordinary functions that ended up between the labels. Merge the files by #including them as before, except with different pathnames and better comments and organization. Changes to the scattered files are minimal -- just move the labels to the file that does the #includes. This also partly fixes profiling of IPIs -- all IPI handlers are now correctly classified as interrupt handlers, but many are still missing mcount calls.
* Fixed insertion sort error in previous commit (prof_machdep.c).bde2004-05-241-4/+4
| | | | | | Fixed apparently-intentional disorder of the crypto files. Lists of files should be sorted first on the pathname, not on the option name or subsystem.
* Build prof_machdep.c if profiling.bde2004-05-231-0/+1
| | | | | | | | | | | | | Kernel profiling for amd64's (normal and high resolution) should now compile and work as (un)well as on i386's. It works better than user profiling because: - it uses _cyg_profile_func_*() instead of .mcount(), so it doesn't suffer from gcc misspelling .mcount as mcount. - it doesn't neglect saving %rax in .mcount(). The SMP case hasn't been tested. The high resolution subcase of this uses the i8254, and as on i386's, the locking for this is deficient and the i8254 is too inefficient. The acpi timer is also too inefficient.
* - Connect geom(8) and its libraries to the build.pjd2004-05-203-0/+6
| | | | | | | | - Connect geom_stripe and geom_nop modules to the build. - Connect STRIPE and NOP classes to the LINT build. - Disconnect gconcat(8) from the build. Supported by: Wheel - Open Technologies - http://www.wheel.pl
* MFi386: Add NETGRAPH_CRONYX.nyan2004-05-181-0/+3
|
* MFi386: revision 1.492.nyan2004-05-181-0/+2
|
* Connect Cronyx Tau-PCI to the system.rik2004-05-171-0/+2
|
* o De-support fdc(4). No ia64 has ever been made with PC floppy andmarcel2004-05-171-3/+0
| | | | | the likelyhood of one ever being made is nil. o While here, de-support sio(4).
* Move fdc from isa/fd.c to dev/fdc/fdc.c. The old files wereimp2004-05-174-4/+4
| | | | | | | | repocopied. Soon there will be additional bus attachments and specialization for isa, acpi and pccard (and maybe pc98's cbus). This was approved by nate, joerg and myself. bde dissented on the new location, but appeared to be OK after some discussion.
* MFi386: numerous interrupt and acpi updatespeter2004-05-161-0/+1
|
* Enable first part of kld's on amd64. This is known to not work rightpeter2004-05-162-0/+10
| | | | | | | yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
* Remove libkern/mem*cognet2004-05-141-2/+0
|
* Remove libkern/bzero.S and libkern/memset.S.cognet2004-05-141-2/+0
|
* Define INLINE_LIMIT for arm.cognet2004-05-141-0/+3
|
* Add config magic for arm.cognet2004-05-144-0/+261
|
* MFi386: revision 1.489nyan2004-05-131-6/+6
|
* Expose USBVERBOSE as a first-class option. It will be needed soon asimp2004-05-131-0/+1
| | | | | | an option. Note that this option doesn't follow the normal USB_ or Uxxx_ convention. That's because it is this way in the upstream provider and I didn't want to change that.
* Add a driver for the watchdog timer function present on the LPC interfacedes2004-05-111-0/+1
| | | | | | | bridge in Intel ICH-series chipsets. The original implementation was by W. Daryl Hawkins of Texas A&M, but I have made substantial modifications.
* Change required config(8) version.cognet2004-05-097-7/+7
|
* - Remove the old sparc64 OFW PCI code (as opposed to the formermarius2004-05-082-4/+3
| | | | | | | | | | | | | "options OFW_NEWPCI"). This is a bit overdue, the new sparc64 OFW PCI code which is meant to replace the old one is in place for 10 months and enabled by default in GENERIC for 8 months. FreeBSD 5.2 and 5.2.1 also shipped with the new code enabled by default. - Some minor clean-up, e.g. remove functions that encapsulated the #ifdefs for OFW_NEWPCI, remove unused resp. no longer required includes, etc. Approved by: tmm, no objections on freebsd-sparc64
* Remove unwinder files that are commented-out.marcel2004-05-071-3/+0
|
* Detach i386/isa/elcr.c.nyan2004-05-061-1/+0
|
* MFi386: Add elcr.c.jhb2004-05-051-0/+1
|
* 1. Spell Cronyx Sigma-ISA and Cronyx Tau-ISA correctly.rik2004-05-051-2/+2
| | | | | | | 2. Note that ct device uses ctau name as driver name (due to name conflict with ct driver) and also mark it as a driver inside the CVS tree. MFC after: 10 days
* Cronyx Tau-PCI's driver name is "cp".rik2004-05-051-1/+1
| | | | MFC after: 10 days
* Fixed some insertion sort errors.bde2004-05-051-9/+9
|
* MFi386 (rev.1.488: demangle svr4 entries).bde2004-05-051-18/+18
|
* Fixed unformatting of svr4 entries in rev.1.326 and consistent misformattingbde2004-05-051-18/+18
| | | | of them in rev.1.358.
* Add a simple mini-driver for the ELCR register. Originally, the ELCRjhb2004-05-041-0/+1
| | | | | | | | | | | | | | | register controlled the trigger mode and polarity of EISA interrupts. However, it appears that most (all?) PCI systems use the ELCR to manage the trigger mode and polarity of ISA interrupts as well since ISA IRQs used to route PCI interrupts need to be level triggered with active low polarity. We check to see if the ELCR exists by sanity checking the value we get back ensuring that IRQS 0 (8254), 1 (atkbd), 2 (the link from the slave PIC), and 8 (RTC) are all clear indicating edge trigger and active high polarity. This mini-driver will be used by the atpic driver to manage the trigger and polarity of ISA IRQs. Also, the mptable parsing code will use this mini driver rather than examining the ELCR directly.
* Oops^2, finish switch to using the moved cy driver for pc98 by removingbde2004-05-041-1/+1
| | | | cy.c and not legacy.c here.
* Remove new options and my prevention of system freeze when the sio probeambrisko2004-05-032-3/+0
| | | | | | | returns okay when HW probe fails. This happens when comconsole flag is set but VGA console is used instead. Back out requested by: bde (He will be looking at other solutions from scratch)
* Allow geom_concat and geom_gate to be compiled in kernel.pjd2004-05-033-0/+6
|
* Add MAC_STATIC, a kernel option that disables internal MAC Frameworkrwatson2004-05-031-0/+1
| | | | | | | | | | synchronization protecting against dynamic load and unload of MAC policies, and instead simply blocks load and unload. In a static configuration, this allows you to avoid the synchronization costs associated with introducing dynamicism. Obtained from: TrustedBSD Project Sponsored by: DARPA, McAfee Research
OpenPOWER on IntegriCloud