FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2012-05-13T17:04:46Z 2012-05-13T17:04:46Z Andriy Gapon avg@FreeBSD.org 2012-05-13T17:04:46Z urn:sha1:33a662c963044ea3fcc5293a131e9da2abe506fe kernel 2012-04-12T00:38:34Z Nathan Whitehorn nwhitehorn@FreeBSD.org 2012-04-12T00:38:34Z urn:sha1:40bb25ee63eea65619fd3e91c4479af1a58ad85e Make ofw_bus_get_node() consistently return -1 when there is no associated OF node, instead of a random mixture of 0 and -1. Update all checks for 0 to check for -1 instead. 2012-02-01T21:11:06Z Marius Strobl marius@FreeBSD.org 2012-02-01T21:11:06Z urn:sha1:3b992a9ac5dcb91fcd4b993ad5861fbbd540ed6c Implement OF_printf() using kvprintf() directly, avoiding to use a buffer and allowing to handle newlines properly. 2011-12-31T14:12:12Z Hans Petter Selasky hselasky@FreeBSD.org 2011-12-31T14:12:12Z urn:sha1:0105e7b57ec82d3d157edb9f4322f29f05d54f6e Use DEVMETHOD_END to mark end of device methods. Remove superfluous device methods. Add some missing __FBSBID() macros. 2011-11-19T12:55:32Z Marius Strobl marius@FreeBSD.org 2011-11-19T12:55:32Z urn:sha1:0c831fa6bd42962aaa557c12cb1cecf1b21c11bf As it turns out, r186347 actually is insufficient to avoid the use of the curthread-accessing part of mtx_{,un}lock(9) when using a r210623-style curthread implementation on sparc64, crashing the kernel in its early cycles as PCPU isn't set up, yet (and can't be set up as OFW is one of the things we need for that, which leads to a chicken-and-egg problem). What happens is that due to the fact that the idea of r210623 actually is to allow the compiler to cache invocations of curthread, it factors out obtaining curthread needed for both mtx_lock(9) and mtx_unlock(9) to before the branch based on kobj_mutex_inited when compiling the kernel without the debugging options. So change kobj_class_compile_static(9) to just never acquire kobj_mtx, effectively restricting it to its documented use, and add a kobj_init_static(9) for initializing objects using a class compiled with the former and that also avoids using mutex(9) (and malloc(9)). Also assert in both of these functions that they are used in their intended way only. While at it, inline kobj_register_method() and kobj_unregister_method() as there wasn't much point for factoring them out in the first place and so that a reader of the code has to figure out the locking for fewer functions missing a KOBJ_ASSERT. Tested on powerpc{,64} by andreast. Reviewed by: nwhitehorn (earlier version), jhb Approved by: re (kib) 2011-08-27T14:24:27Z Robert Watson rwatson@FreeBSD.org 2011-08-27T14:24:27Z urn:sha1:e5a0927394502ac7d7d0383c523490eb35f773dc improvements: (1) Implement new model in previously missed at91 UART driver (2) Move BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER from opt_comconsole.h to opt_kdb.h (spotted by np) (3) Garbage collect now-unused opt_comconsole.h MFC after: 3 weeks Approved by: re (bz) 2011-08-26T21:46:36Z Robert Watson rwatson@FreeBSD.org 2011-08-26T21:46:36Z urn:sha1:4cf75455890c103c9a66cb791e88998aafd4f8ce accessible: (1) Always compile in support for breaking into the debugger if options KDB is present in the kernel. (2) Disable both by default, but allow them to be enabled via tunables and sysctls debug.kdb.break_to_debugger and debug.kdb.alt_break_to_debugger. (3) options BREAK_TO_DEBUGGER and options ALT_BREAK_TO_DEBUGGER continue to behave as before -- only now instead of compiling in break-to-debugger support, they change the default values of the above sysctls to enable those features by default. Current kernel configurations should, therefore, continue to behave as expected. (4) Migrate alternative break-to-debugger state machine logic out of individual device drivers into centralised KDB code. This has a number of upsides, but also one downside: it's now tricky to release sio spin locks when entering the debugger, so we don't. However, similar logic does not exist in other device drivers, including uart. (5) dcons requires some special handling; unlike other console types, it allows overriding KDB's own debugger selection, so we need a new interface to KDB to allow that to work. GENERIC kernels in -CURRENT will now support break-to-debugger as long as appropriate boot/run-time options are set, which should improve the debuggability of BETA kernels significantly. MFC after: 3 weeks Reviewed by: kib, nwhitehorn Approved by: re (bz) 2010-11-11T13:42:46Z Rafal Jaworowski raj@FreeBSD.org 2010-11-11T13:42:46Z urn:sha1:96fe0b35528bdf9a7dd5ca54433e49807a5a9eb9 Submitted by: nwhitehorn 2010-11-09T19:45:29Z Nathan Whitehorn nwhitehorn@FreeBSD.org 2010-11-09T19:45:29Z urn:sha1:0bad71a347f1d486612b930eb202e22961a33632 does-not-exist error when no client interface module is installed instead of dereferencing NULL pointers. This eases implementation of platforms that may or may not have Open Firmware. 2010-09-11T18:55:00Z Marius Strobl marius@FreeBSD.org 2010-09-11T18:55:00Z urn:sha1:cdb25d827efda15643a73b0b15f1b724b6e83429 Reviewed by: nwhitehorn