From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sathvika Vasireddy <sv@linux.ibm.com>
Cc: peterz@infradead.org, Nicholas Piggin <npiggin@gmail.com>,
naveen.n.rao@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
jpoimboe@kernel.org
Subject: Re: [PATCH] powerpc/64: Fix unannotated intra-function call warning
Date: Fri, 17 Feb 2023 16:32:49 +1100 [thread overview]
Message-ID: <20230217163249.17ac772e@canb.auug.org.au> (raw)
In-Reply-To: <20230217043226.1020041-1-sv@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
Hi all,
On Fri, 17 Feb 2023 10:02:26 +0530 Sathvika Vasireddy <sv@linux.ibm.com> wrote:
>
> objtool throws the following warning:
> arch/powerpc/kernel/head_64.o: warning: objtool: .text+0x6128:
> unannotated intra-function call
>
> Fix the warning by annotating start_initialization_book3s symbol with the
> SYM_FUNC_START_LOCAL and SYM_FUNC_END macros.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Sathvika Vasireddy <sv@linux.ibm.com>
> ---
> arch/powerpc/kernel/head_64.S | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
> index 3a7266fa8a18..1febb56ebaeb 100644
> --- a/arch/powerpc/kernel/head_64.S
> +++ b/arch/powerpc/kernel/head_64.S
> @@ -472,7 +472,7 @@ SYM_FUNC_START_LOCAL(__mmu_off)
> b . /* prevent speculative execution */
> SYM_FUNC_END(__mmu_off)
>
> -start_initialization_book3s:
> +SYM_FUNC_START_LOCAL(start_initialization_book3s)
> mflr r25
>
> /* Setup some critical 970 SPRs before switching MMU off */
> @@ -494,6 +494,7 @@ start_initialization_book3s:
>
> mtlr r25
> blr
> +SYM_FUNC_END(start_initialization_book3s)
> #endif
>
> /*
> --
> 2.31.1
>
That at least makes the warning go away for me.
Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>
Fixes: 58f24eea5278 ("powerpc/64s: Refactor initialisation after prom")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-17 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 4:32 [PATCH] powerpc/64: Fix unannotated intra-function call warning Sathvika Vasireddy
2023-02-17 5:32 ` Stephen Rothwell [this message]
2023-02-17 7:07 ` Josh Poimboeuf
2023-02-20 3:49 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230217163249.17ac772e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jpoimboe@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sv@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox