FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F6.2.0 2006-10-09T18:41:37Z 2006-10-09T18:41:37Z Simon L. B. Nielsen simon@FreeBSD.org 2006-10-09T18:41:37Z urn:sha1:194d254cbd8f57cd05771d21f3315625578a50c6 - Remove SCHED_ULE from GENERIC to better avoid foot-shooting by unsuspecting users. - Add a comment in NOTES about experimental status of SCHED_ULE. - Make warning about experimental status in sched_ule(4) a bit stronger. This is not an exact MFC since we don't have alpha in -CURRENT. Approved by: re (kensmith) 2006-07-13T08:11:46Z Xin LI delphij@FreeBSD.org 2006-07-13T08:11:46Z urn:sha1:6c6aa05bffcedce70c8d689fbc6674d80f8d610c 2006-07-11T17:34:13Z Sam Leffler sam@FreeBSD.org 2006-07-11T17:34:13Z urn:sha1:81461b2ee7554a02cb036263ee166a023c5d413a 2006-06-03T23:10:46Z Wilko Bulte wilko@FreeBSD.org 2006-06-03T23:10:46Z urn:sha1:800bc153b5918d063f24d7e3ad94a0d65d1eec74 showing lockmgr) encountered with "make -jX release" for X > 1 and running on SMP hardware are gone once PREEMPTION is disabled. Better ideas on fixing the problem are more than welcome. 2006-05-31T21:42:11Z Wilko Bulte wilko@FreeBSD.org 2006-05-31T21:42:11Z urn:sha1:9a9817432fd5dae01b41b9289708b0478154334f The RL8169s worked just fine for me on my release building DS20E with the CVS repo mounted via NFS. For EUR 10 that is not too bad :) 2006-05-28T11:15:16Z Wilko Bulte wilko@FreeBSD.org 2006-05-28T11:15:16Z urn:sha1:2ea05c8eed82d444758e5a8e9ec8096def1b9bac I encountered repeatable Unaligned access panics similar to: fatal kernel trap: trap entry = 0x4 (unaligned access fault) cpuid = 0 faulting va = 0xfffffc0000fae1c2 opcode = 0x28 register = 0x1 pc = 0xfffffc00004d07dc ra = 0xfffffc00004d0a1c sp = 0xfffffe0031875bc0 curthread = 0xfffffc007da237a0 pid = 2, comm = g_event These occur when a floppy or a CD (the 6.1R install CD will do in most cases) is in the drive during boot. A floppy or CD inserted *after* the system was booted did not give me this problem. Interestingly enough booting from the 6.1-R install CD sometimes caused the crash, sometimes it did not. When it did not panic an installation of 6.1-R was possible without any incidents. A subsequent boot from HD with the CD still present sometimes(...) worked fine, sometimes paniced. Taking GEOM_GPT out of the kernel config file allows booting without incidents. We do not need GPT on Alpha, so this is the easy way out. Discussed with: phk 2006-03-14T21:04:46Z John Baldwin jhb@FreeBSD.org 2006-03-14T21:04:46Z urn:sha1:0c26452ae6d6f44ade8c6208ba768348766ff9dc timecounter in UP kernels on SMP machines and, and G/C some cruft. Approved by: re (scottl) 2006-03-13T03:05:37Z Jeff Roberson jeff@FreeBSD.org 2006-03-13T03:05:37Z urn:sha1:fce02f8d711a779dad1d5b42650e7cbe41253948 VFS SMP fixes, stack api, softupdates fixes. Sponsored by: Isilon Systems, Inc. Approved by: re (scottl) 2006-03-10T19:37:35Z John Baldwin jhb@FreeBSD.org 2006-03-10T19:37:35Z urn:sha1:272174a97c6ca574b8824883b21a3d2147c71e39 associated changes. More details below: Remove public declarations of variables that were forgotten when they were made static. Revision Changes Path 1.31 +0 -1 src/sys/sys/interrupt.h Make sure the interrupt is masked before processing it, or bad things can happen. Revision Changes Path 1.10 +3 -3 src/sys/arm/arm/intr.c Reorganize the interrupt handling code a bit to make a few things cleaner and increase flexibility to allow various different approaches to be tried in the future. - Split struct ithd up into two pieces. struct intr_event holds the list of interrupt handlers associated with interrupt sources. struct intr_thread contains the data relative to an interrupt thread. Currently we still provide a 1:1 relationship of events to threads with the exception that events only have an associated thread if there is at least one threaded interrupt handler attached to the event. This means that on x86 we no longer have 4 bazillion interrupt threads with no handlers. It also means that interrupt events with only INTR_FAST handlers no longer have an associated thread either. - Renamed struct intrhand to struct intr_handler to follow the struct intr_foo naming convention. This did require renaming the powerpc MD struct intr_handler to struct ppc_intr_handler. - INTR_FAST no longer implies INTR_EXCL on all architectures except for powerpc. This means that multiple INTR_FAST handlers can attach to the same interrupt and that INTR_FAST and non-INTR_FAST handlers can attach to the same interrupt. Sharing INTR_FAST handlers may not always be desirable, but having sio(4) and uhci(4) fight over an IRQ isn't fun either. Drivers can always still use INTR_EXCL to ask for an interrupt exclusively. The way this sharing works is that when an interrupt comes in, all the INTR_FAST handlers are executed first, and if any threaded handlers exist, the interrupt thread is scheduled afterwards. This type of layout also makes it possible to investigate using interrupt filters ala OS X where the filter determines whether or not its companion threaded handler should run. - Aside from the INTR_FAST changes above, the impact on MD interrupt code is mostly just 's/ithread/intr_event/'. - A new MI ddb command 'show intrs' walks the list of interrupt events dumping their state. It also has a '/v' verbose switch which dumps info about all of the handlers attached to each event. - We currently don't destroy an interrupt thread when the last threaded handler is removed because it would suck for things like ppbus(8)'s braindead behavior. The code is present, though, it is just under #if 0 for now. - Move the code to actually execute the threaded handlers for an interrrupt event into a separate function so that ithread_loop() becomes more readable. Previously this code was all in the middle of ithread_loop() and indented halfway across the screen. - Made struct intr_thread private to kern_intr.c and replaced td_ithd with a thread private flag TDP_ITHREAD. - In statclock, check curthread against idlethread directly rather than curthread's proc against idlethread's proc. (Not really related to intr changes) Tested on: alpha, amd64, i386, sparc64 Tested on: arm, ia64 (older version of patch by cognet and marcel) Revision Changes Path 1.88 +43 -29 src/sys/alpha/alpha/interrupt.c 1.38 +5 -5 src/sys/alpha/isa/isa.c 1.16 +58 -52 src/sys/amd64/amd64/intr_machdep.c 1.6 +1 -1 src/sys/amd64/include/intr_machdep.h 1.16 +2 -2 src/sys/amd64/isa/atpic.c 1.11 +28 -22 src/sys/arm/arm/intr.c 1.462 +2 -2 src/sys/dev/sio/sio.c 1.6 +1 -1 src/sys/dev/uart/uart_kbd_sun.c 1.24 +2 -2 src/sys/dev/uart/uart_tty.c 1.15 +58 -52 src/sys/i386/i386/intr_machdep.c 1.8 +1 -1 src/sys/i386/include/intr_machdep.h 1.21 +2 -2 src/sys/i386/isa/atpic.c 1.52 +32 -25 src/sys/ia64/ia64/interrupt.c 1.180 +3 -2 src/sys/kern/kern_clock.c 1.127 +437 -270 src/sys/kern/kern_intr.c 1.206 +0 -1 src/sys/kern/subr_witness.c 1.6 +3 -3 src/sys/powerpc/include/intr_machdep.h 1.7 +35 -32 src/sys/powerpc/powerpc/intr_machdep.c 1.14 +1 -1 src/sys/sparc64/include/intr_machdep.h 1.24 +43 -36 src/sys/sparc64/sparc64/intr_machdep.c 1.32 +36 -36 src/sys/sys/interrupt.h 1.440 +1 -3 src/sys/sys/proc.h Catch up with interrupt-thread changes. Revision Changes Path 1.32 +1 -1 src/sys/dev/zs/zs.c Catch up with new interrupt handling code. Revision Changes Path 1.16 +3 -3 src/sys/netgraph/bluetooth/drivers/bt3c/ng_bt3c_pccard.c Catch up with new interrupt handling code. Revision Changes Path 1.162 +2 -2 src/sys/dev/cy/cy.c 1.101 +2 -2 src/sys/dev/rc/rc.c Catch up with new interrupt handling code. Revision Changes Path 1.50 +2 -2 src/sys/dev/cx/if_cx.c 1.41 +1 -1 src/sys/dev/sab/sab.c 1.238 +2 -2 src/sys/pc98/cbus/sio.c Add a swi_remove() function to teardown software interrupt handlers. For now it just calls intr_event_remove_handler(), but at some point it might also be responsible for tearing down interrupt events created via swi_add. Revision Changes Path 1.128 +17 -0 src/sys/kern/kern_intr.c 1.33 +1 -0 src/sys/sys/interrupt.h - Use swi_remove() to teardown swi handlers rather than intr_event_remove_handler(). - Remove tty: prefix from a couple of swi handler names. Revision Changes Path 1.51 +1 -1 src/sys/dev/cx/if_cx.c 1.102 +2 -2 src/sys/dev/rc/rc.c 1.42 +1 -1 src/sys/dev/sab/sab.c 1.25 +1 -1 src/sys/dev/uart/uart_tty.c 1.33 +1 -1 src/sys/dev/zs/zs.c 1.17 +2 -2 src/sys/netgraph/bluetooth/drivers/bt3c/ng_bt3c_pccard.c Remove a stray return statement in the interrupt dispatch function that caused a premature exit after calling a fast interrupt handler and bypassing a much needed critical_exit() and the scheduling of the interrupt thread for non-fast handlers. In short: unbreak :-) Revision Changes Path 1.53 +0 -1 src/sys/ia64/ia64/interrupt.c If we get a stray interrupt, return after logging it. In the extremely rare case of a stray interrupt to an unregistered source (such as a stray interrupt from the 8259As when using APIC), this could result in a page fault when it tried to walk the list of interrupt handlers to execute INTR_FAST handlers. This bug was introduced with the intr_event changes, so it's not present in 5.x or 6.x. Submitted by: Mark Tinguely tinguely at casselton dot net Revision Changes Path 1.17 +1 -0 src/sys/amd64/amd64/intr_machdep.c 1.16 +1 -0 src/sys/i386/i386/intr_machdep.c Approved by: re (scottl) 2006-03-07T18:08:09Z John Baldwin jhb@FreeBSD.org 2006-03-07T18:08:09Z urn:sha1:37a4ca60365faf382f53b8d4f1582c0806285366 exit1() to block until any current PHOLD's are released. This includes Simplifying the cleanup code in kern_ptrace() and removing the now unnecessary vmspace ref counting magic from proc_rwmem(). Also, the locking for ptrace_single_step(), ptrace_set_pc(), and ptrace_clear_single_step() have been fixed to be consistent across the tree. Approved by: re (scottl)