[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140803121259.GB1181@krava.brq.redhat.com>
Date: Sun, 3 Aug 2014 14:12:59 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Yann Droneaud <ydroneaud@...eya.com>
Cc: Jiri Olsa <jolsa@...nel.org>, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
Adrian Hunter <adrian.hunter@...el.com>,
David Ahern <dsahern@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Namhyung Kim <namhyung@...il.com>,
Stephane Eranian <eranian@...gle.com>,
William Cohen <wcohen@...hat.com>
Subject: Re: [PATCH] perf tools: report PERF_FLAG_FD_CLOEXEC probing error
once
On Sat, Aug 02, 2014 at 08:13:22PM +0200, Yann Droneaud wrote:
> In case of failure, unrelated to PERF_FLAG_FD_CLOEXEC,
> perf_flag_probe() reports the error twice. For example:
>
> $ perf record ls
> Error:
> perf_event_open(..., PERF_FLAG_FD_CLOEXEC) failed with unexpected error 16 (Device or resource busy)
> perf_event_open(..., 0) failed unexpectedly with error 16 (Device or resource busy)
seems ok,
but since your patch is not based on my other patch,
please provide the changelog perf out without it
---
> The PMU counters are busy/taken by another profiler.
> We found oprofile daemon running, please stop it and try again.
---
also, please provide both before and after outputs
I'll queue it up with those other 2 patches
thanks,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists