All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Selva <selva.manuel@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Intel PEBS Load Latency Measurement
Date: Fri, 01 Nov 2013 10:02:08 +0100	[thread overview]
Message-ID: <52736E10.9080104@gmail.com> (raw)
In-Reply-To: <87eh704iq9.fsf@sejong.aot.lge.com>

Thanks for this info. It confirms what I finally concluded after looking 
at source code where I saw that pid is used to get a task_struct object.

Manu

On 11/01/2013 09:41 AM, Namhyung Kim wrote:
> On Tue, 29 Oct 2013 14:20:09 +0100, Manuel Selva wrote:
>> One more thing I forgot to ask is clarification about the pid
>> parameter. According to Vince Weaver page: "If pid is 0, measurements
>> happen on the current thread, if pid is greater than 0, the process
>> indicated by pid is measured, and if pid is -1, all processes are
>> counted." and according to perf userland tool wiki page, it's possible
>> to attache to a specific thread with a -i option. As a consequence I
>> wonder how I can use the perf perf_event_sys_call to only count events
>> for a specific thread ?
>
> In the syscall's point of view, pid is actually tid AFAIK - so I works
> on the thread-basis not the process.
>
> Thanks,
> Namhyung
>

  reply	other threads:[~2013-11-01  9:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  7:44 Intel PEBS Load Latency Measurement Manuel Selva
2013-09-19  8:22 ` Andi Kleen
2013-10-28 11:28 ` Manuel Selva
2013-10-29  2:36   ` Namhyung Kim
     [not found]     ` <CALbiyZy_JE+wai7d_=r-XzE+FdHRitTiAuPmANtRt7Qpet8fTg@mail.gmail.com>
2013-10-29  9:12       ` Fwd: " Manuel Selva
2013-10-29 13:20         ` Manuel Selva
2013-11-01  8:41           ` Namhyung Kim
2013-11-01  9:02             ` Manuel Selva [this message]
2013-11-01 17:02             ` Vince Weaver
2013-11-01 18:08               ` Manuel Selva
2013-11-01  8:38         ` Fwd: " Namhyung Kim
2013-11-06 13:06           ` Manuel Selva
2013-11-06 13:41           ` Stephane Eranian

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=52736E10.9080104@gmail.com \
    --to=selva.manuel@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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.