Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965064Ab3HHNd5 (ORCPT ); Thu, 8 Aug 2013 09:33:57 -0400 Received: from mail-vc0-f177.google.com ([209.85.220.177]:47488 "EHLO mail-vc0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757835Ab3HHNdz (ORCPT ); Thu, 8 Aug 2013 09:33:55 -0400 Date: Thu, 8 Aug 2013 09:40:08 -0400 (EDT) From: Vince Weaver To: Will Deacon cc: Vince Weaver , Stephen Boyd , "linux-kernel@vger.kernel.org" , Mark Rutland , Peter Zijlstra , Ingo Molnar , Paul Mackerras , Arnaldo Carvalho de Melo , "trinity@vger.kernel.org" Subject: Re: perf,arm -- another (different) fuzzer oops In-Reply-To: <20130808121337.GC18724@mudshark.cambridge.arm.com> Message-ID: References: <20130807223129.GA17118@mudshark.cambridge.arm.com> <5202D5B0.9020107@codeaurora.org> <20130808121337.GC18724@mudshark.cambridge.arm.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1599 Lines: 41 On Thu, 8 Aug 2013, Will Deacon wrote: > On the flip side, the good news is that we know the problem is there. We're > probably generating interrupts at some horrendous rate for the lock-up.... > are you running your fuzzer as root? No, I'm running the fuzzer as a regular user. > Also, is your fuzzer available somewhere? I could take it for a spin on some > different architectures if you like. Yes: git clone https://github.com/deater/perf_event_tests.git and it's in the "fuzzer" subdirectory. I think I've committed all of the ARM related patches. To run the tool it's just "./perf_fuzzer" and away you go. There's a lot of other tools for generating and analyzing fuzzer syscall traces but unfortunately they're not very user-friendly yet. As for other architectures (at least ARM) in addition to the pandaboard I also have a beagleboard and a cortex-A15 chromebook. The challenge is always getting recent Linus-git kernels running on the things. I also have a raspberry-pi. I've successfully accessed the perf counters on that by reading the low-level registers directly with a kernel modulue. There's no perf driver because the PMU interrupt isn't hooked up. I've been meaning to get perf support going by making things periodically polled rather than interrupt driven: has anybody looked into doing that yet? Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/