Matches in DBpedia 2015-10 for { <http://dbpedia.org/resource/Kernel_marker> ?p ?o }
Showing triples 1 to 41 of
41
with 100 triples per page.
- Kernel_marker abstract "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: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: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: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. Static instrumentation can also more easily survive source code changes because the markers are in the source code.Kernel Markers consisted essentially of a C preprocessing macro which added, in the instrumented function, a branch over a function call. By doing so, neither the stack setup nor the function call are executed when instrumentation is not enabled. By identifying the branch executing stack setup andfunction call as unlikely (using the gcc built-in expect()), a hint is given to the compiler to position the tracing instructions away from cache lines involved in standard kernel execution.Two Kernel Markers drawbacks were identified which led to its replacement by Tracepoints: Type verification was limited to scalar types because the API is based on format strings. This could be problematic if pointers must be dereferenced by the tracer code. The Markers "hide" the instrumentation in the source code, keeping no global registry of the instrumentation. This makes namespace conventions and tracking of instrumentation modification difficult unless the whole kernel tree is monitored.A patch-set implementing them was merged into version 2.6.24, which was released on January 24, 2008. To address issues regarding kernel markers, Mathieu Desnoyers, their original author, implemented a simpler and more type-safe version of static probe points named Tracepoints. A patch-set implementing Tracepoints was merged into version 2.6.28, which was released on December 25, 2008. Starting then, kernel markers were slowly removed from kernel sources and eventually fully removed in Linux kernel 2.6.32, which was released on December 3, 2009.".
- Kernel_marker wikiPageExternalLink markers.txt;hb=v2.6.24.
- Kernel_marker wikiPageExternalLink 245671.
- Kernel_marker wikiPageExternalLink 291091.
- Kernel_marker wikiPageID "17242567".
- Kernel_marker wikiPageLength "5601".
- Kernel_marker wikiPageOutDegree "19".
- Kernel_marker wikiPageRevisionID "527558448".
- Kernel_marker wikiPageWikiLink Breakpoint.
- Kernel_marker wikiPageWikiLink CPU_cache.
- Kernel_marker wikiPageWikiLink C_(programming_language).
- Kernel_marker wikiPageWikiLink Cache_line.
- Kernel_marker wikiPageWikiLink Call_stack.
- Kernel_marker wikiPageWikiLink Category:Linux_kernel_features.
- Kernel_marker wikiPageWikiLink Compiler.
- Kernel_marker wikiPageWikiLink Ftrace.
- Kernel_marker wikiPageWikiLink Function_call.
- Kernel_marker wikiPageWikiLink GNU_Compiler_Collection.
- Kernel_marker wikiPageWikiLink Immediate_Value.
- Kernel_marker wikiPageWikiLink Kernel_debugger.
- Kernel_marker wikiPageWikiLink LTTng.
- Kernel_marker wikiPageWikiLink Linux_kernel.
- Kernel_marker wikiPageWikiLink Macro_(computer_science).
- Kernel_marker wikiPageWikiLink Subroutine.
- Kernel_marker wikiPageWikiLink SystemTap.
- Kernel_marker wikiPageWikiLink Tracepoint.
- Kernel_marker wikiPageWikiLink Tracing_(software).
- Kernel_marker wikiPageWikiLinkText "Kernel Markers".
- Kernel_marker wikiPageWikiLinkText "Kernel marker".
- Kernel_marker wikiPageWikiLinkText "kernel marker".
- Kernel_marker hasPhotoCollection Kernel_marker.
- Kernel_marker subject Category:Linux_kernel_features.
- Kernel_marker hypernym Mechanism.
- Kernel_marker type Organisation.
- Kernel_marker comment "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: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.".
- Kernel_marker label "Kernel marker".
- Kernel_marker sameAs m.043rgvq.
- Kernel_marker sameAs Q6394195.
- Kernel_marker sameAs Q6394195.
- Kernel_marker wasDerivedFrom Kernel_marker?oldid=527558448.
- Kernel_marker isPrimaryTopicOf Kernel_marker.