FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=stable%2F9 2013-11-16T10:47:58Z 2013-11-16T10:47:58Z Alexander Motin mav@FreeBSD.org 2013-11-16T10:47:58Z urn:sha1:615688035b41a56ca7e330e983f37fcd3f685b40 Fix several typos PR: kern/176054 2013-04-05T08:22:11Z Alexander Motin mav@FreeBSD.org 2013-04-05T08:22:11Z urn:sha1:1139d398ea93668ee65ae02b8ceab630ca9e5487 Mark MALLOC_DEFINEs static that have no corresponding MALLOC_DECLAREs. This means that their use is restricted to a single C file. 2013-03-06T11:07:59Z Andriy Gapon avg@FreeBSD.org 2013-03-06T11:07:59Z urn:sha1:a572bb048dc64f8115971e01e00e72013e1aa0ca the most common x86 buses 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) 2009-11-28T11:13:50Z Ed Schouten ed@FreeBSD.org 2009-11-28T11:13:50Z urn:sha1:f02d50a3c86eebd2400fef614468c7b7ff79e4ce 2009-10-02T22:30:44Z Marcel Moolenaar marcel@FreeBSD.org 2009-10-02T22:30:44Z urn:sha1:0acb3c4aacb5cb3650e5540a56c28f6325da3c62 interface is fairly simple WRT dealing with flow control, but needed 2 new RX buffer functions with "get-char-from-buf" separated from "advance-buf-pointer" so that the pointer could be advanced only when ttydisc_rint() succeeded. MFC after: 1 week 2008-08-20T08:31:58Z Ed Schouten ed@FreeBSD.org 2008-08-20T08:31:58Z urn:sha1:bc093719ca478fe10b938cef32c30b528042cbcd The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan 2008-05-04T23:29:38Z Peter Wemm peter@FreeBSD.org 2008-05-04T23:29:38Z urn:sha1:43d7128c1450d36af259094b7cf39c0c4d17908c ALT_BREAK_TO_DEBUGGER. In addition to "Enter ~ ctrl-B" (to enter the debugger), there is now "Enter ~ ctrl-P" (force panic) and "Enter ~ ctrl-R" (request clean reboot, ala ctrl-alt-del on syscons). We've used variations of this at work. The force panic sequence is best used with KDB_UNATTENDED for when you just want it to dump and get on with it. The reboot request is a safer way of getting into single user than a power cycle. eg: you've hosed the ability to log in (pam, rtld, etc). It gives init the reboot signal, which causes an orderly reboot. I've taken my best guess at what the !x86 and non-sio code changes should be. This also makes sio release its spinlock before calling KDB/DDB. 2007-12-25T17:52:02Z Robert Watson rwatson@FreeBSD.org 2007-12-25T17:52:02Z urn:sha1:3de213cc00f2889d2cd693968fd38c10a7f5def1 for that argument. This will allow DDB to detect the broad category of reason why the debugger has been entered, which it can use for the purposes of deciding which DDB script to run. Assign approximate why values to all current consumers of the kdb_enter() interface.