From: Ray Lee <ray-lk@madrabbit.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jason Baron <jbaron@redhat.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org, paulus@samba.org,
a.p.zijlstra@chello.nl, fweisbec@gmail.com
Subject: Re: [PATCH 2/2] perf_counter: detect debugfs location
Date: Tue, 21 Jul 2009 10:01:40 -0700 [thread overview]
Message-ID: <2c0942db0907211001o5273a3ccybbba4de448150ddf@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907211242570.11743@gandalf.stny.rr.com>
On Tue, Jul 21, 2009 at 9:44 AM, Steven Rostedt<rostedt@goodmis.org> wrote:
>
> On Tue, 21 Jul 2009, Ray Lee wrote:
>
>> On Tue, Jul 21, 2009 at 9:20 AM, Jason Baron <jbaron@redhat.com> wrote:
>> >
>> > Search for the debugfs filesystem in /proc/mounts, but also allows the user to
>> > specify '--debugfs-dir=blah' or set the environment variable: 'PERF_DIR_DEBUGFS'
>>
>> > -static char default_debugfs_path[] = "/sys/kernel/debug/tracing/events";
>>
>> There are server systems out there that run with thousands of mounts.
>> It would be kinder to the users of those systems (ie, faster perf
>> startup) if you only went rooting around /proc/mounts if opening the
>> default location failed.
>
> Well, those that have thousand of mounts could probably get away with
> setting PERF_DIR_DEBUGFS in /etc/profile.
The intent of the patch is obviously to try to Do The Right Thing by
default. I think that's great. I just think it should DT(fast and)RT
instead.
> But, a simple stat("/sys/kernel/debug/tracing") should be easy enough.
<nod>
next prev parent reply other threads:[~2009-07-21 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 16:20 [PATCH 0/2] perf_counter: add tracepoint support Jason Baron
2009-07-21 16:20 ` [PATCH 1/2] perf_counter: add tracepoint support to perf list, perf stat Jason Baron
2009-07-21 16:20 ` [PATCH 2/2] perf_counter: detect debugfs location Jason Baron
2009-07-21 16:26 ` Ray Lee
2009-07-21 16:44 ` Steven Rostedt
2009-07-21 17:01 ` Ray Lee [this message]
2009-07-21 18:16 ` Jason Baron
2009-07-22 9:49 ` Peter Zijlstra
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=2c0942db0907211001o5273a3ccybbba4de448150ddf@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®