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>,
<yaoaili@kingsoft.com>
Subject: Re: [PATCH v2] Dump cper error table in mce_panic
Date: Tue, 23 Feb 2021 17:18:09 +0800 [thread overview]
Message-ID: <20210223171809.7df62b08@alex-virtual-machine> (raw)
In-Reply-To: <e9645a3ff93e46d4aabdf7dd45bfc4d7@intel.com>
On Thu, 28 Jan 2021 17:22:30 +0000
"Luck, Tony" <tony.luck@intel.com> wrote:
>
> Getting a full memory dump after a machine check generally isn't
> all that useful anyway. The problem was (almost certainly) h/w, so
> not much benefit in decoding the dump to find which code was running
> when the h/w signalled.
The purpose I try to collect the coredump log is not to identify what the backtrace
is, I want to confirm if this panic is really needed, there are too many panics in production
environment with MCA Recovery Enabled, and no kernel log is collected, in some way we can't find
the benifits from MCA recovery, And for purley this feature cost too much.
And the unexpected NMI for fatal memory error is not the right way to get work done.
This is not right, and shouldn't happen.
> A second bite at getting the error logs from the death of the first
> kernel is worth it though.
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.
Thanks
Aili Yao
next prev parent reply other threads:[~2021-02-23 9:19 UTC|newest]
Thread overview: 16+ 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-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 [this message]
2021-02-23 19:32 ` Luck, Tony
2021-02-24 9:56 ` Aili Yao
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=20210223171809.7df62b08@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 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).