public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: [PATCHv2] x86/mce: Look in genpool instead of mcelog.entry[] for pending error records
Date: Thu, 7 Apr 2016 19:03:26 +0200	[thread overview]
Message-ID: <20160407170326.GK3735@pd.tnic> (raw)
In-Reply-To: <b5198c79fc527cc63d858087bd20fd81b1c4011a.1460046517.git.tony.luck@intel.com>

On Thu, Apr 07, 2016 at 09:34:06AM -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>
> ---
> 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(-)
> 
> diff --git a/arch/x86/kernel/cpu/mcheck/mce-genpool.c b/arch/x86/kernel/cpu/mcheck/mce-genpool.c
> index 0a850100c594..c43050b91d6d 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce-genpool.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce-genpool.c
> @@ -26,6 +26,52 @@ static struct gen_pool *mce_evt_pool;
>  static LLIST_HEAD(mce_event_llist);
>  static char gen_pool_buf[MCE_POOLSZ];
>  
> +/*
> + * Compare the record "t" with each of the records on list "l" to see if
> + * a functionally equivalent one is present in the list.

functionally?

> + */
> +static bool is_duplicate_mce_record(struct mce_evt_llist *t, struct mce_evt_llist *l)
> +{
> +	struct mce_evt_llist *node;
> +	struct mce *m1, *m2;
> +
> +	m1 = &t->mce;
> +
> +	llist_for_each_entry(node, &l->llnode, llnode) {
> +		m2 = &node->mce;
> +
> +		if (mce_cmp(m1, m2))

Sorry for nitpicking but isn't it usually the case that a
_cmp()-something function should return 0 when both things are equal?

I.e., you have:

	if (!strcmp(s1, s2))
		...

I think if we do it this way here too, it'll be very natural. mce_cmp()
would then have to do:

        return !(m1->bank == m2->bank &&
                m1->status == m2->status &&
                m1->addr == m2->addr &&
                m1->misc == m2->misc);

simply.

Hmmm?

Rest looks ok.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  parent reply	other threads:[~2016-04-07 17:03 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     ` Borislav Petkov [this message]
     [not found]       ` <0a9f1fc6b1626ad2b9cb6f1a7c621249b39d1a63.1460058327.git.tony.luck@intel.com>
2016-04-26 18:11         ` [PATCHv3] " Borislav Petkov

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=20160407170326.GK3735@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