From: Filippo Sironi <sironi@amazon.de>
To: <linux-kernel@vger.kernel.org>
Cc: <sironi@amazon.de>, <tony.luck@intel.com>, <bp@alien8.de>,
<tglx@linutronix.de>, <mingo@redhat.com>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<linux-edac@vger.kernel.org>
Subject: [PATCH] x86/mce: Increase the size of the MCE pool from 2 to 8 pages
Date: Wed, 11 Oct 2023 16:33:20 +0000 [thread overview]
Message-ID: <20231011163320.79732-1-sironi@amazon.de> (raw)
On some of our large servers and some of our most sorry servers ( :) ),
we're seeing the kernel reporting the warning in mce_gen_pool_add: "MCE
records pool full!". Let's increase the amount of memory that we use to
store the MCE records from 2 to 8 pages to prevent this from happening
and be able to collect useful information.
Signed-off-by: Filippo Sironi <sironi@amazon.de>
---
arch/x86/kernel/cpu/mce/genpool.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/mce/genpool.c b/arch/x86/kernel/cpu/mce/genpool.c
index fbe8b61c3413..870dcb7011cd 100644
--- a/arch/x86/kernel/cpu/mce/genpool.c
+++ b/arch/x86/kernel/cpu/mce/genpool.c
@@ -17,9 +17,9 @@
*
* This memory pool is only to be used to save MCE records in MCE context.
* MCE events are rare, so a fixed size memory pool should be enough. Use
- * 2 pages to save MCE events for now (~80 MCE records at most).
+ * 8 pages to save MCE events for now (~320 MCE records at most).
*/
-#define MCE_POOLSZ (2 * PAGE_SIZE)
+#define MCE_POOLSZ (8 * PAGE_SIZE)
static struct gen_pool *mce_evt_pool;
static LLIST_HEAD(mce_event_llist);
--
2.33.0
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next reply other threads:[~2023-10-11 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:33 Filippo Sironi [this message]
2023-10-11 17:32 ` [PATCH] x86/mce: Increase the size of the MCE pool from 2 to 8 pages Dave Hansen
2023-10-12 11:46 ` Sironi, Filippo
2023-10-12 11:52 ` Borislav Petkov
2023-10-12 15:49 ` Dave Hansen
2023-10-16 14:14 ` Yazen Ghannam
2023-10-16 14:24 ` Dave Hansen
2023-10-16 14:40 ` Borislav Petkov
2023-10-16 14:47 ` Yazen Ghannam
2023-10-16 16:14 ` Luck, Tony
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=20231011163320.79732-1-sironi@amazon.de \
--to=sironi@amazon.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).