Hello Robert,

The answers are inline.

 # uname -a
Linux domU-12-31-39-07-7A-71 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:34:28 EST 2008 x86_64 GNU/Linux

 # zgrep -i oprofile /proc/config.gz
gzip: /proc/config.gz: No such file or directory

 # dmesg | grep -i oprofile
xenoprofile_init: ret 0, events 2, xenoprof_is_primary 0
 
# find /dev/oprofile/
/dev/oprofile/
/dev/oprofile/1
/dev/oprofile/1/user
/dev/oprofile/1/kernel
/dev/oprofile/1/unit_mask
/dev/oprofile/1/count
/dev/oprofile/1/event
/dev/oprofile/1/enabled
/dev/oprofile/0
/dev/oprofile/0/user
/dev/oprofile/0/kernel
/dev/oprofile/0/unit_mask
/dev/oprofile/0/count
/dev/oprofile/0/event
/dev/oprofile/0/enabled
/dev/oprofile/stats
/dev/oprofile/stats/bt_lost_no_mapping
/dev/oprofile/stats/event_lost_overflow
/dev/oprofile/stats/sample_lost_no_mapping
/dev/oprofile/stats/sample_lost_no_mm
/dev/oprofile/stats/cpu1
/dev/oprofile/stats/cpu1/backtrace_aborted
/dev/oprofile/stats/cpu1/sample_lost_overflow
/dev/oprofile/stats/cpu1/sample_received
/dev/oprofile/stats/cpu0
/dev/oprofile/stats/cpu0/backtrace_aborted
/dev/oprofile/stats/cpu0/sample_lost_overflow
/dev/oprofile/stats/cpu0/sample_received
/dev/oprofile/pointer_size
/dev/oprofile/backtrace_depth
/dev/oprofile/cpu_type
/dev/oprofile/cpu_buffer_size
/dev/oprofile/buffer_watershed
/dev/oprofile/buffer_size
/dev/oprofile/buffer
/dev/oprofile/passive_domains
/dev/oprofile/active_domains
/dev/oprofile/dump
/dev/oprofile/enable
 

# echo $(cat /dev/oprofile/cpu_type)
i386/piii

Thanks and Regards,
Nupur Garg



On Fri, Oct 16, 2009 at 4:17 AM, Robert Richter <robert.richter@amd.com> wrote:
On 15.10.09 23:21:36, nupur garg wrote:
> Hello,
> The oprofile device is mounted.

Nupur,

what gives the following on your system with oprofile mounted?

 # uname -a
 # zgrep -i oprofile /proc/config.gz
 # dmesg | grep -i oprofile
 # find /dev/oprofile/
 # echo $(cat /dev/oprofile/cpu_type)

> I had one xen image also, I tried on it and oprofile worked perfectly fine
> on it. The difference between the ec2 image and this image I found was that
> in /sys/devices/system/ directory oprofile directory was not there. Looking
> around more I found that while compiling the kernel, Oprofile has to be set.

This happens if CONFIG_PM is not set and is only needed for
suspend/resume.

-Robert

--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com