Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759138Ab2HJBlb (ORCPT ); Thu, 9 Aug 2012 21:41:31 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:15509 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754137Ab2HJBl3 (ORCPT ); Thu, 9 Aug 2012 21:41:29 -0400 X-Authority-Analysis: v=2.0 cv=IOWA+3TG c=1 sm=0 a=s5Htg7xnQOKvHEu9STBOug==:17 a=OpT9cpI26MMA:10 a=3rytjJLIguwA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=meVymXHHAAAA:8 a=ayC55rCoAAAA:8 a=2Mck7MtwRj-EGOkNCYAA:9 a=PUjeQqilurYA:10 a=s5Htg7xnQOKvHEu9STBOug==:117 X-Cloudmark-Score: 0 X-Originating-IP: 72.230.195.127 Message-ID: <1344562886.6935.93.camel@gandalf.stny.rr.com> Subject: Re: [RFC][PATCH] tracepoints: Move the work out of line from hotpath sections From: Steven Rostedt To: David Daney Cc: "H. Peter Anvin" , Mathieu Desnoyers , LKML , Linus Torvalds , Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Masami Hiramatsu , Avi Kivity , Christoph Hellwig , Andrew Morton Date: Thu, 09 Aug 2012 21:41:26 -0400 In-Reply-To: <50244D9A.2070000@gmail.com> References: <1344544823.6935.82.camel@gandalf.stny.rr.com> <20120809205053.GB15109@Krystal> <1344551131.6935.90.camel@gandalf.stny.rr.com> <502444CC.8030906@linux.intel.com> <50244D9A.2070000@gmail.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.4.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 933 Lines: 27 On Thu, 2012-08-09 at 16:54 -0700, David Daney wrote: > On 08/09/2012 04:16 PM, H. Peter Anvin wrote: > > On 08/09/2012 03:25 PM, Steven Rostedt wrote: > >>> > >>> It might be better to improve gcc to move really cold branches out of > >>> line (really, really far away), and use the compiler to do this, rather > >>> than to use an extra indirection that adds bloat and complexity to the > >>> kernel. > > Oh, you mean like: -freorder-blocks-and-partition Actually, what would be really nice is to place a block in a section of your choice. Something like: if (unlikely(x)) __attribute__((section(".unlikely"))) { /* code here will be in the ".unlikely" section */ } -- Steve -- 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/