[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] xenoprof missing xen symbols on x86_64 dom0


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Mukil Kesavan <mukilk7@xxxxxxxxx>
  • Date: Sun, 22 Feb 2009 22:44:55 -0500
  • Delivery-date: Sun, 22 Feb 2009 19:45:22 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=NxbOFQ/feSI35PfmaSx/yYtysNNHj5RZg6dMBDGhIo/cRBiJGvaqt5FzX73mQzb9Kz u/3EG+ch+AhDT/L/NWj9qvzKp2zmfahbvPTtM7LzHre6grf8vApD1pd4fOF1HrzQ8O4j XS0TnY2TOuUKwW2pkjnbCpjKLWAQdQNpKwZqs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

I followed the online guide to get xenoprof up and running
(http://www.xen.org/files/summit_3/xenoprof_tutorial.pdf). I compiled
the kernel with debugging symbols and patched up the user tools.

The problem I'm facing now is that "opreport -l" doesn't pick up
symbols from the xen-syms file specified while starting profiling. I
get a whole lot of "xen-unknown" symbols. This issue seems to be a
affecting only reports from dom0; strangely enough, I am able to get
symbols from xen on the domU report though. I'm running on an Intel
Xeon E5320 with Xen 3.3.2 pre-release (compiled from source). The
version of oprofile used is oprofile-0.9.3 and the xen patch applied
is  oprofile-0.9.3-xen-r2.patch.

I know that this question has been asked recently by someone else
working with xen3.3 but there was no response to it. So, reposting
another one here. Please do respond.

Thanks,
Mukil

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.