Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Interprets profile/interval value as a frequency and not a number of ticks. | 2020-06-26 | 1 | -3/+3 | |
| | | | | | | Matches the behavior of other dynamic tracing tools. From Yuichiro NAITO. | ||||
* | Introduce stacktrace_save_at() and make use of it in dt(4). | 2020-03-25 | 1 | -2/+2 | |
| | | | | | | | | This variant of stacktrace_save() takes an aditionnal argument to skip an arbitrary number of frame. This allows to skip recording frames used to execute the profiling code and produces outputs easier to understand. Inputs from and ok visa@ | ||||
* | Import dt(4) a driver and framework for Dynamic Profiling. | 2020-01-21 | 1 | -0/+147 | |
The design is fairly simple: events, in the form of descriptors on a ring, are being produced in any kernel context and being consumed by a userland process reading /dev/dt. Code and hooks are all guarded under '#if NDT > 0' so this commit shouldn't introduce any change as long as dt(4) is disable in GENERIC. ok kettenis@, visa@, jasper@, deraadt@ |