From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751724AbdKYUGQ (ORCPT ); Sat, 25 Nov 2017 15:06:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:39214 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751224AbdKYUGP (ORCPT ); Sat, 25 Nov 2017 15:06:15 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EC62E219AE Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Sat, 25 Nov 2017 15:06:10 -0500 From: Steven Rostedt To: Thomas Gleixner Cc: Ingo Molnar , Andy Lutomirski , Dave Hansen , Josh Poimboeuf , LKML , Andy Lutomirski , "H . Peter Anvin" , Peter Zijlstra , Borislav Petkov , Linus Torvalds , Andrey Ryabinin , kasan-dev@googlegroups.com, Masami Hiramatsu Subject: Re: [PATCH] x86/mm/kaiser: Fix IRQ entries text section mapping Message-ID: <20171125150610.29f83ce9@gandalf.local.home> In-Reply-To: References: <20171124172411.19476-1-mingo@kernel.org> <20171124202237.oytdkqq25s3ak2ul@gmail.com> <20171124220934.q7ovq4yzaihevqls@gmail.com> <464B14E7-EC38-4A5A-8BF6-B086F437C6D1@amacapital.net> <20171124225311.zpbgsejobpzxm7tb@gmail.com> <20171125092113.p2shs3hjy6q2mip2@gmail.com> <20171125093243.4gmkelmyb4mnhvos@gmail.com> <20171125093949.qbnibvj3nej5vidz@gmail.com> <20171125111721.p2o3khstk5tawzqt@gmail.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 25 Nov 2017 17:08:08 +0100 (CET) Thomas Gleixner wrote: > Tracing uses it to stop the printout of the function graph. Should be safe > to print the C-Code functions. It uses it to filter out interrupts, as well as to print the: "<==========" "==========>" annotations. Since function tracing only traces C functions, this will be lost. That said, we could possibly replace that check with keeping track of the hardirq state in the "flags" field of the trace event entry. -- Steve