From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757502Ab0JYWdr (ORCPT ); Mon, 25 Oct 2010 18:33:47 -0400 Received: from terminus.zytor.com ([198.137.202.10]:57986 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753263Ab0JYWdp (ORCPT ); Mon, 25 Oct 2010 18:33:45 -0400 Message-ID: <4CC60585.70503@zytor.com> Date: Mon, 25 Oct 2010 15:32:37 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jason Baron CC: Steven Rostedt , Thomas Gleixner , Mathieu Desnoyers , Koki Sanagi , Peter Zijlstra , Ingo Molnar , Frederic Weisbecker , nhorman@tuxdriver.com, scott.a.mcmillan@intel.com, laijs@cn.fujitsu.com, LKML , eric.dumazet@gmail.com, kaneshige.kenji@jp.fujitsu.com, David Miller , izumi.taku@jp.fujitsu.com, kosaki.motohiro@jp.fujitsu.com, Heiko Carstens , "Luck, Tony" Subject: Re: [PATCH] tracing: Cleanup the convoluted softirq tracepoints References: <20101019132236.GA19197@Krystal> <1287496495.16971.372.camel@gandalf.stny.rr.com> <20101019142820.GA14520@Krystal> <20101019212816.GA2855@redhat.com> <1287538590.16971.548.camel@gandalf.stny.rr.com> <20101020015227.GA2011@redhat.com> In-Reply-To: <20101020015227.GA2011@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/19/2010 06:52 PM, Jason Baron wrote: > > thanks Steve. I was about to say this. When CONFIG_CC_OPTIMIZE_FOR_SIZE > is not set we don't get the double 'jmp' and the tracepoint code is > moved out of line. It was mentioned that a number of distros ship with > CONFIG_CC_OPTIMIZE_FOR_SIZE not set, and as Steve mentioned my original > patch set was conditional on !CONFIG_CC_OPTIMIZE_FOR_SIZE. > > using hot/cold labels gcc can fix the CONFIG_CC_OPTIMIZE_FOR_SIZE case, > but its a non-trivial amount of work for gcc. I was hoping that if jump > labels are included, we could make the gcc work happen. > That's fair. I think jump labels are still a win even in the double-jump case (especially if the the tracepoint turns into a NOP rather than a JMP.) Code generated with -Os has a bunch of other problems, too. -hpa