From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v1 0/2] Human readable performance event description in sysfs
Date: Wed, 20 Jan 2010 10:16:39 +0100 [thread overview]
Message-ID: <1263978999.4283.823.camel@laptop> (raw)
In-Reply-To: <1263978706-15499-1-git-send-email-t.fujak@samsung.com>
On Wed, 2010-01-20 at 10:11 +0100, Tomasz Fujak wrote:
> Hi,
>
> While I managed to build and run the early version (back from
> December), I was unable to find the newest sources (infra + ARMv6,
> ARMv7 support).
> Where do I find them?
>
> The following patches provide a sysfs entry with hardware event human
> readable description in the form of "0x%llx\t%lld-%lld\t%s\t%s" %
> (event_value, minval, maxval, name, description) and means to populate
> the file.
> The version posted contains ARMv6, ARMv7 (Cortex-A[89]) support in
> this matter.
>
> The intended use is twofold: for users to read the list directly and
> for tools (like perf).
>
> This series includes:
> [PATCH v1 1/2] perfevent: Add performance event structure definition
> and 'extevents' sysfs entry
> [PATCH v1 2/2] [ARM] perfevent: Event description list for ARMv6,
> Cortex-A8 and Cortex-A9 exported
Why do this in kernel space? Listing available events seems like
something we can do from userspace just fine.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Tomasz Fujak <t.fujak@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jamie.iles@picochip.com,
will.deacon@arm.com, jpihet@mvista.com, mingo@elte.hu,
p.osciak@samsung.com, m.szyprowski@samsung.com,
kyungmin.park@samsung.com
Subject: Re: [PATCH/RFC v1 0/2] Human readable performance event description in sysfs
Date: Wed, 20 Jan 2010 10:16:39 +0100 [thread overview]
Message-ID: <1263978999.4283.823.camel@laptop> (raw)
In-Reply-To: <1263978706-15499-1-git-send-email-t.fujak@samsung.com>
On Wed, 2010-01-20 at 10:11 +0100, Tomasz Fujak wrote:
> Hi,
>
> While I managed to build and run the early version (back from
> December), I was unable to find the newest sources (infra + ARMv6,
> ARMv7 support).
> Where do I find them?
>
> The following patches provide a sysfs entry with hardware event human
> readable description in the form of "0x%llx\t%lld-%lld\t%s\t%s" %
> (event_value, minval, maxval, name, description) and means to populate
> the file.
> The version posted contains ARMv6, ARMv7 (Cortex-A[89]) support in
> this matter.
>
> The intended use is twofold: for users to read the list directly and
> for tools (like perf).
>
> This series includes:
> [PATCH v1 1/2] perfevent: Add performance event structure definition
> and 'extevents' sysfs entry
> [PATCH v1 2/2] [ARM] perfevent: Event description list for ARMv6,
> Cortex-A8 and Cortex-A9 exported
Why do this in kernel space? Listing available events seems like
something we can do from userspace just fine.
next prev parent reply other threads:[~2010-01-20 9:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 9:11 [PATCH/RFC v1 0/2] Human readable performance event description in sysfs Tomasz Fujak
2010-01-20 9:11 ` Tomasz Fujak
2010-01-20 9:11 ` [PATCH v1 1/2] perfevent: Add performance event structure definition and 'extevents' sysfs entry Tomasz Fujak
2010-01-20 9:11 ` Tomasz Fujak
2010-01-20 9:11 ` [PATCH v1 2/2] [ARM] perfevent: Event description list for ARMv6, Cortex-A8 and Cortex-A9 exported Tomasz Fujak
2010-01-20 9:11 ` Tomasz Fujak
2010-01-20 9:16 ` Peter Zijlstra [this message]
2010-01-20 9:16 ` [PATCH/RFC v1 0/2] Human readable performance event description in sysfs Peter Zijlstra
2010-01-20 9:46 ` Tomasz Fujak
2010-01-20 9:46 ` Tomasz Fujak
2010-01-20 9:57 ` Michał Nazarewicz
2010-01-20 9:57 ` Michał Nazarewicz
2010-01-20 13:31 ` Jamie Iles
2010-01-20 13:31 ` Jamie Iles
2010-01-20 13:39 ` Peter Zijlstra
2010-01-20 13:39 ` Peter Zijlstra
2010-01-20 13:55 ` Russell King - ARM Linux
2010-01-20 13:55 ` Russell King - ARM Linux
2010-01-20 14:01 ` Peter Zijlstra
2010-01-20 14:01 ` Peter Zijlstra
2010-01-20 14:09 ` Michał Nazarewicz
2010-01-20 14:09 ` Michał Nazarewicz
2010-01-20 14:16 ` Peter Zijlstra
2010-01-20 14:16 ` Peter Zijlstra
2010-01-20 14:26 ` Peter Zijlstra
2010-01-20 14:26 ` Peter Zijlstra
2010-01-20 14:45 ` Russell King - ARM Linux
2010-01-20 14:45 ` Russell King - ARM Linux
2010-01-20 14:54 ` Michał Nazarewicz
2010-01-20 14:54 ` Michał Nazarewicz
2010-01-20 14:41 ` Russell King - ARM Linux
2010-01-20 14:41 ` Russell King - ARM Linux
2010-01-20 15:03 ` Jamie Iles
2010-01-20 15:03 ` Jamie Iles
2010-01-20 15:42 ` Russell King - ARM Linux
2010-01-20 15:42 ` Russell King - ARM Linux
2010-01-20 16:18 ` Jamie Iles
2010-01-20 16:18 ` Jamie Iles
2010-01-20 16:26 ` Jamie Lokier
2010-01-20 16:26 ` Jamie Lokier
2010-01-20 16:35 ` Russell King - ARM Linux
2010-01-20 16:35 ` Russell King - ARM Linux
2010-01-20 9:57 ` Russell King - ARM Linux
2010-01-20 9:57 ` Russell King - ARM Linux
2010-01-20 10:21 ` Tomasz Fujak
2010-01-20 10:21 ` Tomasz Fujak
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=1263978999.4283.823.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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.