Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756236Ab3JHQ0B (ORCPT ); Tue, 8 Oct 2013 12:26:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49699 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754576Ab3JHQZ7 (ORCPT ); Tue, 8 Oct 2013 12:25:59 -0400 Date: Tue, 8 Oct 2013 12:24:51 -0400 From: Dave Jones To: David Ahern Cc: Ingo Molnar , Andi Kleen , x86@kernel.org, linux-kernel@vger.kernel.org, peterz@infradead.org, Andi Kleen , fweisbec@gmail.com Subject: Re: [PATCH 6/6] x86: Allow disabling HW_BREAKPOINTS and PERF_EVENTS Message-ID: <20131008162451.GA1848@redhat.com> Mail-Followup-To: Dave Jones , David Ahern , Ingo Molnar , Andi Kleen , x86@kernel.org, linux-kernel@vger.kernel.org, peterz@infradead.org, Andi Kleen , fweisbec@gmail.com References: <1380922788-23112-1-git-send-email-andi@firstfloor.org> <1380922788-23112-7-git-send-email-andi@firstfloor.org> <20131006164934.GA15167@gmail.com> <20131008065938.GA4333@gmail.com> <20131008155131.GA31975@redhat.com> <5254313F.4030409@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5254313F.4030409@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 25 On Tue, Oct 08, 2013 at 10:22:23AM -0600, David Ahern wrote: > On 10/8/13 9:51 AM, Dave Jones wrote: > > On Tue, Oct 08, 2013 at 08:59:38AM +0200, Ingo Molnar wrote: > > > > > You might want to concentrate your efforts from fighting perf > > > functionality towards decreasing per tracepoint overhead instead, > > > without hurting kernel functionality and maintainability. > > > > Making it easier to disable perf entirely would be desirable for one use case. > > I can't do a trinity run for more than a few hours for the last few months > > without hitting perf/ftrace bugs that no-one seems to be able to get their > > heads around. > > Looks like trinity has an exclude syscall option. Seems like that option > can be used to avoid perf_event_open (haven't tried though). You'd think that, but for whatever reason, ftrace/perf oopses still happen. Dave -- 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/