[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250213090334.dc00185d643d96722dab9902@kernel.org>
Date: Thu, 13 Feb 2025 09:03:34 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Peter Zijlstra <peterz@...radead.org>, "Masami Hiramatsu (Google)"
<mhiramat@...nel.org>, Gabriel de Perthuis <g2p.code@...il.com>, Haiyue
Wang <haiyuewa@....com>, Sami Tolvanen <samitolvanen@...gle.com>, Mark
Rutland <mark.rutland@....com>, Thomas Gleixner <tglx@...utronix.de>, Ingo
Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
<dave.hansen@...ux.intel.com>, "H . Peter Anvin" <hpa@...or.com>,
x86@...nel.org, linux-trace-kernel@...r.kernel.org, LKML
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ftrace: x86: Fix a compile error about
get_kernel_nofault()
On Tue, 11 Feb 2025 10:50:02 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Tue, 11 Feb 2025 11:09:14 +0100
> Peter Zijlstra <peterz@...radead.org> wrote:
>
> > I was aiming my patch for x86/core, but if there's a reason to expedite
> > them, I can stick it in x86/urgent I suppose.
> >
> > Just need a reason -- what's this compile error nonsense about, my
> > kernels build just fine?
>
> Masami,
>
> Do you have a config that fails to build without this fix? If so, can you
> please reply with it, and then this can go in as a quick fix.
Let me share the config. But as Sami pointed, the combination of
CONFIG_GENDWARFKSYMS and CONFIG_FUNCTION_TRACER caused this issue.
Thank you,
>
> Thanks,
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Download attachment "build-error.kconfig" of type "application/octet-stream" (191001 bytes)
Powered by blists - more mailing lists