From: Muthusamy <muthu9283@yahoo.com>
To: Harald Servat <harald.servat@bsc.es>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: unable to get load latency info
Date: Tue, 4 Mar 2014 02:43:25 -0800 (PST) [thread overview]
Message-ID: <1393929805.25511.YahooMailNeo@web125403.mail.ne1.yahoo.com> (raw)
In-Reply-To: <531490AC.70605@bsc.es>
>>> On Monday, March 3, 2014 1:20 PM, Harald Servat
> <harald.servat@bsc.es> wrote:
> I notice that you provide on an earlier output a uname -a showed
> 2.6.32-xxxx but perf --version showed version 3.12.11, and they don't
> match but should. Are you running on 2.6.x or on 3.12.x?
After upgrading the kernel, it did work.
Thanks a lot for the support.
Regards,
Muthusamy C
> On Monday, March 3, 2014 7:54 PM, Harald Servat <harald.servat@bsc.es> wrote:
> > On 03/03/14 14:02, Muthusamy wrote:
>>> On Monday, March 3, 2014 1:20 PM, Harald Servat
> <harald.servat@bsc.es> wrote:
>>> so I imagine that you're ok with respect to OS.
>>> Besides of that, the Intel Manual [1] says in section 18.7.1.1
> that
>>> Nehalem (and I'd would guess Westmere, as it is a Nehalem
> successor)
>>> supports PEBS, so it should work.
>>
>>
>> So, what am I missing. Is there something the kernel needs to be enabled
> for PEBS. If yes, how do I know if it is enabled.
>>
>> Regards,
>> Muthusamy C
>>
>
> I notice that you provide on an earlier output a uname -a showed
> 2.6.32-xxxx but perf --version showed version 3.12.11, and they don't
> match but should. Are you running on 2.6.x or on 3.12.x?
>
>
> Regards
>
>
> WARNING / LEGAL TEXT: This message is intended only for the use of the
> individual or entity to which it is addressed and may contain
> information which is privileged, confidential, proprietary, or exempt
> from disclosure under applicable law. If you are not the intended
> recipient or the person responsible for delivering the message to the
> intended recipient, you are strictly prohibited from disclosing,
> distributing, copying, or in any way using this message. If you have
> received this communication in error, please notify the sender and
> destroy and delete any copies you may have received.
>
> http://www.bsc.es/disclaimer
>
prev parent reply other threads:[~2014-03-04 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 6:24 unable to get load latency info Muthusamy
2014-02-28 10:43 ` Harald Servat
2014-02-28 11:06 ` Manuel Selva
2014-02-28 13:42 ` Andi Kleen
2014-02-28 13:57 ` Harald Servat
2014-02-28 16:45 ` Andi Kleen
2014-03-03 5:12 ` Muthusamy
2014-03-03 7:50 ` Harald Servat
[not found] ` <1393851732.26401.YahooMailNeo@web125404.mail.ne1.yahoo.com>
2014-03-03 14:24 ` Harald Servat
2014-03-04 10:43 ` Muthusamy [this message]
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=1393929805.25511.YahooMailNeo@web125403.mail.ne1.yahoo.com \
--to=muthu9283@yahoo.com \
--cc=harald.servat@bsc.es \
--cc=linux-perf-users@vger.kernel.org \
/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.