From: m.nazarewicz@samsung.com (Michał Nazarewicz)
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 15:54:22 +0100 [thread overview]
Message-ID: <op.u6t6cwu17p4s8u@pikus> (raw)
In-Reply-To: <1263996979.4283.1066.camel@laptop>
>> On Wed, 20 Jan 2010 15:01:20 +0100, Peter Zijlstra <peterz@infradead.org> wrote:
>>> It seems to me userspace might care about the exact platform they're
>>> running on.
> On Wed, 2010-01-20 at 15:09 +0100, Micha? Nazarewicz wrote:
>> In my humble opinion, user space should never care about platform it's
>> running on. Interfaces provided by kernel should suffice to implement
>> abstraction layer between user space and hardware. If we abandon that
>> we're back in DOS times. But hey, again, that's just my opinion.
On Wed, 20 Jan 2010 15:16:19 +0100, Peter Zijlstra <peterz@infradead.org> wrote:
> Well, you're completely right. But the often sad reality is that perfect
> abstraction is either impossible or prohibitively expensive.
Yes, I agree and am aware of that, but I think it's not the case with
performance events. It is possible for kernel to provide such a list
and at the same time it's not that expensive (it's a matter of hardcoding
a list in the source and possibly alter it a bit according to hardware
detection which is done anyway).
Of course, it's not all gold -- maintaining such a list increases
complexity of the kernel and adds burden of keeping the lists in
sync with reality.
Still, however, in my opinion, the advantages of the list maintained
in kernel are greater then disadvantages and so I'd opt in for that
solution. (Of course, I'm not some kind of ARM Linux guru so I may
be simply wrong.)
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Micha? "mina86" Nazarewicz (o o)
ooo +---[mina86 at mina86.com]---[mina86 at jabber.org]---ooO--(_)--Ooo--
next prev parent reply other threads:[~2010-01-20 14:54 UTC|newest]
Thread overview: 23+ 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 ` [PATCH v1 1/2] perfevent: Add performance event structure definition and 'extevents' sysfs entry 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: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:57 ` Michał Nazarewicz
2010-01-20 13:31 ` Jamie Iles
2010-01-20 13:39 ` Peter Zijlstra
2010-01-20 13:55 ` Russell King - ARM Linux
2010-01-20 14:01 ` Peter Zijlstra
2010-01-20 14:09 ` Michał Nazarewicz
2010-01-20 14:16 ` Peter Zijlstra
2010-01-20 14:26 ` Peter Zijlstra
2010-01-20 14:45 ` Russell King - ARM Linux
2010-01-20 14:54 ` Michał Nazarewicz [this message]
2010-01-20 14:41 ` Russell King - ARM Linux
2010-01-20 15:03 ` Jamie Iles
2010-01-20 15:42 ` Russell King - ARM Linux
2010-01-20 16:18 ` Jamie Iles
2010-01-20 16:26 ` Jamie Lokier
2010-01-20 16:35 ` Russell King - ARM Linux
2010-01-20 9:57 ` Russell King - ARM Linux
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=op.u6t6cwu17p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--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