mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: xen-devel@lists.xenproject.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 01/10] x86/mtrr: fix MTRR fixup on APs
Date: Mon, 22 Aug 2022 10:32:28 +0200	[thread overview]
Message-ID: <e2ea61ad-3ff3-2ba7-3426-834b87fe85a3@suse.com> (raw)
In-Reply-To: <YwM+GPu8hFowl2R7@zn.tnic>


[-- Attachment #1.1.1: Type: text/plain, Size: 1242 bytes --]

On 22.08.22 10:28, Borislav Petkov wrote:
> On Mon, Aug 22, 2022 at 07:17:40AM +0200, Juergen Gross wrote:
>> And then there is mtrr_state_warn() in arch/x86/kernel/cpu/mtrr/generic.c
>> which has a comment saying:
>>
>> /* Some BIOS's are messed up and don't set all MTRRs the same! */
> 
> That thing also says:
> 
>          pr_info("mtrr: probably your BIOS does not setup all CPUs.\n");
>          pr_info("mtrr: corrected configuration.\n");
> 
> because it'll go and force on all CPUs the MTRR state it read from the
> BSP in mtrr_bp_init->get_mtrr_state.
> 
>> Yes, the chances are slim to hit such a box,
> 
> Well, my workstation says:
> 
> $ dmesg | grep -i mtrr
> [    0.391514] mtrr: your CPUs had inconsistent variable MTRR settings
> [    0.395199] mtrr: probably your BIOS does not setup all CPUs.
> [    0.399199] mtrr: corrected configuration.
> 
> but that's the variable MTRRs.
> 
>> but your reasoning suggests I should remove the related code?
> 
> My reasoning says you should not do anything at all here - works as
> advertized. :-)
> 

And what about the:

   pr_warn("mtrr: your CPUs had inconsistent MTRRdefType settings\n");

This is the case the patch would fix.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-08-22  8:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20  9:25 [PATCH v2 00/10] x86: make pat and mtrr independent from each other Juergen Gross
2022-08-20  9:25 ` [PATCH v2 01/10] x86/mtrr: fix MTRR fixup on APs Juergen Gross
2022-08-20 10:28   ` Greg KH
2022-08-21 12:25   ` Borislav Petkov
2022-08-21 21:41     ` Borislav Petkov
2022-08-22  5:17       ` Juergen Gross
2022-08-22  8:28         ` Borislav Petkov
2022-08-22  8:32           ` Juergen Gross [this message]
2022-10-19 18:45   ` [tip: x86/cpu] x86/mtrr: Add comment for set_mtrr_state() serialization tip-bot2 for Juergen Gross
2022-08-20  9:25 ` [PATCH v2 02/10] x86/mtrr: remove unused cyrix_set_all() function Juergen Gross
2022-08-25 10:31   ` Borislav Petkov
2022-08-25 10:38     ` Juergen Gross
2022-08-25 10:41     ` Juergen Gross
2022-08-25 11:42       ` Borislav Petkov
2022-08-25 12:13         ` Juergen Gross
2022-08-20  9:25 ` [PATCH v2 03/10] x86/mtrr: replace use_intel() with a local flag Juergen Gross
2022-08-20  9:25 ` [PATCH v2 04/10] x86: move some code out of arch/x86/kernel/cpu/mtrr Juergen Gross
2022-08-20  9:25 ` [PATCH v2 05/10] x86/mtrr: split generic_set_all() Juergen Gross
2022-08-20  9:25 ` [PATCH v2 06/10] x86/mtrr: remove set_all callback from struct mtrr_ops Juergen Gross
2022-08-20  9:25 ` [PATCH v2 07/10] x86/mtrr: simplify mtrr_bp_init() Juergen Gross
2022-08-20  9:25 ` [PATCH v2 08/10] x86/mtrr: let cache_aps_delayed_init replace mtrr_aps_delayed_init Juergen Gross
2022-08-20  9:25 ` [PATCH v2 09/10] x86/mtrr: add a stop_machine() handler calling only cache_cpu_init() Juergen Gross
2022-08-20  9:25 ` [PATCH v2 10/10] x86: decouple pat and mtrr handling Juergen Gross

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=e2ea61ad-3ff3-2ba7-3426-834b87fe85a3@suse.com \
    --to=jgross@suse.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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®