From: t.fujak@samsung.com (Tomasz Fujak)
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 11:21:51 +0100 [thread overview]
Message-ID: <023f01ca99ba$61ce7e90$256b7bb0$%fujak@samsung.com> (raw)
In-Reply-To: <20100120095757.GA20302@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-arm-
> kernel-bounces at lists.infradead.org] On Behalf Of Russell King - ARM
> Linux
> Sent: Wednesday, January 20, 2010 10:58 AM
> To: Tomasz Fujak
> Cc: jpihet at mvista.com; peterz at infradead.org; p.osciak at samsung.com;
> jamie.iles at picochip.com; will.deacon at arm.com; linux-
> kernel at vger.kernel.org; kyungmin.park at samsung.com; mingo at elte.hu;
> linux-arm-kernel at lists.infradead.org; m.szyprowski at samsung.com
> Subject: Re: [PATCH/RFC v1 0/2] Human readable performance event
> description in sysfs
>
> On Wed, Jan 20, 2010 at 10:11:44AM +0100, Tomasz Fujak wrote:
> > 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)
>
> I think your patch is in violation of this from
> Documentation/filesystems/sysfs.txt:
>
> Attributes
> ~~~~~~~~~
> ...
> Attributes should be ASCII text files, preferably with only one value
> per file. It is noted that it may not be efficient to contain only one
> value per file, so it is socially acceptable to express an array of
> values of the same type.
>
> Mixing types, expressing multiple lines of data, and doing fancy
> formatting of data is heavily frowned upon. Doing these things may get
> you publically humiliated and your code rewritten without notice.
1. There are numerous exceptions:
$ find /sys -exec grep -HC ^ {} \; 2>/dev/null | grep ":[3-9]$" | grep -c
yielded 43 on my machine.
Some of them list multiple lines with fancy formatting each (i.e.:
/sys/class/Bluetooth/l2cap or devices/pci*/resource)
2. There are sysfs entries regarding the performance counters already:
'overcommit' and 'reserve_percpu'
They are simple, I admit, but I find it useful to have all relevant thing in
one place.
If the above does not convince you, I could move the file to the debugfs.
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2010-01-20 10:21 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
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 [this message]
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='023f01ca99ba$61ce7e90$256b7bb0$%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