[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171125150610.29f83ce9@gandalf.local.home>
Date: Sat, 25 Nov 2017 15:06:10 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...nel.org>,
Andy Lutomirski <luto@...capital.net>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
kasan-dev@...glegroups.com, Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH] x86/mm/kaiser: Fix IRQ entries text section mapping
On Sat, 25 Nov 2017 17:08:08 +0100 (CET)
Thomas Gleixner <tglx@...utronix.de> 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
Powered by blists - more mailing lists