From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: leitao@debian.org, mauricfo@linux.vnet.ibm.com, linuxram@us.ibm.com
Subject: Re: powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
Date: Thu, 12 Apr 2018 00:49:29 +1000 (AEST) [thread overview]
Message-ID: <40Ln4T5mK0z9s3D@ozlabs.org> (raw)
In-Reply-To: <20180405124913.12001-1-mpe@ellerman.id.au>
On Thu, 2018-04-05 at 12:49:13 UTC, Michael Ellerman wrote:
> The recent LPM changes to setup_rfi_flush() are causing some section
> mismatch warnings because we removed the __init annotation on
> setup_rfi_flush():
>
> The function setup_rfi_flush() references
> the function __init ppc64_bolted_size().
> the function __init memblock_alloc_base().
>
> The references are actually in init_fallback_flush(), but that is
> inlined into setup_rfi_flush().
>
> These references are safe because:
> - only pseries calls setup_rfi_flush() at runtime
> - pseries always passes L1D_FLUSH_FALLBACK at boot
> - so the fallback flush area will always be allocated
> - so the check in init_fallback_flush() will always return early:
> /* Only allocate the fallback flush area once (at boot time). */
> if (l1d_flush_fallback_area)
> return;
>
> - and therefore we won't actually call the freed init routines.
>
> We should rework the code to make it safer by default rather than
> relying on the above, but for now as a quick-fix just add a __ref
> annotation to squash the warning.
>
> Fixes: abf110f3e1ce ("powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc fixes.
https://git.kernel.org/powerpc/c/501a78cbc17c329fabf8e9750a1e9a
cheers
prev parent reply other threads:[~2018-04-11 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 12:49 [PATCH] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush() Michael Ellerman
2018-04-11 14:49 ` Michael Ellerman [this message]
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=40Ln4T5mK0z9s3D@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=leitao@debian.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mauricfo@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).