From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Kujau <lists@nerdbynature.de>,
Juergen Gross <jgross@suse.com>,
Michael Kelley <mikelley@microsoft.com>,
linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: External USB disks not recognized with v6.1.8 when using Xen
Date: Sun, 5 Feb 2023 14:20:14 +0100 [thread overview]
Message-ID: <Y9+tDmLAlqg37TS+@zn.tnic> (raw)
In-Reply-To: <CAHk-=wg1yXaX+Ut4uctf7x1WrZ4WW9hjSCr1VACwZtkZT9frFw@mail.gmail.com>
On Thu, Feb 02, 2023 at 12:24:30PM -0800, Linus Torvalds wrote:
> So I think that commit should be reverted as broken, and then people
> should *maybe* look at something like this (intentionally whitespace
> damaged, and people should *really* think about what the
> MTRR_TYPE_INVALID case should be - returning UC- is probably what is
> closest to "this is what the hardware does",
Yes, it is actually even documented that by default, all memory is UC-
if MTRRs are disabled.
> but maybe doesn't make sense for the largepage case, which might as
> well just always use largepages in that case?)
See below. I think it should be this way but I might be missing an
angle...
---
diff --git a/arch/x86/include/asm/mtrr.h b/arch/x86/include/asm/mtrr.h
index f0eeaf6e5f5f..4061f1e8d34c 100644
--- a/arch/x86/include/asm/mtrr.h
+++ b/arch/x86/include/asm/mtrr.h
@@ -53,7 +53,8 @@ static inline u8 mtrr_type_lookup(u64 addr, u64 end, u8 *uniform)
/*
* Return no-MTRRs:
*/
- return MTRR_TYPE_INVALID;
+ *uniform = 1;
+ return MTRR_TYPE_UNCACHABLE;
}
#define mtrr_save_fixed_ranges(arg) do {} while (0)
#define mtrr_save_state() do {} while (0)
diff --git a/arch/x86/kernel/cpu/mtrr/generic.c b/arch/x86/kernel/cpu/mtrr/generic.c
index ee09d359e08f..2a1ed63d2b24 100644
--- a/arch/x86/kernel/cpu/mtrr/generic.c
+++ b/arch/x86/kernel/cpu/mtrr/generic.c
@@ -255,17 +255,25 @@ static u8 mtrr_type_lookup_variable(u64 start, u64 end, u64 *partial_end,
u8 mtrr_type_lookup(u64 start, u64 end, u8 *uniform)
{
u8 type, prev_type, is_uniform = 1, dummy;
- int repeat;
u64 partial_end;
+ int repeat;
/* Make end inclusive instead of exclusive */
end--;
+ /*
+ * UC- by default because " [i]f the MTRRs are disabled in implementations
+ * that support the MTRR mechanism, the default memory type is set to
+ * uncacheable (UC)".
+ */
+ type = MTRR_TYPE_UNCACHABLE;
+
if (!mtrr_state_set)
- return MTRR_TYPE_INVALID;
+ goto out;
+ type = mtrr_state.def_type;
if (!(mtrr_state.enabled & MTRR_STATE_MTRR_ENABLED))
- return MTRR_TYPE_INVALID;
+ goto out;
/*
* Look up the fixed ranges first, which take priority over
diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c
index e4f499eb0f29..ed914bc95345 100644
--- a/arch/x86/mm/pgtable.c
+++ b/arch/x86/mm/pgtable.c
@@ -721,8 +721,9 @@ int pud_set_huge(pud_t *pud, phys_addr_t addr, pgprot_t prot)
u8 mtrr, uniform;
mtrr = mtrr_type_lookup(addr, addr + PUD_SIZE, &uniform);
- if ((mtrr != MTRR_TYPE_INVALID) && (!uniform) &&
- (mtrr != MTRR_TYPE_WRBACK))
+ if (mtrr != MTRR_TYPE_UNCACHABLE &&
+ mtrr != MTRR_TYPE_WRBACK &&
+ !uniform)
return 0;
/* Bail out if we are we on a populated non-leaf entry: */
@@ -748,8 +749,9 @@ int pmd_set_huge(pmd_t *pmd, phys_addr_t addr, pgprot_t prot)
u8 mtrr, uniform;
mtrr = mtrr_type_lookup(addr, addr + PMD_SIZE, &uniform);
- if ((mtrr != MTRR_TYPE_INVALID) && (!uniform) &&
- (mtrr != MTRR_TYPE_WRBACK)) {
+ if (mtrr != MTRR_TYPE_UNCACHABLE &&
+ mtrr != MTRR_TYPE_WRBACK &&
+ !uniform) {
pr_warn_once("%s: Cannot satisfy [mem %#010llx-%#010llx] with a huge-page mapping due to MTRR override.\n",
__func__, addr, addr + PMD_SIZE);
return 0;
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-02-05 13:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 3:46 External USB disks not recognized with v6.1.8 when using Xen Christian Kujau
2023-01-30 5:17 ` Greg KH
2023-01-30 12:01 ` Linux kernel regression tracking (#adding)
2023-01-31 22:50 ` Christian Kujau
2023-02-01 8:14 ` Juergen Gross
2023-02-01 9:37 ` Christian Kujau
2023-02-02 11:38 ` Christian Kujau
2023-02-02 20:24 ` Linus Torvalds
2023-02-03 16:50 ` Christian Kujau
2023-02-03 17:29 ` Christian Kujau
2023-02-05 13:20 ` Borislav Petkov [this message]
2023-02-05 17:17 ` Christian Kujau
2023-02-05 20:21 ` Linus Torvalds
2023-02-06 6:33 ` Juergen Gross
2023-02-06 9:54 ` Juergen Gross
2023-02-06 9:43 ` Borislav Petkov
2023-02-05 10:40 ` Linux kernel regression tracking (#update)
2023-02-14 9:35 ` [tip: x86/urgent] x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for MTRR disabled case") tip-bot2 for Juergen Gross
2023-02-18 9:47 ` Christian Kujau
2023-02-18 9:59 ` Borislav Petkov
2023-05-08 13:41 ` [tip: x86/cleanups] Documentation/process: Explain when tip branches get merged into mainline tip-bot2 for Christian Kujau
2023-05-15 15:28 ` tip-bot2 for Christian Kujau
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=Y9+tDmLAlqg37TS+@zn.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mikelley@microsoft.com \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).