Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756714AbaDBAfJ (ORCPT ); Tue, 1 Apr 2014 20:35:09 -0400 Received: from mail-vc0-f177.google.com ([209.85.220.177]:51309 "EHLO mail-vc0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751847AbaDBAfH (ORCPT ); Tue, 1 Apr 2014 20:35:07 -0400 MIME-Version: 1.0 In-Reply-To: <20140401200145.05e0437e@gandalf.local.home> References: <201403312105.s2VL5AqX010173@terminus.zytor.com> <20140331230347.GH32556@tassilo.jf.intel.com> <533B0B5F.2040907@linux.intel.com> <20140401200145.05e0437e@gandalf.local.home> Date: Tue, 1 Apr 2014 17:35:05 -0700 X-Google-Sender-Auth: wdCxOTbMgGs-_XBwrIYShqdLwCs Message-ID: Subject: Re: [GIT PULL] x86 LTO changes for v3.15 From: Linus Torvalds To: Steven Rostedt Cc: "H. Peter Anvin" , Andi Kleen , Gleb Natapov , Peter Anvin , Jan Hubicka , Linux Kernel Mailing List , Ingo Molnar , Paolo Bonzini , Jaroslav Kysela , Peter Zijlstra , Rusty Russell , Thomas Gleixner Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 1, 2014 at 5:01 PM, Steven Rostedt wrote: > > Why would they break tracing? I remember there was a issue with compat > calls, are these related to that? They "break" tracing by being invisible to syscall tracing. As you really should know ;) The syscall tracing feature depends on the wrappers that SYSCALL_DEFINEx() creates. See the SYSCALL_TRACE_ENTER_EVENT() etc crud in So there's no SYSCALL_METADATA for those system calls that weren't created with the proper SYSCALL_DEFINE() wrappers. Linus -- 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/