Based on an email mhorne@ sent to arch@.
Details
- Reviewers
mhorne - Group Reviewers
manpages - Commits
- rG86e3fb4038ac: boottrace.4: Document that boottrace is good at tracing one-shot events
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
share/man/man4/boottrace.4 | ||
---|---|---|
38 | 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. |
share/man/man4/boottrace.4 | ||
---|---|---|
38 | If 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. |
share/man/man4/boottrace.4 | ||
---|---|---|
38 | I 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. |
"one-shot" in this context means an event that occurs once and does not repeat. So the "Launching APs" event is a good example of this, as would be:
0 44875750 15 init init(8) starting... 1 0.00 0 0
(raw output from the log)