public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: lists@nerdbynature.de, mikelley@microsoft.com,
	torvalds@linux-foundation.org, Juergen Gross <jgross@suse.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH v2 2/8] x86/mtrr: support setting MTRR state for software defined MTRRs
Date: Thu,  9 Feb 2023 08:22:14 +0100	[thread overview]
Message-ID: <20230209072220.6836-3-jgross@suse.com> (raw)
In-Reply-To: <20230209072220.6836-1-jgross@suse.com>

When running virtualized, MTRR access can be reduced (e.g. in Xen PV
guests or when running as a SEV-SNP guest under Hyper-V). Typically
the hypervisor will reset the MTRR feature in cpuid data, resulting
in no MTRR memory type information being available for the kernel.

This has turned out to result in problems:

- Hyper-V SEV-SNP guests using uncached mappings where they shouldn't
- Xen PV dom0 mapping memory as WB which should be UC- instead

Solve those problems by supporting to set a fixed MTRR state,
overwriting the empty state used today. In case such a state has been
set, don't call get_mtrr_state() in mtrr_bp_init(). The set state
will only be used by mtrr_type_lookup(), as in all other cases
mtrr_enabled() is being checked, which will return false. Accept the
overwrite call only in case of MTRRs being disabled in cpuid.

Signed-off-by: Juergen Gross <jgross@suse.com>
---
V2:
- new patch
---
 arch/x86/include/asm/mtrr.h        |  2 ++
 arch/x86/kernel/cpu/mtrr/generic.c | 38 ++++++++++++++++++++++++++++++
 arch/x86/kernel/cpu/mtrr/mtrr.c    |  9 +++++++
 3 files changed, 49 insertions(+)

diff --git a/arch/x86/include/asm/mtrr.h b/arch/x86/include/asm/mtrr.h
index f0eeaf6e5f5f..0b8f51d683dc 100644
--- a/arch/x86/include/asm/mtrr.h
+++ b/arch/x86/include/asm/mtrr.h
@@ -31,6 +31,8 @@
  */
 # ifdef CONFIG_MTRR
 void mtrr_bp_init(void);
+void mtrr_overwrite_state(struct mtrr_var_range *var, unsigned int num_var,
+			  mtrr_type *fixed, mtrr_type def_type);
 extern u8 mtrr_type_lookup(u64 addr, u64 end, u8 *uniform);
 extern void mtrr_save_fixed_ranges(void *);
 extern void mtrr_save_state(void);
diff --git a/arch/x86/kernel/cpu/mtrr/generic.c b/arch/x86/kernel/cpu/mtrr/generic.c
index ee09d359e08f..788bc16888a5 100644
--- a/arch/x86/kernel/cpu/mtrr/generic.c
+++ b/arch/x86/kernel/cpu/mtrr/generic.c
@@ -240,6 +240,44 @@ static u8 mtrr_type_lookup_variable(u64 start, u64 end, u64 *partial_end,
 	return mtrr_state.def_type;
 }
 
+/**
+ * mtrr_overwrite_state - set fixed MTRR state
+ *
+ * Used to set MTRR state via different means (e.g. with data obtained from
+ * a hypervisor).
+ */
+void mtrr_overwrite_state(struct mtrr_var_range *var, unsigned int num_var,
+			  mtrr_type *fixed, mtrr_type def_type)
+{
+	unsigned int i;
+
+	if (boot_cpu_has(X86_FEATURE_MTRR))
+		return;
+
+	if (var) {
+		if (num_var > MTRR_MAX_VAR_RANGES) {
+			pr_warn("Trying to overwrite MTRR state with %u variable entries\n",
+				num_var);
+			num_var = MTRR_MAX_VAR_RANGES;
+		}
+		for (i = 0; i < num_var; i++)
+			mtrr_state.var_ranges[i] = var[i];
+		num_var_ranges = num_var;
+	}
+
+	if (fixed) {
+		for (i = 0; i < MTRR_NUM_FIXED_RANGES; i++)
+			mtrr_state.fixed_ranges[i] = fixed[i];
+		mtrr_state.enabled |= MTRR_STATE_MTRR_FIXED_ENABLED;
+		mtrr_state.have_fixed = 1;
+	}
+
+	mtrr_state.def_type = def_type;
+	mtrr_state.enabled |= MTRR_STATE_MTRR_ENABLED;
+
+	mtrr_state_set = 1;
+}
+
 /**
  * mtrr_type_lookup - look up memory type in MTRR
  *
diff --git a/arch/x86/kernel/cpu/mtrr/mtrr.c b/arch/x86/kernel/cpu/mtrr/mtrr.c
index 542ca5639dfd..b73fe243c7fd 100644
--- a/arch/x86/kernel/cpu/mtrr/mtrr.c
+++ b/arch/x86/kernel/cpu/mtrr/mtrr.c
@@ -668,6 +668,15 @@ void __init mtrr_bp_init(void)
 	const char *why = "(not available)";
 	unsigned int phys_addr;
 
+	if (mtrr_state.enabled) {
+		/* Software overwrite of MTRR state, only for generic case. */
+		mtrr_calc_physbits(true);
+		init_table();
+		pr_info("MTRRs set to read-only\n");
+
+		return;
+	}
+
 	phys_addr = mtrr_calc_physbits(boot_cpu_has(X86_FEATURE_MTRR));
 
 	if (boot_cpu_has(X86_FEATURE_MTRR)) {
-- 
2.35.3


  parent reply	other threads:[~2023-02-09  7:23 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  7:22 [PATCH v2 0/8] x86/mtrr: fix handling with PAT but without MTRR Juergen Gross
2023-02-09  7:22 ` [PATCH v2 1/8] x86/mtrr: split off physical address size calculation Juergen Gross
2023-02-11 10:08   ` Borislav Petkov
2023-02-13  6:19     ` Juergen Gross
2023-02-09  7:22 ` Juergen Gross [this message]
2023-02-13  1:07   ` [PATCH v2 2/8] x86/mtrr: support setting MTRR state for software defined MTRRs Michael Kelley (LINUX)
2023-02-13  6:27     ` Juergen Gross
2023-02-13  6:43       ` Michael Kelley (LINUX)
2023-02-13 11:39   ` Borislav Petkov
2023-02-13 14:07     ` Juergen Gross
2023-02-13 15:03       ` Borislav Petkov
2023-02-13 15:11         ` Borislav Petkov
2023-02-13 15:18           ` Juergen Gross
2023-02-13 15:40             ` Borislav Petkov
2023-02-13 15:44               ` Juergen Gross
2023-02-13 18:53                 ` Borislav Petkov
2023-02-14  7:04                   ` Juergen Gross
2023-02-14  8:58                     ` Borislav Petkov
2023-02-14  9:02                       ` Juergen Gross
2023-02-14  9:10                         ` Borislav Petkov
2023-02-14  9:17                           ` Juergen Gross
2023-02-14  9:32                             ` Borislav Petkov
2023-02-13 15:27           ` Dave Hansen
2023-02-13 15:38             ` Juergen Gross
2023-02-13 15:36         ` Juergen Gross
2023-02-13 18:43           ` Borislav Petkov
2023-02-14  7:01             ` Juergen Gross
2023-02-14  0:45       ` Kirill A. Shutemov
2023-02-16  9:32     ` Juergen Gross
2023-02-16 11:02       ` Jeremi Piotrowski
2023-02-16 11:25       ` Borislav Petkov
2023-02-16 12:19         ` Juergen Gross
2023-02-16 12:29           ` Borislav Petkov
2023-02-16 16:04             ` Michael Kelley (LINUX)
2023-02-16 11:07     ` Jeremi Piotrowski
2023-02-16 11:27       ` Borislav Petkov
2023-02-09  7:22 ` [PATCH v2 3/8] x86/hyperv: set MTRR state when running as SEV-SNP Hyper-V guest Juergen Gross
2023-02-13  1:07   ` Michael Kelley (LINUX)
2023-02-13  6:28     ` Juergen Gross
2023-02-09  7:22 ` [PATCH v2 4/8] x86/xen: set MTRR state when running as Xen PV initial domain Juergen Gross
2023-02-09  7:22 ` [PATCH v2 5/8] x86/mtrr: revert commit 90b926e68f50 Juergen Gross
2023-02-10 18:59   ` Linux regression tracking (Thorsten Leemhuis)
2023-02-13  6:07     ` Juergen Gross
2023-02-13 11:46       ` Christian Kujau
2023-02-13 16:23         ` Juergen Gross
2023-02-13 17:01           ` Michael Kelley (LINUX)
2023-02-13 17:24             ` Juergen Gross
2023-02-13 22:54           ` Christian Kujau
2023-02-14  7:13             ` Juergen Gross
2023-02-09  7:22 ` [PATCH v2 6/8] x86/mtrr: don't let mtrr_type_lookup() return MTRR_TYPE_INVALID Juergen Gross
2023-02-09  7:22 ` [PATCH v2 7/8] x86/mm: only check uniform after calling mtrr_type_lookup() Juergen Gross
2023-02-11  0:06   ` Edgecombe, Rick P
2023-02-13  6:08     ` Juergen Gross
2023-02-13  1:08   ` Michael Kelley (LINUX)
2023-02-13  6:35     ` Juergen Gross
2023-02-15 13:40     ` Juergen Gross
2023-02-15 19:38       ` Michael Kelley (LINUX)
2023-02-16  5:22         ` Juergen Gross
2023-02-09  7:22 ` [PATCH v2 8/8] x86/mtrr: drop sanity check in mtrr_type_lookup_fixed() Juergen Gross
2023-02-11  0:06 ` [PATCH v2 0/8] x86/mtrr: fix handling with PAT but without MTRR Edgecombe, Rick P
2023-02-13  6:12   ` Juergen Gross
2023-02-13 18:21     ` Edgecombe, Rick P
2023-02-15  8:25       ` Juergen Gross
2023-02-15 23:22         ` Linus Torvalds
2023-02-16  5:35           ` 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=20230209072220.6836-3-jgross@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=lists@nerdbynature.de \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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