Using virtualization for online kernel profiling, code coverage and instrumentation

Eviatar Khen*, Nezer J. Zaidenberg, Amir Averbuch

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Kernel development is considered more challenging than user space development, partly due the lack of adequate development tools. We present LgDb, an innovative framework for kernel profiling, code coverage and instrumentation. LgDb is built on top of Lguest and allows running inspected kernel modules on virtual environment. The innovation lies on the fact that Lguest hypervisor takes active part in the kernel development process. Unlike previous approaches, that used standard kernel profilers on a guest, we enlist the hypervisor to our aid to achieve better profiling of inspected kernel modules. LgDb strives to provide generic environment for running performance evaluation and checking decision coverage for any inspected kernel module.

Original languageEnglish
Title of host publicationProceedings of the 2011 International Symposium on Performance Evaluation of Computer and Telecommunication Systems, SPECTS 2011
Pages104-110
Number of pages7
StatePublished - 2011
Event2011 International Symposium on Performance Evaluation of Computer and Telecommunication Systems, SPECTS 2011 - The Hague, Netherlands
Duration: 27 Jun 201130 Jun 2011

Publication series

NameProceedings of the 2011 International Symposium on Performance Evaluation of Computer and Telecommunication Systems, SPECTS 2011

Conference

Conference2011 International Symposium on Performance Evaluation of Computer and Telecommunication Systems, SPECTS 2011
Country/TerritoryNetherlands
CityThe Hague
Period27/06/1130/06/11

Keywords

  • Code Coverage
  • Debugging
  • Lguest
  • Linux Kernel
  • Profiling
  • Virtualization

Fingerprint

Dive into the research topics of 'Using virtualization for online kernel profiling, code coverage and instrumentation'. Together they form a unique fingerprint.

Cite this