From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2054 invoked by alias); 30 Mar 2006 21:18:03 -0000 Received: (qmail 2047 invoked by uid 22791); 30 Mar 2006 21:18:02 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mga03.intel.com (HELO azsmga101-1.ch.intel.com) (143.182.124.21) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 30 Mar 2006 21:18:01 +0000 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101-1.ch.intel.com with ESMTP; 30 Mar 2006 13:17:59 -0800 Received: from scsmsx331.sc.intel.com (HELO scsmsx331.amr.corp.intel.com) ([10.3.90.4]) by azsmga001.ch.intel.com with ESMTP; 30 Mar 2006 13:17:59 -0800 X-IronPort-AV: i="4.03,147,1141632000"; d="scan'208"; a="17062264:sNHT53604754" Received: from scsmsx403.amr.corp.intel.com ([10.3.90.18]) by scsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 30 Mar 2006 13:17:59 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes) Date: Thu, 30 Mar 2006 21:18:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SystemTap vs. FC5 Xen kernels (was: 03-23-2006 Meeting minutes) Thread-Index: AcZPUEAj0EV3dPitSqKTD/rG3VDfxgEQuCWAACoj6+A= From: "Stone, Joshua I" To: "William Cohen" , "Roland McGrath" Cc: "SystemTap" X-OriginalArrivalTime: 30 Mar 2006 21:17:59.0261 (UTC) FILETIME=[6BA9F0D0:01C6543F] X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00903.txt.bz2 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: >=20 > CONFIG_KPROBES=3Dy > ... > CONFIG_DEBUG_INFO=3Dy >=20 > Whereas in 2054_FC5xen0 and 2054_xenU, the config files have: >=20 > # CONFIG_KPROBES is not set >=20 > ... 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=3Dy. I believe I've found the root-cause for the missing debuginfo - linux-2.6-xen.patch has this hunk: diff -Nru -p --exclude=3D'.*' ref-linux-2.6.16-rc5/lib/Kconfig.debug linux-2.6.16-rc5-xen0/lib/Kconfig.debug --- ref-linux-2.6.16-rc5/lib/Kconfig.debug 2006-03-01 11:12:31.000000000 -0500 +++ linux-2.6.16-rc5-xen0/lib/Kconfig.debug 2006-03-01 11:09:38.000000000 -0500 @@ -145,7 +145,7 @@ config DEBUG_BUGVERBOSE config DEBUG_INFO bool "Compile the kernel with debug info" - depends on DEBUG_KERNEL + depends on DEBUG_KERNEL && !X86_64_XEN help If you say Y here the resulting kernel image will include debugging info resulting in a larger kernel image. Also, the same patch has this chunk at the top of arch/x86_64/kernel/entry-xen.S: +#ifdef CONFIG_DEBUG_INFO +#undef CONFIG_DEBUG_INFO +#endif I'll leave open the question of *why* DEBUG_INFO is explicitly disabled... Josh