<\/code><\/code><\/p>\nWhere:
\n– ‘filter’: defines a region that will be traced.
\n– ‘start’: defines an address at which tracing will begin.
\n– ‘stop’: defines an address at which tracing will stop.
\n– ‘tracestop’: defines a region in which tracing will stop.<\/p>\n
<\/code><\/code><\/p>\nis the name of the object file, is the offset to the
\ncode to trace in that file, and is the size of the region to
\ntrace. ‘start’ and ‘stop’ filters need not specify a .<\/p>\n
<\/code><\/code><\/p>\nIf no object file is specified then the kernel is assumed, in which case
\nthe start address must be a current kernel memory address.<\/p>\n
<\/code><\/code><\/p>\ncan also be specified by providing the name of a symbol. If the
\nsymbol name is not unique, it can be disambiguated by inserting #n where
\n‘n’ selects the n’th symbol in address order. Alternately #0, #g or #G
\nselect only a global symbol. can also be specified by providing
\nthe name of a symbol, in which case the size is calculated to the end
\nof that symbol. For ‘filter’ and ‘tracestop’ filters, if is
\nomitted and is a symbol, then the size is calculated to the end
\nof that symbol.<\/p>\n
<\/code><\/code><\/p>\nIf is omitted and is ‘*’, then the start and size will
\nbe calculated from the first and last symbols, i.e. to trace the whole
\nfile.
\nIf symbol names (or ‘*’) are provided, they must be surrounded by white
\nspace.<\/p>\n
<\/code><\/code><\/p>\nThe filter passed to the kernel is not necessarily the same as entered.
\nTo see the filter that is passed, use the -v option.<\/p>\n
<\/code><\/code><\/p>\nThe kernel may not be able to configure a trace region if it is not
\nwithin a single mapping. MMAP events (or \/proc\/ \/maps) can be
\nexamined to determine if that is a possibility.<\/p>\n
\n<\/code><\/p>\n<\/code><\/p>\n Multiple filters can be separated with space or comma.
\n<\/code><\/p>\nv2: Fix some typos\/broken links<\/p>\n
v3: Update gdb commands<\/p>\n","protected":false},"excerpt":{"rendered":"
What is Processor Trace Intel Processor Trace (PT) traces program execution (every branch) with low overhead. This is a cheat sheet of how to use PT with perf for common tasks It is not a full introduction to PT. Please read Adding PT to Linux perf or the links from the general PT reference page. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7,14,12,18,17,11],"tags":[],"_links":{"self":[{"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/posts\/410"}],"collection":[{"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/comments?post=410"}],"version-history":[{"count":23,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/posts\/410\/revisions"}],"predecessor-version":[{"id":445,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/posts\/410\/revisions\/445"}],"wp:attachment":[{"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/media?parent=410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/categories?post=410"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/halobates.de\/blog\/wp-json\/wp\/v2\/tags?post=410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}