From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCHv3] x86/mce: Look in genpool instead of mcelog.entry[] for pending error records
Date: Tue, 26 Apr 2016 20:11:14 +0200 [thread overview]
Message-ID: <20160426181114.GH17845@pd.tnic> (raw)
In-Reply-To: <0a9f1fc6b1626ad2b9cb6f1a7c621249b39d1a63.1460058327.git.tony.luck@intel.com>
On Fri, Apr 08, 2016 at 10:00:50AM -0700, Tony Luck wrote:
> Couple of issues here:
> 1) MCE_LOG_LEN is only 32 - so we may have more pending records than will
> fit in the buffer on high core count cpus
> 2) During a panic we may have a lot of duplicate records because multiple
> logical cpus may have seen and logged the same error because some
> banks are shared.
>
> Switch to using the genpool to look for the pending records. Squeeze
> out duplicated records.
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
> v3: Make mce_cmp() behave like other *cmp() functions: return 0 for equality (Boris)
>
> v2: Better names and code layout (Boris)
> Revised commments on mce record comparisons (Ashok)
>
> arch/x86/kernel/cpu/mcheck/mce-genpool.c | 46 +++++++++++++++++++++++++++++++
> arch/x86/kernel/cpu/mcheck/mce-internal.h | 15 ++++++++++
> arch/x86/kernel/cpu/mcheck/mce.c | 21 ++++++--------
> 3 files changed, 70 insertions(+), 12 deletions(-)
Applied, thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2016-04-26 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 18:35 [PATCH] x86/mce: Look in genpool instead of mcelog.entry[] for pending error records Tony Luck
2016-03-31 8:46 ` Borislav Petkov
[not found] ` <b5198c79fc527cc63d858087bd20fd81b1c4011a.1460046517.git.tony.luck@intel.com>
2016-04-07 17:03 ` [PATCHv2] " Borislav Petkov
[not found] ` <0a9f1fc6b1626ad2b9cb6f1a7c621249b39d1a63.1460058327.git.tony.luck@intel.com>
2016-04-26 18:11 ` Borislav Petkov [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=20160426181114.GH17845@pd.tnic \
--to=bp@alien8.de \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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