From: Marcus Granado <marcus.granado@citrix.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: [PATCH 0/3] xenoprof: improve handling of 32-bit guests on 64-bit xen
Date: Fri, 20 Jan 2012 18:44:38 +0000 [thread overview]
Message-ID: <4F19B616.8050603@citrix.com> (raw)
Hi,
this patch series for xen fixes some xenoprofile type glitches between
64-bit xen and 32-bit guests, enablingthe opcontrol callgraph option to
walk the call stack in both 32-bit and 64-bit guests when they are
running on 64-bit xen.
The escape-code patch (3/3) should be used with a corresponding patch in
the guest kernel definition of XENOPROF_ESCAPE_CODE so that both ends
agree on the same escape constant value.
A few comments from my tests with oprofile 0.9.6 in userspace:
- to obtain callgraphs of the xen code, you need to enable the
CONFIG_FRAME_POINTER flag during compilation of the xen binary, eg.
using "make" with "frame_pointer=y".
- if the oprofiled daemon is running in a 32-bit guest, it needs to
receive the xen-range in 32-bits, eg. --xen-image=/boot/xen-syms-4.1.1
--xen-range=80100000,801fe5ee
cheers,
Marcus
(1/3) xenoprof: Adjust indentation
(2/3) xenoprof: Handle 32-bit guest stacks properly in a 64-bit hypervisor
(3/3) xenoprof: Make the escape code consistent across 32 and 64-bit xen
reply other threads:[~2012-01-20 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F19B616.8050603@citrix.com \
--to=marcus.granado@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 NNTP newsgroup(s).