FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2013-12-08T21:59:46Z 2013-12-08T21:59:46Z Peter Wemm peter@FreeBSD.org 2013-12-08T21:59:46Z urn:sha1:f5fdfd5db78e4e1ab254768eaa71fe8b690867e3 of least pain I could find. 2013-11-26T08:46:27Z Andriy Gapon avg@FreeBSD.org 2013-11-26T08:46:27Z urn:sha1:d9fae5ab88a2c170075941d3cd9ba4a2a61893ed In its stead use the Solaris / illumos approach of emulating '-' (dash) in probe names with '__' (two consecutive underscores). Reviewed by: markj MFC after: 3 weeks 2013-11-25T07:38:45Z Attilio Rao attilio@FreeBSD.org 2013-11-25T07:38:45Z urn:sha1:54366c0bd7d0ea904fb9ab32460c66d57684a7cb option, unbreak the lock tracing release semantic by embedding calls to LOCKSTAT_PROFILE_RELEASE_LOCK() direclty in the inlined version of the releasing functions for mutex, rwlock and sxlock. Failing to do so skips the lockstat_probe_func invokation for unlocking. - As part of the LOCKSTAT support is inlined in mutex operation, for kernel compiled without lock debugging options, potentially every consumer must be compiled including opt_kdtrace.h. Fix this by moving KDTRACE_HOOKS into opt_global.h and remove the dependency by opt_kdtrace.h for all files, as now only KDTRACE_FRAMES is linked there and it is only used as a compile-time stub [0]. [0] immediately shows some new bug as DTRACE-derived support for debug in sfxge is broken and it was never really tested. As it was not including correctly opt_kdtrace.h before it was never enabled so it was kept broken for a while. Fix this by using a protection stub, leaving sfxge driver authors the responsibility for fixing it appropriately [1]. Sponsored by: EMC / Isilon storage division Discussed with: rstone [0] Reported by: rstone [1] Discussed with: philip 2010-08-22T11:18:57Z Rui Paulo rpaulo@FreeBSD.org 2010-08-22T11:18:57Z urn:sha1:79856499bd6f3f11cd2bd6b140d36a1183cd49ad use '-' in probe names, matching the probe names in Solaris.[1] Add userland SDT probes definitions to sys/sdt.h. Sponsored by: The FreeBSD Foundation Discussed with: rwaston [1] 2009-11-29T17:46:40Z Bjoern A. Zeeb bz@FreeBSD.org 2009-11-29T17:46:40Z urn:sha1:d8ce4673041491f138a98f779721c48507c2f233 MFC after: 5 days 2009-11-28T21:08:19Z Bjoern A. Zeeb bz@FreeBSD.org 2009-11-28T21:08:19Z urn:sha1:6f443bec58288ee7fb4e7fa519edef07796cd602 This is needed to avoid running into out of buffer situations where we cannot alloc a new buffer because we hit the array size limit (ZBUF). Use a combined allocation for the struct and the actual data buffer to not increase the number of malloc calls. [1] Defer initialization of zbuf until we actually need it. Make sure the output buffer will be large enough in all cases. Details discussed with: kib [1] Reviewed by: kib [1] MFC after: 6 days 2009-11-28T17:44:57Z Bjoern A. Zeeb bz@FreeBSD.org 2009-11-28T17:44:57Z urn:sha1:9699afb61b4e61de5c0089e6548e137f04c1ace6 replacement but only use it for inflate. For deflate use Z_FINISH as Z_SYNC_FLUSH adds a trailing marker in some cases that inflate(), despite the comment in zlib, does npt seem to cope well with, resulting in errors when uncompressing exactly fills the outbut buffer without a Z_STREAM_END and a successive call returns an error. MFC after: 6 days 2009-11-28T17:20:41Z Bjoern A. Zeeb bz@FreeBSD.org 2009-11-28T17:20:41Z urn:sha1:d9c18e56274beb0c8c989c2d0eb5d3b6562f9ec6 They are not nice but they were helpful. MFC after: 6 days 2008-10-23T15:53:51Z Dag-Erling Smørgrav des@FreeBSD.org 2008-10-23T15:53:51Z urn:sha1:1ede983cc905643549d8cae56a9d0e28fc68375f MFC after: 3 months 2005-05-30T05:01:44Z Scott Long scottl@FreeBSD.org 2005-05-30T05:01:44Z urn:sha1:e39e116ca2acbdc59c939a7ead8992d044f898d9 other header pollution that makes this work right now, but it falls over when doing a RELENG_5 -> HEAD upgrade.