All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Feng Tang <feng.tang@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	David Ahern <dsahern@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Robert Richter <robert.richter@amd.com>,
	Andi Kleen <andi@firstfloor.org>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v5 4/5] perf script: Add a python library EventClass.py
Date: Thu, 09 Aug 2012 10:10:14 +0900	[thread overview]
Message-ID: <87mx24yio9.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1344419875-21665-5-git-send-email-feng.tang@intel.com> (Feng Tang's message of "Wed, 8 Aug 2012 17:57:54 +0800")

On Wed,  8 Aug 2012 17:57:54 +0800, Feng Tang wrote:
> This library defines several class types for perf events which could
> help to better analyze the event samples. Currently there are just a
> few classes, PerfEvent is the base class for all perf events,  PebsEvent
> is a HW base Intel x86 PEBS event, and user could add more SW/HW event
> classes based on requriements.
>
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> ---
>  .../Perf-Trace-Util/lib/Perf/Trace/EventClass.py   |   95 ++++++++++++++++++++
>  1 files changed, 95 insertions(+), 0 deletions(-)
>  create mode 100755 tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py
>
> diff --git a/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py b/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py
> new file mode 100755
> index 0000000..12cd773
> --- /dev/null
> +++ b/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py
> @@ -0,0 +1,95 @@
> +# EventClass.py
> +#
> +# This is a libray defining some events typs classes, which could

s/typs/type/


> +# be used by other scripts to analyzing the perf samples.
> +#
> +# Currently there are just a few classes defined for examples,
> +# PerfEvent is the base class for all perf event sample, PebsEvent
> +# is a HW base Intel x86 PEBS event, and user could add more SW/HW
> +# event classes based on requriements.

s/requriements/requirements/

Thanks,
Namhyung


> +
> +import struct
> +
> +# Event types, user could add more here
> +EVTYPE_GENERIC  = 0
> +EVTYPE_PEBS     = 1     # Basic PEBS event
> +EVTYPE_PEBS_LL  = 2     # PEBS event with load latency info
> +EVTYPE_IBS      = 3
> +
> +#
> +# Currently we don't have good way to tell the event type, but by
> +# the size of raw buffer, raw PEBS event with load latency data's
> +# size is 176 bytes, while the pure PEBS event's size is 144 bytes.
> +#
> +def create_event(name, comm, dso, symbol, raw_buf):
> +        if (len(raw_buf) == 144):
> +                event = PebsEvent(name, comm, dso, symbol, raw_buf)
> +        elif (len(raw_buf) == 176):
> +                event = PebsNHM(name, comm, dso, symbol, raw_buf)
> +        else:
> +                event = PerfEvent(name, comm, dso, symbol, raw_buf)
> +
> +        return event
> +
> +class PerfEvent(object):
> +        event_num = 0
> +        def __init__(self, name, comm, dso, symbol, raw_buf, ev_type=EVTYPE_GENERIC):
> +                self.name       = name
> +                self.comm       = comm
> +                self.dso        = dso
> +                self.symbol     = symbol
> +                self.raw_buf    = raw_buf
> +                self.ev_type    = ev_type
> +                PerfEvent.event_num += 1
> +
> +        def show(self):
> +                print "PMU event: name=%12s, symbol=%24s, comm=%8s, dso=%12s" % (self.name, self.symbol, self.comm, self.dso)
> +
> +#
> +# Basic Intel PEBS (Precise Event-based Sampling) event, whose raw buffer
> +# contains the context info when that event happened: the EFLAGS and
> +# linear IP info, as well as all the registers.
> +#
> +class PebsEvent(PerfEvent):
> +        pebs_num = 0
> +        def __init__(self, name, comm, dso, symbol, raw_buf, ev_type=EVTYPE_PEBS):
> +                tmp_buf=raw_buf[0:80]
> +                flags, ip, ax, bx, cx, dx, si, di, bp, sp = struct.unpack('QQQQQQQQQQ', tmp_buf)
> +                self.flags = flags
> +                self.ip    = ip
> +                self.ax    = ax
> +                self.bx    = bx
> +                self.cx    = cx
> +                self.dx    = dx
> +                self.si    = si
> +                self.di    = di
> +                self.bp    = bp
> +                self.sp    = sp
> +
> +                PerfEvent.__init__(self, name, comm, dso, symbol, raw_buf, ev_type)
> +                PebsEvent.pebs_num += 1
> +                del tmp_buf
> +
> +#
> +# Intel Nehalem and Westmere support PEBS plus Load Latency info which lie
> +# in the four 64 bit words write after the PEBS data:
> +#       Status: records the IA32_PERF_GLOBAL_STATUS register value
> +#       DLA:    Data Linear Address (EIP)
> +#       DSE:    Data Source Encoding, where the latency happens, hit or miss
> +#               in L1/L2/L3 or IO operations
> +#       LAT:    the actual latency in cycles
> +#
> +class PebsNHM(PebsEvent):
> +        pebs_nhm_num = 0
> +        def __init__(self, name, comm, dso, symbol, raw_buf, ev_type=EVTYPE_PEBS_LL):
> +                tmp_buf=raw_buf[144:176]
> +                status, dla, dse, lat = struct.unpack('QQQQ', tmp_buf)
> +                self.status = status
> +                self.dla = dla
> +                self.dse = dse
> +                self.lat = lat
> +
> +                PebsEvent.__init__(self, name, comm, dso, symbol, raw_buf, ev_type)
> +                PebsNHM.pebs_nhm_num += 1
> +                del tmp_buf
> +

  reply	other threads:[~2012-08-09  1:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  9:57 [PATCH v5 0/5] perf script: Add general event support to event handler of python script Feng Tang
2012-08-08  9:57 ` [PATCH v5 1/5] perf script: Add general python handler to process non-tracepoint events Feng Tang
2012-08-09  0:54   ` Namhyung Kim
2012-08-21 15:30   ` [tip:perf/core] " tip-bot for Feng Tang
2012-08-08  9:57 ` [PATCH v5 2/5] perf script: Replace "struct thread" with "struct addr_location" as a parameter for "process_event()" Feng Tang
2012-08-21 15:31   ` [tip:perf/core] perf script: Replace "struct thread" with " struct " tip-bot for Feng Tang
2012-08-08  9:57 ` [PATCH v5 3/5] perf script/python: Pass event/thread/dso name and symbol info to event handler in python Feng Tang
2012-08-09  1:06   ` Namhyung Kim
2012-08-21 15:32   ` [tip:perf/core] perf scripts python: Pass event/thread/ dso " tip-bot for Feng Tang
2012-08-08  9:57 ` [PATCH v5 4/5] perf script: Add a python library EventClass.py Feng Tang
2012-08-09  1:10   ` Namhyung Kim [this message]
2012-08-21 15:35   ` [tip:perf/core] perf scripts python: " tip-bot for Feng Tang
2012-08-08  9:57 ` [PATCH v5 5/5] perf script: Add event_analyzing_sample.py as a sample for general event handling Feng Tang
2012-08-09  1:30   ` Namhyung Kim
2012-08-09  4:30     ` Feng Tang
2012-08-09  5:19       ` Namhyung Kim
2012-08-09  5:28         ` Feng Tang
2012-08-09  5:46           ` Namhyung Kim
2012-08-21 15:36   ` [tip:perf/core] perf scripts python: Add event_analyzing_sample. py " tip-bot for Feng Tang

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=87mx24yio9.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.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.