From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755341AbcA1N5p (ORCPT ); Thu, 28 Jan 2016 08:57:45 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:48412 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754785AbcA1N5n (ORCPT ); Thu, 28 Jan 2016 08:57:43 -0500 Date: Thu, 28 Jan 2016 14:57:33 +0100 From: Peter Zijlstra To: Mathieu Desnoyers Cc: rostedt , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, "Paul E. McKenney" Subject: Re: [RFC][BUG] tracer: Fails to work Message-ID: <20160128135733.GQ6356@twins.programming.kicks-ass.net> References: <20160128080859.GB6357@twins.programming.kicks-ass.net> <1069612139.6639.1453988280286.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1069612139.6639.1453988280286.JavaMail.zimbra@efficios.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 28, 2016 at 01:38:00PM +0000, Mathieu Desnoyers wrote: > Thoughts ? So ideally dumping the trace data would not depend on any of that, because I can break it all :-) Not being able to access the trace data completely and utterly defeats the purpose of having a tracer in the first place.