This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes)

From: William Cohen <wcohen at redhat dot com>
To: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
Cc: Roland McGrath <roland at redhat dot com>, SystemTap <systemtap at sources dot redhat dot com>
Date: Thu, 30 Mar 2006 09:44:07 -0500
Subject: Re: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes)
References: <CBDB88BFD06F7F408399DBCF8776B3DC06CD0D51@scsmsx403.amr.corp.intel.com>

Stone, Joshua I wrote:

I found two differences in the config files that will prevent SystemTap
from running on the Xen kernels.  In 2054_FC5 and 2054_FC5kdump, the
config files have:

    CONFIG_KPROBES=y
    ...
    CONFIG_DEBUG_INFO=y

Whereas in 2054_FC5xen0 and 2054_xenU, the config files have:

# CONFIG_KPROBES is not set

... with no mention of CONFIG_DEBUG_INFO.  This might explain the
missing dwarf info in the kernel-debuginfo package.  And of course for
SystemTap we need CONFIG_KPROBES=y.

Josh

Sometimes the options are turned off on purpose. Do the Xen kernels build with "CONFIG_KPROBES=y"?

If kernels are built, do the resulting kernels actually have kprobe support? It use to be that xen kernels copy and pasted code from other arches. What additional patches are needed to bring the kprobe support in the xen kernel in line with the various architectures?

-Will

References:
- SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes)
  - From: Stone, Joshua I

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]