Changeset View
Changeset View
Standalone View
Standalone View
share/man/man4/boottrace.4
Show All 17 Lines | |||||
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | ||||
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | ||||
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | ||||
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | ||||
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | ||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | ||||
.\" SUCH DAMAGE. | .\" SUCH DAMAGE. | ||||
.\" | .\" | ||||
.Dd March 4, 2022 | .Dd July 1, 2022 | ||||
.Dt BOOTTRACE 4 | .Dt BOOTTRACE 4 | ||||
.Os | .Os | ||||
.Sh NAME | .Sh NAME | ||||
.Nm boottrace | .Nm boottrace | ||||
.Nd Boot-time, run-time, and shutdown-time tracing facility | .Nd Boot-time, run-time, and shutdown-time tracing facility | ||||
.Sh SYNOPSIS | .Sh SYNOPSIS | ||||
.In sys/boottrace.h | .In sys/boottrace.h | ||||
.Sh DESCRIPTION | .Sh DESCRIPTION | ||||
.Nm | .Nm | ||||
is a kernel-userspace interface for capturing trace events | is a kernel-userspace interface for capturing trace events | ||||
during system boot and shutdown. | during system boot and shutdown | ||||
.Pq in particular, one-shot events . | |||||
pauamma_gundo.com: I think I understand what you mean, but an example (like *rummages through /var/run/dmesg.boot*… | |||||
Done Inline ActionsIf you have a good example on your mind we can surely merge it in. For the time being, I'll just commit what we have so far. 0mp: If you have a good example on your mind we can surely merge it in. For the time being, I'll… | |||||
Not Done Inline ActionsI meant an example of (what you mean by) "one-shot events". If Launching APs: 1 2 3 is one (is it? you haven't said), and unless someone who already has a 14-current running with more than 1 (v)CPU can add an example with the boottrace equivalent of that message or another suitable one before I can get to setting up a suitable VM to try, I can do that once you confirm it counts as a one-shot event. pauamma_gundo.com: I meant an example of (what you mean by) "one-shot events". If `Launching APs: 1 2 3` is one… | |||||
.Pp | .Pp | ||||
Event annotations are present in: | Event annotations are present in: | ||||
.Bl -bullet -compact | .Bl -bullet -compact | ||||
.It | .It | ||||
the boot and shutdown paths in the | the boot and shutdown paths in the | ||||
kernel | kernel | ||||
.It | .It | ||||
some key system utilities | some key system utilities | ||||
▲ Show 20 Lines • Show All 176 Lines • Show Last 20 Lines |
I think I understand what you mean, but an example (like *rummages through /var/run/dmesg.boot* the boottrace equivalent of "Launching APs: 1 2 3") may confirm my guess - or the guess of other semicasual readers.