[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250214194241.3aymq2kr6gky5zfv@jpoimboe>
Date: Fri, 14 Feb 2025 11:42:41 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Puranjay Mohan <puranjay@...nel.org>
Cc: Indu Bhagat <indu.bhagat@...cle.com>, Song Liu <song@...nel.org>,
Weinan Liu <wnliu@...gle.com>, Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Mark Rutland <mark.rutland@....com>, roman.gushchin@...ux.dev,
Will Deacon <will@...nel.org>, Ian Rogers <irogers@...gle.com>,
linux-toolchains@...r.kernel.org, linux-kernel@...r.kernel.org,
live-patching@...r.kernel.org, joe.lawrence@...hat.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/8] unwind, arm64: add sframe unwinder for kernel
On Fri, Feb 14, 2025 at 11:38:22AM -0800, Josh Poimboeuf wrote:
> On Fri, Feb 14, 2025 at 06:58:01PM +0000, Puranjay Mohan wrote:
> > and the linker script has this line:
> >
> > .sframe : AT(ADDR(.sframe) - 0) { __start_sframe_header = .; KEEP(*(.sframe)) __stop_sframe_header = .; }
> >
> > So, do can you suggest the best way to fix these warnings?
>
> Just add *(.init.sframe) like so:
>
> .sframe : AT(ADDR(.sframe) - 0) { __start_sframe_header = .; KEEP(*(.sframe) *(.init.sframe)) __stop_sframe_header = .; }
Actually each probably needs its own KEEP:
... KEEP(*(.sframe)) KEEP(*(.init.sframe)) ...
or so.
--
Josh
Powered by blists - more mailing lists