From: Aili Yao <yaoaili@kingsoft.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"lenb@kernel.org" <lenb@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"yangfeng1@kingsoft.com" <yangfeng1@kingsoft.com>
Subject: Re: [PATCH v2] Dump cper error table in mce_panic
Date: Wed, 24 Feb 2021 17:56:32 +0800 [thread overview]
Message-ID: <20210224175632.5d99abcc@alex-virtual-machine> (raw)
In-Reply-To: <434eba7a568a4b9f8eb7ee11a5c8b04f@intel.com>
On Tue, 23 Feb 2021 19:32:37 +0000
"Luck, Tony" <tony.luck@intel.com> wrote:
> > I am not smart enough to get the point. I have paid a lot of time for this patch,
> > I need an result even it doesn't work. so i like the reply like this:
> >
> > 1. this patch is meaningless, and should be rejected.
> > 2. this issue is real, but we need other methond, not this patch.
> > 3. the patch need to improve.
>
> I don't want to say that the patch is meaningless ... it may be useful to you
> in your environment to help sort out machine checks due to h/w issues vs.
> programming errors in the machine check recovery code.
>
> But I don't think it is generally useful in the upstream code.
Got it.
Another thing I want to say is that when mca_cfg.tolerant is set to 3, this NMI handling will
also panic the system in some case, but it seems there is not a big influence though.
Thanks
Aili Yao
prev parent reply other threads:[~2021-02-24 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:50 [PATCH] Dump cper error table in mce_panic yaoaili126
2020-11-04 10:16 ` kernel test robot
2020-11-04 10:16 ` kernel test robot
2020-11-06 19:35 ` James Morse
2020-11-18 3:12 ` Aili Yao
2020-11-17 9:58 ` [PATCH v2] " Aili Yao
2020-11-18 12:45 ` Borislav Petkov
2020-11-19 5:40 ` Aili Yao
2020-11-19 17:45 ` Borislav Petkov
2020-11-20 3:40 ` Aili Yao
2020-11-20 9:22 ` Aili Yao
2020-11-20 10:24 ` Borislav Petkov
2021-01-28 12:01 ` Aili Yao
2021-01-28 17:22 ` Luck, Tony
2021-02-23 9:18 ` Aili Yao
2021-02-23 19:32 ` Luck, Tony
2021-02-24 9:56 ` Aili Yao [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=20210224175632.5d99abcc@alex-virtual-machine \
--to=yaoaili@kingsoft.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=yangfeng1@kingsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.