All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Freehill Christopher-RAT063 <RAT063@freescale.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: perf event attrributes
Date: Tue, 02 Apr 2013 13:42:33 +0900	[thread overview]
Message-ID: <87ehetfsqu.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <0C53B16FB1F182409A7BA6DC928E7AFE20C90D@039-SN2MPN1-022.039d.mgd.msft.net> (Freehill Christopher-RAT's message of "Mon, 1 Apr 2013 16:09:50 +0000")

Hi Chris,

On Mon, 1 Apr 2013 16:09:50 +0000, Freehill Christopher-RAT wrote:
> Andi,
>
> Thanks for the response.
>
> I am not familiar with "config/config1", but I infer from your message that I would make folders in sysfs for different event groups (?) and then have a file for each event that is a bit field that can be parsed. 
>
> As an alternative, is there anything to prevent encoding the attributes in the event ID itself? I think there are 64 bits to use. Some of those could be interpreted in a way specific to the event. I can see advantages and disadvantage to both. 
>
> Both ways seem a little convoluted from a user point of view. Seems
> like a more intuitive way would have been from the command line; ie,
> provide a way to pass info from the command line that could be
> interpreted in a way specific to the event. I'm sure that was probably
> considered, and there is a good reason that method wasn't chosen, but
> I do wonder...
>
> Can you point me to the Intel uncore drivers you mentioned?

You can see it under /sys/bus/event_source/devices/uncore_imc_*/ on a
recent kernel.  There'll be the "format" and "events" directories.

If you want to see the source, please go to:

  http://lxr.linux.no/#linux+v3.8.5/arch/x86/kernel/cpu/perf_event_intel_uncore.c


Thanks,
Namhyung

  reply	other threads:[~2013-04-02  4:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 15:40 perf event attrributes Freehill Christopher-RAT063
2013-03-28  1:32 ` Andi Kleen
2013-04-01 16:09   ` Freehill Christopher-RAT063
2013-04-02  4:42     ` Namhyung Kim [this message]
2013-04-03 22:26       ` Freehill Christopher-RAT063

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=87ehetfsqu.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=RAT063@freescale.com \
    --cc=andi@firstfloor.org \
    --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.