|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
| #
7cd79421 |
| 24-Apr-2018 |
Mateusz Guzik <[email protected]> |
dtrace: depessimize dtmalloc when dtrace is active
Each malloc/free was testing dtrace_malloc_enabled and forcing
extra reads from the malloc type struct to see if perhaps a
dtmalloc probe was on.
dtrace: depessimize dtmalloc when dtrace is active
Each malloc/free was testing dtrace_malloc_enabled and forcing
extra reads from the malloc type struct to see if perhaps a
dtmalloc probe was on.
Treat it like lockstat and sdt: have a global bolean.
show more ...
|
|
Revision tags: release/10.4.0 |
|
| #
47f11baa |
| 27-Sep-2017 |
Mark Johnston <[email protected]> |
Use C99 initializers for DTrace provider methods.
This makes the definitions easier to read and more cscope-friendly.
MFC after: 1 week
|
|
Revision tags: release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0 |
|
| #
837610eb |
| 28-Jun-2013 |
Mark Johnston <[email protected]> |
The dtmalloc provider uses the short description of a malloc type as the
function name of its corresponding DTrace probes. These descriptions may
contain whitespace, but probe names cannot, so just r
The dtmalloc provider uses the short description of a malloc type as the
function name of its corresponding DTrace probes. These descriptions may
contain whitespace, but probe names cannot, so just replace any whitespace
with underscores when creating probes.
MFC after: 1 week
show more ...
|
|
Revision tags: release/8.4.0, release/9.1.0, release/8.3.0, release/7.4.0, release/8.2.0, release/8.1.0, release/7.3.0, release/8.0.0, release/7.2.0, release/7.1.0, release/6.4.0 |
|
| #
91eaf3e1 |
| 23-May-2008 |
John Birrell <[email protected]> |
Custom DTrace kernel module files plus FreeBSD-specific DTrace providers.
|