From: Ingo Molnar <mingo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Garnier <thgarnie@google.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: hide unused allocate_percpu_fixmap_ptes
Date: Sat, 30 Dec 2017 09:36:59 +0100 [thread overview]
Message-ID: <20171230083659.6zp6s4wv27xfo452@gmail.com> (raw)
In-Reply-To: <20171218134417.3000184-1-arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> wrote:
> The new function is not always used, causing a warning whenever
> CONFIG_CPU_SUP_INTEL is disabled:
>
> arch/x86/kernel/cpu/common.c:522:20: error: 'allocate_percpu_fixmap_ptes' defined but not used [-Werror=unused-function]
>
> Hide it in the same #ifdef.
>
> Fixes: 3015f86f838c ("x86/fixmap: Add debugstore entries to cpu_entry_area")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> arch/x86/kernel/cpu/common.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 6444f91e8d3c..6f354416a67f 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -519,11 +519,13 @@ static DEFINE_PER_CPU_PAGE_ALIGNED(struct entry_stack_page,
> * Force the population of PMDs for not yet allocated per cpu
> * memory like debug store buffers.
> */
> +#ifdef CONFIG_CPU_SUP_INTEL
> static void __init allocate_percpu_fixmap_ptes(int idx, int pages)
> {
> for (; pages; pages--, idx--)
> __set_fixmap(idx, 0, PAGE_NONE);
> }
> +#endif
Ok, this fix should be moot as the allocate_percpu_fixmap_ptes() is gone from the
latest versions of PTI.
Thanks,
Ingo
prev parent reply other threads:[~2017-12-30 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 13:43 Arnd Bergmann
2017-12-30 8:36 ` Ingo Molnar [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=20171230083659.6zp6s4wv27xfo452@gmail.com \
--to=mingo@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®