[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <547FCB73.1010707@linaro.org>
Date: Wed, 03 Dec 2014 21:48:19 -0500
From: David Long <dave.long@...aro.org>
To: William Cohen <wcohen@...hat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Steve Capper <steve.capper@...aro.org>
CC: "Jon Medhurst (Tixy)" <tixy@...aro.org>,
Russell King <linux@....linux.org.uk>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Sandeepa Prabhu <sandeepa.prabhu@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
David Miller <davem@...emloft.net>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support
On 12/03/14 20:16, William Cohen wrote:
[...]
>
> The perf issue seems to be independent and can be reproduced without using any kprobe support. I need to get a simple reproducer and mention it on the linux-perf-user list.
>
> -Will
>
OK, my confusion came from all the different things perf can use. I
have not yet been able to reproduce the "perf stat" failure, but I do
see the failure with Steve's example using tracepoints. I had thought
that was using kprobes, but apparently it just uses tracepoints. These
look like two different failures to me: One related to tracepoints, and
one in the PMU driver.
Since this seems unrelated to kprobes I don't plan on pursuing these
particular problems.
-dl
--
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