public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu, paulus@samba.org
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 3/3] perf tools: Make test use the preset debugfs path
Date: Thu, 14 Jul 2011 11:25:34 +0200	[thread overview]
Message-ID: <1310635534-4013-4-git-send-email-jolsa@redhat.com> (raw)
In-Reply-To: <1310635534-4013-1-git-send-email-jolsa@redhat.com>

Use preset debugfs path instead of hardcoded one.

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
---
 tools/perf/builtin-test.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/perf/builtin-test.c b/tools/perf/builtin-test.c
index b5cd5f5..55f4c76 100644
--- a/tools/perf/builtin-test.c
+++ b/tools/perf/builtin-test.c
@@ -246,8 +246,8 @@ static int trace_event__id(const char *evname)
 	int err = -1, fd;
 
 	if (asprintf(&filename,
-		     "/sys/kernel/debug/tracing/events/syscalls/%s/id",
-		     evname) < 0)
+		     "%s/syscalls/%s/id",
+		     debugfs_path, evname) < 0)
 		return -1;
 
 	fd = open(filename, O_RDONLY);
-- 
1.7.4


  parent reply	other threads:[~2011-07-14  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14  9:25 [PATCH 0/3] perf tools: Add automated tests for events parsing Jiri Olsa
2011-07-14  9:25 ` [PATCH 1/3] perf tools: De-opt the parse_events function Jiri Olsa
2011-07-21 10:12   ` [tip:perf/core] " tip-bot for Jiri Olsa
2011-07-14  9:25 ` [PATCH 2/3] perf tools: Add automated tests for events parsing Jiri Olsa
2011-07-21 10:13   ` [tip:perf/core] " tip-bot for Jiri Olsa
2011-07-14  9:25 ` Jiri Olsa [this message]
2011-07-21 10:13   ` [tip:perf/core] perf tools: Make test use the preset debugfs path tip-bot for Jiri Olsa

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=1310635534-4013-4-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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