From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v2 0/3] Human readable platform-specific performance event support
Date: Thu, 28 Jan 2010 13:13:35 +0100 [thread overview]
Message-ID: <1264680815.4283.2100.camel@laptop> (raw)
In-Reply-To: <000101caa011$1ba9ee10$52fdca30$%fujak@samsung.com>
On Thu, 2010-01-28 at 12:57 +0100, Tomasz Fujak wrote:
please educate your MUA to wrap lines at ~80.
> Apparently I did not comprehend your attitude towards the events'
> description being exported from the kernel.
> There's been a lengthy discussion which ended in a conclusion that the
> platform detection is a complicated task.
If its really that complicated export a pmu identifier someplace.
The fact is, the kernel simply doesn't use this list, we have perf in
kernel so that resource scheduling and isolation can be done, for that
we need to know how to program the hardware and we need to know about
scheduling constraints, we do not need exhaustive lists of possible
events, let alone descriptive text for them, in the kernel.
next prev parent reply other threads:[~2010-01-28 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 9:34 [PATCH/RFC v2 0/3] Human readable platform-specific performance event support Tomasz Fujak
2010-01-28 9:34 ` [PATCH/RFC v2 1/3] perfevents: Added performance event structure definition, export event description in the debugfs "perf_events_platform" file Tomasz Fujak
2010-01-28 9:34 ` [PATCH/RFC v2 2/3] [ARM] perfevents: Event description for ARMv6, Cortex-A8 and Cortex-A9 exported Tomasz Fujak
2010-01-28 9:34 ` [PATCH/RFC v2 3/3] perf: Extended events (platform-specific) support in perf Tomasz Fujak
2010-01-28 10:52 ` [PATCH/RFC v2 0/3] Human readable platform-specific performance event support Peter Zijlstra
2010-01-28 11:57 ` Tomasz Fujak
2010-01-28 12:13 ` Peter Zijlstra [this message]
2010-01-28 12:40 ` 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=1264680815.4283.2100.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox