From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965488AbbDVX52 (ORCPT ); Wed, 22 Apr 2015 19:57:28 -0400 Received: from mga01.intel.com ([192.55.52.88]:9262 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934004AbbDVX51 (ORCPT ); Wed, 22 Apr 2015 19:57:27 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,627,1422950400"; d="scan'208";a="484432682" Date: Wed, 22 Apr 2015 16:57:25 -0700 From: Andi Kleen To: Dave Hansen Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org, mingo@redhat.com Subject: Re: [PATCH] [RFC] tracing xsave operations Message-ID: <20150422235725.GH13605@tassilo.jf.intel.com> References: <20150422234212.A4F67395@viggo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150422234212.A4F67395@viggo.jf.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Am I doing something wrong? Are there good alternatives for when > we want to trace something that's done in a header? I had to out of line multiple inlines too to trace them. Like the MSR tracing. The trace includes just have too many dependencies. Most of it comes from RCU i believe. It would be great to somehow untangle that. Short of that have to just keep moving things out of line to trace them. -Andi