From: "tip-bot2 for John Allen" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: John Allen <john.allen@amd.com>, Borislav Petkov <bp@suse.de>,
stable@vger.kernel.org, #@tip-bot2.tec.linutronix.de,
"v4.14.."@tip-bot2.tec.linutronix.de, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/urgent] x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE
Date: Tue, 14 Apr 2020 15:46:21 -0000 [thread overview]
Message-ID: <158687918159.28353.7726188053950798556.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200409152931.GA685273@mojo.amd.com>
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: bdf89df3c54518eed879d8fac7577fcfb220c67e
Gitweb: https://git.kernel.org/tip/bdf89df3c54518eed879d8fac7577fcfb220c67e
Author: John Allen <john.allen@amd.com>
AuthorDate: Thu, 09 Apr 2020 10:34:29 -05:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Tue, 14 Apr 2020 17:34:46 +02:00
x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE
Future AMD CPUs will have microcode patches that exceed the default 4K
patch size. Raise our limit.
Signed-off-by: John Allen <john.allen@amd.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Cc: stable@vger.kernel.org # v4.14..
Link: https://lkml.kernel.org/r/20200409152931.GA685273@mojo.amd.com
---
arch/x86/include/asm/microcode_amd.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/microcode_amd.h b/arch/x86/include/asm/microcode_amd.h
index 6685e12..7063b5a 100644
--- a/arch/x86/include/asm/microcode_amd.h
+++ b/arch/x86/include/asm/microcode_amd.h
@@ -41,7 +41,7 @@ struct microcode_amd {
unsigned int mpb[0];
};
-#define PATCH_MAX_SIZE PAGE_SIZE
+#define PATCH_MAX_SIZE (3 * PAGE_SIZE)
#ifdef CONFIG_MICROCODE_AMD
extern void __init load_ucode_amd_bsp(unsigned int family);
prev parent reply other threads:[~2020-04-14 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 15:34 [PATCH] x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE John Allen
2020-04-14 15:46 ` tip-bot2 for John Allen [this message]
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=158687918159.28353.7726188053950798556.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc="v4.14.."@tip-bot2.tec.linutronix.de \
--cc=#@tip-bot2.tec.linutronix.de \
--cc=bp@suse.de \
--cc=john.allen@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).