From: Rodrigo Campos <rodrigo@sdfg.com.ar>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@redhat.com, acme@ghostprotocols.net,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Clarify error when running "perf lock record"
Date: Thu, 5 Sep 2013 18:35:39 +0100 [thread overview]
Message-ID: <20130905173538.GB31659@sdfg.com.ar> (raw)
In-Reply-To: <52289536.3070504@gmail.com>
On Thu, Sep 05, 2013 at 08:29:10AM -0600, David Ahern wrote:
> On 9/5/13 2:32 AM, Rodrigo Campos wrote:
> >If you have the config options enabled in your kernel, you still need to be root
> >to run perf lock. And is kind of misleading when you have that options enabled
> >and the error says that they might not be.
> >
> >So, this patch just adds to the error that it should be run as root. Although we
> >can probably check if it's running as root or not, adding it to the error
> >message is really simple and should be enough.
> >
> >Signed-off-by: Rodrigo Campos <rodrigo@sdfg.com.ar>
> >---
> >Please keep me in Cc: since I'm not subscribed
> >---
> > tools/perf/builtin-lock.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> >diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> >index 76543a4..f07b318 100644
> >--- a/tools/perf/builtin-lock.c
> >+++ b/tools/perf/builtin-lock.c
> >@@ -886,8 +886,8 @@ static int __cmd_record(int argc, const char **argv)
> > for (i = 0; i < ARRAY_SIZE(lock_tracepoints); i++) {
> > if (!is_valid_tracepoint(lock_tracepoints[i].name)) {
> > pr_err("tracepoint %s is not enabled. "
> >- "Are CONFIG_LOCKDEP and CONFIG_LOCK_STAT enabled?\n",
> >- lock_tracepoints[i].name);
> >+ "Are CONFIG_LOCKDEP and CONFIG_LOCK_STAT enabled "
> >+ "and running as root?\n", lock_tracepoints[i].name);
> > return 1;
> > }
> > }
> >
>
> you can run perf-lock as non-root with certain settings. It would be
Ohh, I didn't know. Sorry.
> better to discriminate debugfs access errors (insufficient
> privilege). That means improving is_valid_tracepoint and handling
> the errors in perf-lock.
IMHO suggesting to check the privileges should be enough for most cases and is
simpler that checking all that. I mean, for me it's not worth the effort, but
maybe I'm too lazy. Probably it's quite simple too... :-)
Thanks,
Rodrigo
prev parent reply other threads:[~2013-09-05 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 8:32 Rodrigo Campos
2013-09-05 14:29 ` David Ahern
2013-09-05 17:35 ` Rodrigo Campos [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=20130905173538.GB31659@sdfg.com.ar \
--to=rodrigo@sdfg.com.ar \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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®