veyepar: See what your computer is doing with Ftrace utilities

Author(s):	Steven Rostedt
Location	A3
Date	jan Wed 23	Days Raw Files
Start	10:40	First Raw Start	10:36
Duration	0:100:0	Offset	0:03:51
End	12:20	Last Raw End	12:22
Chapters	00:00 0:00:18 0:00:27 0:00:29 0:01:01 0:02:50 0:26:02 0:47:57 0:48:04 1:17:07 1:30:50
Total cuts_time	91 min.

https://2019.linux.conf.au/schedule/presentation/130/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public tweet mp4 svg png

assets release.pdf See_what_your_computer_is_doing_with_Ftrace_utilities.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Ftrace is the official tracer of the Linux kernel. It allows you to see what is happening in the black box that the applications sit on. Ftrace is a very powerful tool, but like all tools, it is useless if you don't know how to use it, or even know its full potential. This tutorial will teach you how to use Ftrace from the command line (all major distributions have Ftrace enabled), as well as how to use trace-cmd and finally, if time allows, the new KernelShark. trace-cmd and KernelShark can be easily downloaded from Steven's git repository on kernel.org (best to get the latest even though your distribution may have an older version available). Steven will first walk you through some of the main commands to display how Ftrace can show you how your applications are being scheduled in, how many page faults they are taking, and even see what other applications may be interfering with your main application. Some of these can be used to see if there's any rouge applications running on your system. Then Steven will walk you through how to use trace-cmd as it allows you to have even more flexibility with its post processing analysis. Finally, an introduction to the new KernelShark, which shows a graphic display of the data that you have retrieved.

In order to get the most from this tutorial, it is recommend that you:
1) Have a laptop running a recent Linux distribution (Running in a VM will work too)
2) Download and install the most recent trace-cmd and KernelShark
  $ git clone git://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git
  $ cd trace-cmd
  $ make
  $ less kernel-shark-qt/README # to make sure you have all the dependencies
  $ make gui
  $ make doc
  $ sudo make install
  $ sudo make install_gui
  $ sudo make install_doc
3) It will be helpful if you download the source code of the kernel that is running on your laptop
4) Having the debug info of that kernel can also be useful

Note, 3 and 4 above are helpful but not required.

Comment:

production notes