From: "tip-bot2 for Juergen Gross" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cpu] x86/mtrr: Make message for disabled MTRRs more descriptive
Date: Mon, 05 Dec 2022 10:16:43 -0000 [thread overview]
Message-ID: <167023540385.4906.769505168034496699.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20221205080433.16643-3-jgross@suse.com>
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: 7882b69eb6cdf6288a89d831d95c8547400a8b4d
Gitweb: https://git.kernel.org/tip/7882b69eb6cdf6288a89d831d95c8547400a8b4d
Author: Juergen Gross <jgross@suse.com>
AuthorDate: Mon, 05 Dec 2022 09:04:33 +01:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Mon, 05 Dec 2022 11:08:25 +01:00
x86/mtrr: Make message for disabled MTRRs more descriptive
Instead of just saying "Disabled" when MTRRs are disabled for any
reason, tell what is disabled and why.
Signed-off-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20221205080433.16643-3-jgross@suse.com
---
arch/x86/kernel/cpu/mtrr/mtrr.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/mtrr/mtrr.c b/arch/x86/kernel/cpu/mtrr/mtrr.c
index 6432abc..783f321 100644
--- a/arch/x86/kernel/cpu/mtrr/mtrr.c
+++ b/arch/x86/kernel/cpu/mtrr/mtrr.c
@@ -629,6 +629,7 @@ int __initdata changed_by_mtrr_cleanup;
*/
void __init mtrr_bp_init(void)
{
+ const char *why = "(not available)";
u32 phys_addr;
phys_addr = 32;
@@ -705,12 +706,13 @@ void __init mtrr_bp_init(void)
changed_by_mtrr_cleanup = mtrr_cleanup(phys_addr);
} else {
mtrr_if = NULL;
+ why = "by BIOS";
}
}
}
if (!mtrr_enabled())
- pr_info("Disabled\n");
+ pr_info("MTRRs disabled %s\n", why);
}
/**
next prev parent reply other threads:[~2022-12-05 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:04 [PATCH 0/2] x86: fixes for MTRR/PAT decoupling Juergen Gross
2022-12-05 8:04 ` [PATCH 1/2] x86/pat: fix TDX guest PAT initialization Juergen Gross
2022-12-05 10:16 ` [tip: x86/cpu] x86/pat: Handle " tip-bot2 for Juergen Gross
2022-12-05 12:26 ` [PATCH 1/2] x86/pat: fix " kirill
2022-12-05 8:04 ` [PATCH 2/2] x86/mtrr: make message for disabled MTRRs more descriptive Juergen Gross
2022-12-05 10:16 ` tip-bot2 for Juergen Gross [this message]
2022-12-05 12:26 ` kirill
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=167023540385.4906.769505168034496699.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.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
all inboxes | Powered by JetHome®