From: Xin Zhao <zhaoxin@eecs.umich.edu>
To: Xen devel list <xen-devel@lists.xensource.com>
Subject: xenoprof problem
Date: Tue, 23 May 2006 01:49:59 -0400 [thread overview]
Message-ID: <4472A287.4090806@eecs.umich.edu> (raw)
I am using xen-unstable with kernel 2.6.16. I enabled the auditd when
compiling kernel. After compile and restart, I did "opcontrol --start"
in DomU. But I got the error message as following:
------------------------------
Using default event: GLOBAL_POWER_EVENTS:100000:1:1:1
Using 2.6+ OProfile kernel interface.
Failed to open profile device: Operation not permitted
Couldn't start oprofiled.
Check the log file "/var/lib/oprofile/oprofiled.log" and kernel syslog
-------------------------------------------------
Does anyone have similar experience? Is this the right way to profiling
the performance in xen systems?
Thanks in advance for your help!
Xin
next reply other threads:[~2006-05-23 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 5:49 Xin Zhao [this message]
2006-05-23 16:24 ` xenoprof problem Santos, Jose Renato G
[not found] <d47704fc1002111337u6e7cd33ne22ed14affc1cb7b@mail.gmail.com>
2010-02-11 23:39 ` XENOPROF Problem Andrew Evans
2010-02-11 23:52 ` Ahmad Hassan
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=4472A287.4090806@eecs.umich.edu \
--to=zhaoxin@eecs.umich.edu \
--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).