Lesson plan

Kernel marker

Kernel markers were a static kernel instrumentation support mechanism for Linux kernel source code, allowing special tools such as LTTng or SystemTap to trace information exposed by these probe points. Kernel markers were declared in the kernel code by one-liners of the form: trace_mark(name, format_string, ...); Where name is the marker's unique name, and format_string describes the remaining arguments' types. A marker can be on or off depending on whether a probe is connected to it or not. Code which wants to hook into a trace point first calls: int marker_probe_register(const char *name, const char *format_string, marker_probe_func *probe, void *pdata); to register its probe callback with the marker point ( pdata is a private data value that the code wants to pass to the probe ). Later, the probe is turned on and off using: int marker_arm(const char *name); int marker_disarm(const char *name); Using markers has a negligible overhead thanks in part to Immediate Values, another support mechanism that embeds switches in the code that can be dynamically turned on and off, without using a memory reference and thus saving cache lines. The initial motivation to create this static instrumentation infrastructure was the large performance overhead induced by the predating dynamic instrumentation mechanism Kprobe mechanism, which depends on breakpoints.…

Back to article

Article summary

Kernel markers were a static kernel instrumentation support mechanism for Linux kernel source code, allowing special tools such as LTTng or SystemTap to trace information exposed by these probe points. Kernel markers were declared in the kernel code by one-liners of the form: trace_mark(name, format_string, ...); Where name is the marker's unique name, and format_string describes the remaining arguments' types. A marker can be on or off depending on whether a probe is connected to it or not. Code which wants to hook into a trace point first calls: int marker_probe_register(const char *name, const char *format_string, marker_probe_func *probe, void *pdata); to register its probe callback with the marker point ( pdata is a private data value that the code wants to pass to the probe ). Later, the probe is turned on and off using: int marker_arm(const char *name); int marker_disarm(const char *name); Using markers has a negligible overhead thanks in part to Immediate Values, another support mechanism that embeds switches in the code that can be dynamically turned on and off, without using a memory reference and thus saving cache lines. The initial motivation to create this static instrumentation infrastructure was the large performance overhead induced by the predating dynamic instrumentation mechanism Kprobe mechanism, which depends on breakpoints.…

Key claims

  1. release date: 2008-01-24 — source: Wikipedia · confidence 0.95
  2. release date: 2008-12-25 — source: Wikipedia · confidence 0.95
  3. release date: 2009-12-03 — source: Wikipedia · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "2008-01-24". What evidence would count against this claim?
  3. The record states that the release date is "2008-12-25". What evidence would count against this claim?
  4. The record states that the release date is "2009-12-03". What evidence would count against this claim?
  5. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  6. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.