From: t.fujak@samsung.com (Tomasz Fujak)
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 12:57:47 +0100 [thread overview]
Message-ID: <000101caa011$1ba9ee10$52fdca30$%fujak@samsung.com> (raw)
In-Reply-To: <1264675934.4283.2088.camel@laptop>
> -----Original Message-----
> From: Peter Zijlstra [mailto:peterz at infradead.org]
> Sent: Thursday, January 28, 2010 11:52 AM
> To: Tomasz Fujak
> Cc: linux-arm-kernel at lists.infradead.org; linux-kernel at vger.kernel.org;
> acme at redhat.com; jamie.iles at picochip.com; will.deacon at arm.com;
> jpihet at mvista.com; mingo at elte.hu; p.osciak at samsung.com;
> m.szyprowski at samsung.com; kyungmin.park at samsung.com;
> m.nazarewicz at samsung.com
> Subject: Re: [PATCH/RFC v2 0/3] Human readable platform-specific
> performance event support
>
> On Thu, 2010-01-28 at 10:34 +0100, Tomasz Fujak wrote:
> > Human readable description support for performance events v2. With
> perf support included.
> > Changes from v1:
> > - applied on top of latest perf_event/ARM (5899/1 - 5903/1)
> > - moved to debugfs, now based on seq_file
> > - reads one line at a time, memory overallocation fixed [perf]
>
> You can keep sending these patches, but I'll keep ignoring them
> eventually adding you to the /dev/null redirect.
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.
The solution finally accepted covers just a subset of platforms. I guess the detection scheme may be updated and possibly changed as new cores/implementers come into sight.
That I think provides additional reasoning to keep the event list where it's defined (in the kernel).
The rest of the suggestions (perf implementation, debugfs instead of sysfs) I've included into the posted patches.
Therefore I cannot really understand why you're threatening to ignore my further efforts; especially since the arguments me and my teammate Michal brought I find reasonable.
So finally, if the proposed patches are too intrusive, can you imagine other mechanism in the kernel that would let the userspace unambiguously retrieve a list of supported events?
Maybe an entry in the sysfs that indicates supported event list version (relevant to the implementer, cupid and other black magic that is involved into the platform detection)?
Right now what can be done is to try follow the kernel implementation of the detection scheme in the applications, which I can't say I'm a fan of.
next prev parent reply other threads:[~2010-01-28 11:57 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 [this message]
2010-01-28 12:13 ` Peter Zijlstra
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='000101caa011$1ba9ee10$52fdca30$%fujak@samsung.com' \
--to=t.fujak@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