FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.0.0 2016-05-03T03:41:25Z 2016-05-03T03:41:25Z Pedro F. Giffuni pfg@FreeBSD.org 2016-05-03T03:41:25Z urn:sha1:453130d9bfc1c6d68b366dfcb041689d69f81295 Most affect comments, very few have user-visible effects. 2016-02-27T03:38:01Z Justin Hibbits jhibbits@FreeBSD.org 2016-02-27T03:38:01Z urn:sha1:c47476d7e6801deffc8b3c057d0fbf7d2335a0c2 Most calls to bus_alloc_resource() use "anywhere" as the range, with a given count. Migrate these to use the new bus_alloc_resource_anywhere() API. Reviewed by: jhb Differential Revision: https://reviews.freebsd.org/D5370 2014-08-20T16:07:17Z John Baldwin jhb@FreeBSD.org 2014-08-20T16:07:17Z urn:sha1:669eac89c5420b8ca9579788d17259ebb90c0178 2014-06-28T03:56:17Z Hans Petter Selasky hselasky@FreeBSD.org 2014-06-28T03:56:17Z urn:sha1:af3b2549c4ba2ef00a7cbb4cb6836598bf0aefbe 2014-06-27T22:05:21Z Glen Barber gjb@FreeBSD.org 2014-06-27T22:05:21Z urn:sha1:37a107a407cdb47ee0f4c4337e369e9973b34076 These changes prevent sysctl(8) from returning proper output, such as: 1) no output from sysctl(8) 2) erroneously returning ENOMEM with tools like truss(1) or uname(1) truss: can not get etype: Cannot allocate memory 2014-06-27T16:33:43Z Hans Petter Selasky hselasky@FreeBSD.org 2014-06-27T16:33:43Z urn:sha1:3da1cf1e88f8448bb10c5f778ab56ff65c7a6938 there is an environment variable which shall initialize the SYSCTL during early boot. This works for all SYSCTL types both statically and dynamically created ones, except for the SYSCTL NODE type and SYSCTLs which belong to VNETs. A new flag, CTLFLAG_NOFETCH, has been added to be used in the case a tunable sysctl has a custom initialisation function allowing the sysctl to still be marked as a tunable. The kernel SYSCTL API is mostly the same, with a few exceptions for some special operations like iterating childrens of a static/extern SYSCTL node. This operation should probably be made into a factored out common macro, hence some device drivers use this. The reason for changing the SYSCTL API was the need for a SYSCTL parent OID pointer and not only the SYSCTL parent OID list pointer in order to quickly generate the sysctl path. The motivation behind this patch is to avoid parameter loading cludges inside the OFED driver subsystem. Instead of adding special code to the OFED driver subsystem to post-load tunables into dynamically created sysctls, we generalize this in the kernel. Other changes: - Corrected a possibly incorrect sysctl name from "hw.cbb.intr_mask" to "hw.pcic.intr_mask". - Removed redundant TUNABLE statements throughout the kernel. - Some minor code rewrites in connection to removing not needed TUNABLE statements. - Added a missing SYSCTL_DECL(). - Wrapped two very long lines. - Avoid malloc()/free() inside sysctl string handling, in case it is called to initialize a sysctl from a tunable, hence malloc()/free() is not ready when sysctls from the sysctl dataset are registered. - Bumped FreeBSD version to indicate SYSCTL API change. MFC after: 2 weeks Sponsored by: Mellanox Technologies 2013-02-21T07:19:50Z Warner Losh imp@FreeBSD.org 2013-02-21T07:19:50Z urn:sha1:b441301d0589e5002191b0220bb8936a17dcb2db 2009-05-29T06:41:23Z Ed Schouten ed@FreeBSD.org 2009-05-29T06:41:23Z urn:sha1:c5e30cc02b9bee4c53457d1bc4184b256ce1a569 I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future. 2009-02-07T02:14:27Z Wojciech A. Koszek wkoszek@FreeBSD.org 2009-02-07T02:14:27Z urn:sha1:e54815ad40deb91ff0695c485353eaa924432dfb using this function in simple printf() causes compile-time problems. Use conditionally enabled DPRINT() macro instead. 2008-09-08T11:41:20Z Peter Wemm peter@FreeBSD.org 2008-09-08T11:41:20Z urn:sha1:434cb989010e6ea6491c85003bbece79fb39bc22 but needs a lot more work. In particular, it has no flow control and has a tendency to race when giving commands. It still uses Giant for the tty and driver lock, but this is a keep-it-simple feature for now. Some of the [temporary] proliferation of messages lines are way too long.