From: William Cohen <wcohen@redhat.com>
To: "Santos, Jose Renato G" <joserenato.santos@hp.com>
Cc: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>,
xen-devel@lists.xensource.com
Subject: Re: Revisiting the Xenoprof problem
Date: Tue, 20 Nov 2007 15:49:22 -0500 [thread overview]
Message-ID: <47434852.20309@redhat.com> (raw)
In-Reply-To: <7CE4D90FFCFD444AA05E2D0FF89A390D5538F8@orsmsx412.amr.corp.intel.com>
Venkataraman, Meenakshi wrote:
>> What versions of Xen and oprofile are you running?
> I'm running xen 3.1.0 and oprofile 0.9.3 (patched for xen).
>
>> Any oprofile related message in the kernel log or in the output of "xm
>> dmesg"
> No...none. Although the cpu type is correctly recognized as a xeon in xm
> dmesg.
>
>> What is on /dev/oprofile/cpu_type after you run opcontrol?
> "i386/piii"
>
>> Also take a look at /var/lib/oprofile/samples/oprofiled.log for any
> error message
> There are a lot of CPU_SWITCH messages in during some runs in the
> oprofiled.log. I saw another post with the same problem on an embedded
> processor, but couldn't find any follow up to it.
>
> Meenakshi
Is xen 3.1.0 okay to run with oprofile 0.9.3. There were some conflicts in the
defines between xenoprof and the defines added for the cell processor in
oprofile 0.9.3.
https://bugzilla.redhat.com/show_bug.cgi?id=250852
-Will
next prev parent reply other threads:[~2007-11-20 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 17:32 Revisiting the Xenoprof problem Venkataraman, Meenakshi
2007-11-15 7:32 ` Santos, Jose Renato G
2007-11-15 7:46 ` Venkataraman, Meenakshi
2007-11-15 8:16 ` Santos, Jose Renato G
2007-11-15 9:31 ` Venkataraman, Meenakshi
2007-11-15 22:38 ` Santos, Jose Renato G
2007-11-20 20:49 ` William Cohen [this message]
2007-11-21 1:27 ` Santos, Jose Renato G
2007-11-28 18:30 ` William Cohen
2007-11-28 21:44 ` Santos, Jose Renato G
2007-11-28 22:14 ` Keir Fraser
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=47434852.20309@redhat.com \
--to=wcohen@redhat.com \
--cc=joserenato.santos@hp.com \
--cc=meenakshi.venkataraman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.