linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Shahina Rabbani <shahinarabbani.shaik@gmail.com>
Cc: Chulmin Kim <cmkim@core.kaist.ac.kr>, linux-perf-users@vger.kernel.org
Subject: Re: Queries on using PERF tool
Date: Thu, 29 Nov 2012 23:47:06 +0900	[thread overview]
Message-ID: <1354200426.1630.30.camel@leonhard> (raw)
In-Reply-To: <CA+wByoXeohgy4bhi3WN3was0-7RboXzWcTU1Kv0DrZ=b7ewR4Q@mail.gmail.com>

Hi Shahina,

2012-11-29 (목), 13:45 +0530, Shahina Rabbani:
> Hi Namhyung Kim ,
> 
> 
> First of all Thanks for your mail.
> I have some more doubts. Please help me.
> 
> 
> Q1: when we are working with more than one CPU, there will be a shared
> L2 cache for all the CPUs and each CPU will have its own L1-cache
>        If i want to monitor a event and i am using L1-cahce and
> L2-caches from CPU1 and the same time if CPU2 is also trying to
> monotora particular event and using L2-  
>        cache. Then how the perf tool handles this situation.

On a recent kernel and Intel cpus, it supports offcore and/or uncore
events for that purpose AFAIK.  Please check your cpu manuals.

> 
> 
> Q2.  Can you please list what are the architechtures it is supporting
> at present.
> 
> 
> Q3.  Consider the case of Distributed systems, where the processors
> are connected through the network and say i am trying to transmit data
> over the TCP/IP stack. Is it 
>         possible to monitor the data send at our end and data received
> from the other end using the perf tool??

The perf tools work with pipe so that we might use nc/netcat for this.
Only tested on a local machine:

<on terminal 1>
$ nc -l localhost 8282 | perf report -i -

<on terminal 2>
$ perf record -o - sleep 1 | nc localhost 8282


> 
> 
> Q4. when using perf record. Say i have got the data in perf.data file.
> Say i am using this file to get some information and assume that
> system crashes and the perf.data file is 
>       in inconsistent state. when u reboot the system after the crash,
> is it posssible to get the perf.data file safely.???

I doubt you can use the file safely.  There's no guarantee when system
crashed.

Thanks,
Namhyung

> 
> 
> Q5. Say i am counting some samples depending on the clock. and assume
> that i change the clock in between., Then the perf tool will be able
> to understand the situation and count the samples depending on the old
> and ne changed clocks or do we need to provide this information to
> perf tool.?? how to handle this situation??

  parent reply	other threads:[~2012-11-29 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  5:47 Queries on using PERF tool Shahina Rabbani
2012-11-28  6:02 ` Chulmin Kim
2012-11-29  6:59   ` Namhyung Kim
     [not found]     ` <CA+wByoXeohgy4bhi3WN3was0-7RboXzWcTU1Kv0DrZ=b7ewR4Q@mail.gmail.com>
2012-11-29 14:47       ` Namhyung Kim [this message]
     [not found] ` <CAD15agZ1Q5RZ=LLnJ5d1t7WURL+C=S_KZ+Hn_NxukyYKaX12Vw@mail.gmail.com>
     [not found]   ` <CA+wByoUyv8LGA_rZXV=xgLXQWG=s3jAXq9m_38tE9DjY94DC0w@mail.gmail.com>
2012-11-28  7:16     ` Chulmin Kim

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=1354200426.1630.30.camel@leonhard \
    --to=namhyung@kernel.org \
    --cc=cmkim@core.kaist.ac.kr \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=shahinarabbani.shaik@gmail.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).