From: Borislav Petkov <bp@alien8.de>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: mingo@kernel.org, bp@suse.de, hpa@zytor.com, tglx@linutronix.de,
mcgrof@suse.com, jgross@suse.com, paul.gortmaker@windriver.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/mm/pat: Change pat_disable() to emulate PAT table
Date: Fri, 11 Mar 2016 10:12:30 +0100 [thread overview]
Message-ID: <20160311091229.GA4347@pd.tnic> (raw)
In-Reply-To: <1457671546-13486-2-git-send-email-toshi.kani@hpe.com>
On Thu, Mar 10, 2016 at 09:45:45PM -0700, Toshi Kani wrote:
> Since 'commit 9cd25aac1f44 ("x86/mm/pat: Emulate PAT when it
> is disabled")', we emulate a PAT table when PAT is disabled.
> This requires pat_init() be called even if PAT is disabled,
> which revealed a long standing issue that PAT is left enabled
> without calling pat_init() at all.
>
> pat_init() is called from MTRR code since it relies on MTRR's
> rendezvous handler to initialize PAT for all APs . However,
> when CPU does not support MTRR, ex. qemu32's virtual CPU, MTRR
> is set disabled and does not call pat_init(). There is no
> interface available for MTRR to disable PAT, either.
>
> Change pat_disable() to a regular function (from an inline func)
> so that MTRR can call it to disable PAT when MTRR is disabled.
> pat_disable() sets PAT disabled, and calls pat_disable_init()
> to emulate the PAT table.
>
> link: https://lkml.org/lkml/2016/3/10/402
> Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Luis R. Rodriguez <mcgrof@suse.com>
> Cc: Juergen Gross <jgross@suse.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/x86/include/asm/pat.h | 1 +
> arch/x86/mm/pat.c | 84 +++++++++++++++++++++++++++-----------------
> 2 files changed, 52 insertions(+), 33 deletions(-)
>
> diff --git a/arch/x86/include/asm/pat.h b/arch/x86/include/asm/pat.h
> index ca6c228..016142b 100644
> --- a/arch/x86/include/asm/pat.h
> +++ b/arch/x86/include/asm/pat.h
> @@ -5,6 +5,7 @@
> #include <asm/pgtable_types.h>
>
> bool pat_enabled(void);
> +void pat_disable(const char *reason);
> extern void pat_init(void);
> void pat_init_cache_modes(u64);
>
> diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
> index f4ae536..1ff8aa9 100644
> --- a/arch/x86/mm/pat.c
> +++ b/arch/x86/mm/pat.c
> @@ -40,11 +40,19 @@
> static bool boot_cpu_done;
>
> static int __read_mostly __pat_enabled = IS_ENABLED(CONFIG_X86_PAT);
> +static void pat_disable_init(void);
>
> -static inline void pat_disable(const char *reason)
> +void pat_disable(const char *reason)
> {
> + if (boot_cpu_done) {
> + pr_info("x86/PAT: PAT cannot be disabled after initialized\n");
pr_err()
> + return;
> + }
> +
> __pat_enabled = 0;
> pr_info("x86/PAT: %s\n", reason);
> +
> + pat_disable_init();
Why can't you call pat_init() here simply? It checks pat_enabled(). You
can call it pat_setup() or so if it looks confusing to call an init
function in a disable function...
Then you don't have to add yet another static disable_init_done but rely on
boot_cpu_done which gets set in pat_init().
Also, I don't see the static_cpu_has() check I suggested yesterday - we need to
check the feature bits if PAT gets disabled early on some old Intels.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-03-11 9:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 4:45 [PATCH 0/2] Refactor MTRR and PAT initializations Toshi Kani
2016-03-11 4:45 ` [PATCH 1/2] x86/mm/pat: Change pat_disable() to emulate PAT table Toshi Kani
2016-03-11 9:12 ` Borislav Petkov [this message]
2016-03-11 16:27 ` Toshi Kani
2016-03-11 15:54 ` Borislav Petkov
2016-03-11 19:28 ` Toshi Kani
2016-03-12 11:55 ` Borislav Petkov
2016-03-14 21:37 ` Toshi Kani
2016-03-15 11:00 ` Borislav Petkov
2016-03-15 22:02 ` Toshi Kani
2016-03-15 0:29 ` Luis R. Rodriguez
2016-03-15 3:11 ` Toshi Kani
2016-03-15 11:01 ` Borislav Petkov
2016-03-15 15:43 ` Toshi Kani
2016-03-15 15:47 ` Borislav Petkov
2016-03-15 17:11 ` Toshi Kani
2016-03-15 16:33 ` Borislav Petkov
2016-03-15 21:31 ` Luis R. Rodriguez
2016-03-11 4:45 ` [PATCH 2/2] x86/mtrr: Refactor PAT initialization code Toshi Kani
2016-03-11 9:01 ` Ingo Molnar
2016-03-11 9:13 ` Ingo Molnar
2016-03-11 18:34 ` Toshi Kani
2016-03-12 16:18 ` Ingo Molnar
2016-03-14 19:47 ` Toshi Kani
2016-03-14 22:50 ` Luis R. Rodriguez
2016-03-15 0:37 ` Toshi Kani
2016-03-15 15:56 ` Borislav Petkov
2016-03-16 15:44 ` Joe Lawrence
2016-03-11 9:24 ` Borislav Petkov
2016-03-11 18:57 ` Toshi Kani
2016-03-11 22:17 ` Luis R. Rodriguez
2016-03-11 23:56 ` Toshi Kani
2016-03-11 23:34 ` Luis R. Rodriguez
2016-03-12 1:16 ` Toshi Kani
2016-03-15 0:15 ` Luis R. Rodriguez
2016-03-15 23:48 ` Toshi Kani
2016-03-15 23:29 ` Luis R. Rodriguez
2016-03-17 21:56 ` Toshi Kani
2016-03-18 0:06 ` Luis R. Rodriguez
2016-03-18 21:35 ` Toshi Kani
2016-03-29 17:14 ` Luis R. Rodriguez
2016-03-29 21:46 ` Toshi Kani
2016-03-29 22:12 ` Luis R. Rodriguez
2016-03-30 0:16 ` Toshi Kani
2016-03-29 23:43 ` Luis R. Rodriguez
2016-03-30 1:07 ` Toshi Kani
2016-03-30 0:34 ` Luis R. Rodriguez
2016-04-09 2:04 ` Luis R. Rodriguez
2016-04-11 14:30 ` Toshi Kani
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=20160311091229.GA4347@pd.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hpe.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