From: Lin Ming <ming.m.lin@intel.com>
To: Greg KH <greg@kroah.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
"eranian@gmail.com" <eranian@gmail.com>,
"Gary.Mohr@Bull.com" <Gary.Mohr@bull.com>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Will Deacon <will.deacon@arm.com>,
Maynard Johnson <mpjohn@us.ibm.com>, Carl Love <carll@us.ibm.com>,
Kay Sievers <kay.sievers@vrfy.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH v2 08/11] sysfs: introduce new interface sysfs_get_kobject
Date: Wed, 19 May 2010 13:42:00 +0800 [thread overview]
Message-ID: <1274247720.3603.91.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20100519033541.GA25967@kroah.com>
On Wed, 2010-05-19 at 11:35 +0800, Greg KH wrote:
> On Wed, May 19, 2010 at 10:55:17AM +0800, Lin Ming wrote:
> > On Wed, 2010-05-19 at 04:08 +0800, Greg KH wrote:
> > > On Wed, May 19, 2010 at 01:48:43AM +0000, Lin Ming wrote:
> > > > Need this interface in the later sysfs pmu lookup.
> > > >
> > > > struct kobject *sysfs_get_kobject(struct file *file);
> > > > Return the relative kobject of the sysfs file.
> > >
> > > Ick, no. Why would you ever have the file, yet not have the kobject
> > > already? Something is really wrong if this is needed. Or strange. Or
> > > maybe both :)
> >
> > Let me show you the scenario.
> >
> > /sys/devices/system/cpu/event_source/
> > `-- id
> >
> > /sys/devices/system/cpu/events/
> > |-- L1-dcache-load-misses
> > | |-- event_source -> ../../event_source
> >
> > $perf top -e L1-dcache-load-misses
> >
> > Lookup the pmu used to handle L1-dcache-load-misses as below,
> >
> > 1. pmu_sys_fd =
> > open("/sys/devices/system/cpu/events/L1-dcache-load-misses/event_source/id", ...)
>
> You do that within the kernel? or from userspace?
>From userspace.
See "[RFC][PATCH v2 11/11] perf top: demo of how to use the sysfs
interfac" for a simple example.
>
> Either way, your id show callback will get called when you read or write
> to that file, right? Then you have your kobject.
>
> > 2. pmu_sys_file = fget_light(pmu_sys_fd, ....)
> >
> > 3. pmu_kobject = sysfs_get_kobject(pmu_sys_file)
> >
> > 4. pmu_kobject is embedded in struct pmu, pmu = container_of(kobj,
> > struct pmu, kobj);
>
> Oh no.
>
> You are just using the kobject sysfs tree to store your kobjects so you
> can look them up again some time in the future from within the kernel?
Yes.
> Seriously?
>
> What's wrong with a simple list of kobjects? Or what the rest of the
> kernel does (busses and devices and iterating over the devices for a
> bus)?
A simple list of pmus is also added in this patch series
There are 2 pmu lookup methods in this patch series.
1. Search a simple list of pmus
2. Lookup pmu via sysfs
Method 1 is used for back compatibility.
>
> Don't act like userspace here and try to use the sysfs filesystem layout
> as a lookup into the kobject you are trying to find. That's a
> horrible abuse of sysfs. One of the worse I have ever seen. And I've
> seen a lot of sysfs abuse over the years...
Ah, it's that bad... I need to re-think how to export pmus/events to
userspace...
Lin Ming
>
> ick.
>
> greg k-h
prev parent reply other threads:[~2010-05-19 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 1:48 [RFC][PATCH v2 08/11] sysfs: introduce new interface sysfs_get_kobject Lin Ming
2010-05-18 20:08 ` Greg KH
2010-05-19 2:55 ` Lin Ming
2010-05-19 3:35 ` Greg KH
2010-05-19 5:42 ` Lin Ming [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=1274247720.3603.91.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=Gary.Mohr@bull.com \
--cc=acme@redhat.com \
--cc=arjan@linux.intel.com \
--cc=carll@us.ibm.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpjohn@us.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=will.deacon@arm.com \
--cc=yanmin_zhang@linux.intel.com \
/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.