From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "William Cohen" <wcohen@redhat.com>
Cc: "Roland McGrath" <roland@redhat.com>,
"SystemTap" <systemtap@sources.redhat.com>
Subject: RE: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes)
Date: Fri, 31 Mar 2006 02:36:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06D019F4@scsmsx403.amr.corp.intel.com> (raw)
William Cohen wrote:
> Sometimes the options are turned off on purpose. Do the Xen kernels
> build with "CONFIG_KPROBES=y"?
yes
> 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?
In order to get the debug info working, I removed the change to
lib/Kconfig.debug (mentioned in my other email), but left the change in
arch/x86_64/kernel/entry-xen.S. I suspect that more will need to be
done here before CONFIG_DEBUG_INFO really works completely, as there's
probably some reason it was disabled, but this is good enough for
testing SystemTap.
On both xen0 and xenU, all pass-5 tests succeed, except those that use
timer.profile. (systemtap.base/timers.stp and
systemtap.maps/pmap_agg_overflow.stp). It seems that the timer.profile
thinks it is registered successfully, but the callback is never
triggered. I will investigate this further...
Josh
next reply other threads:[~2006-03-31 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 2:36 Stone, Joshua I [this message]
2006-03-31 14:07 ` William Cohen
-- strict thread matches above, loose matches on Subject: below --
2006-03-31 20:38 Stone, Joshua I
2006-03-30 21:18 Stone, Joshua I
2006-03-30 1:05 Stone, Joshua I
2006-03-30 14:44 ` William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CBDB88BFD06F7F408399DBCF8776B3DC06D019F4@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).