Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755177AbcJLNzy (ORCPT ); Wed, 12 Oct 2016 09:55:54 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:55479 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754864AbcJLNzp (ORCPT ); Wed, 12 Oct 2016 09:55:45 -0400 Date: Wed, 12 Oct 2016 15:53:16 +0200 (CEST) From: Thomas Gleixner To: Marcin Nowakowski cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, luto@amacapital.net, rostedt@goodmis.org, Ingo Molnar , "H. Peter Anvin" , x86@kernel.org Subject: Re: [PATCH v3 05/11] x86/tracing: fix compat syscall handling In-Reply-To: <1476182576-15247-6-git-send-email-marcin.nowakowski@imgtec.com> Message-ID: References: <1476182576-15247-1-git-send-email-marcin.nowakowski@imgtec.com> <1476182576-15247-6-git-send-email-marcin.nowakowski@imgtec.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 452 Lines: 14 On Tue, 11 Oct 2016, Marcin Nowakowski wrote: > -/* > - * Because ia32 syscalls do not map to x86_64 syscall numbers > - * this screws up the trace output when tracing a ia32 task. > - * Instead of reporting bogus syscalls, just do not trace them. > - * > - * If the user really wants these, then they should use the > - * raw syscall tracepoints with filtering. Why aren't you moving this information to the new place? It's valuable. Thanks, tglx