Abstract: Providing dynamic instrumentation using domain-specific monitoring-language-to-kernel-bytecode compilation is disclosed. An instrumentation program file is converted by a compilation engine into multiple bytecode sections. A load and execute engine identifies which sections can be executed in kernel space and which can be executed in user space. The sections to be executed in kernel space are then loaded into a kernel space bytecode interpreter for execution, while the sections to be executed in user space are concurrently executed by a user space bytecode interpreter of the load and execute engine. In some examples, the load and execute engine may provide global variables that are accessible by both the kernel space and the user space, and that facilitate data exchange between the kernel space bytecode interpreter and the user space bytecode interpreter.

Abstract: Providing dynamic instrumentation using domain-specific monitoring-language-to-kernel-bytecode compilation is disclosed. An instrumentation program file is converted by a compilation engine into multiple bytecode sections. A load and execute engine identifies which sections can be executed in kernel space and which can be executed in user space. The sections to be executed in kernel space are then loaded into a kernel space bytecode interpreter for execution, while the sections to be executed in user space are concurrently executed by a user space bytecode interpreter of the load and execute engine. In some examples, the load and execute engine may provide global variables that are accessible by both the kernel space and the user space, and that facilitate data exchange between the kernel space bytecode interpreter and the user space bytecode interpreter.