From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752708AbaLDCsX (ORCPT ); Wed, 3 Dec 2014 21:48:23 -0500 Received: from mail-qg0-f47.google.com ([209.85.192.47]:57358 "EHLO mail-qg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751911AbaLDCsW (ORCPT ); Wed, 3 Dec 2014 21:48:22 -0500 Message-ID: <547FCB73.1010707@linaro.org> Date: Wed, 03 Dec 2014 21:48:19 -0500 From: David Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: William Cohen , Masami Hiramatsu , Steve Capper CC: "Jon Medhurst (Tixy)" , Russell King , Ananth N Mavinakayanahalli , Sandeepa Prabhu , Catalin Marinas , Will Deacon , "linux-kernel@vger.kernel.org" , Anil S Keshavamurthy , David Miller , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support References: <1416292375-29560-1-git-send-email-dave.long@linaro.org> <20141120135851.GA32528@linaro.org> <54759041.9080105@hitachi.com> <20141126100325.GA9157@linaro.org> <5476120D.9030703@linaro.org> <5476BFB4.2020705@hitachi.com> <547C36DB.7060903@hitachi.com> <547F242D.1060705@redhat.com> <547F94B0.1000902@linaro.org> <547FB5DD.901@redhat.com> In-Reply-To: <547FB5DD.901@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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