From: Borislav Petkov <bp@alien8.de>
To: "Paoloni, Gabriele" <gabriele.paoloni@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-safety@lists.elisa.tech" <linux-safety@lists.elisa.tech>
Subject: Re: [linux-safety] [PATCH 2/4] x86/mce: move the mce_panic() call and kill_it assignments at the right places
Date: Mon, 23 Nov 2020 18:19:10 +0100 [thread overview]
Message-ID: <20201123171910.GF15044@zn.tnic> (raw)
In-Reply-To: <MN2PR11MB4158162EBECE1AEA80D5EC0288FC0@MN2PR11MB4158.namprd11.prod.outlook.com>
On Mon, Nov 23, 2020 at 05:06:31PM +0000, Paoloni, Gabriele wrote:
> From my understanding no_way_out and kill_it are different in principles:
> no_way_out is telling that an error occurred 'somewhere' in some CPU bank
> that requires the system to panic (e.g. PCC=1); kill_it is saying that the execution
> cannot be restarted where it left for the local CPU and hence we need to find
> an alternative solution as part of the recovery action. In practice it seems to
> me that kill_it is used to replace kill_me_maybe with kill_me_now in case
> the exception happened in user mode.
Bah, I got confused, sorry about that - you're right.
Btw, that kill_it should probably be called "kill_current_task" or so to
make it more clear.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194): https://lists.elisa.tech/g/linux-safety/message/194
Mute This Topic: https://lists.elisa.tech/mt/78342502/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-11-23 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 15:15 [linux-safety] [PATCH 0/4] x86/MCE: some minor fixes Paoloni, Gabriele
2020-11-18 15:15 ` [linux-safety] [PATCH 1/4] x86/mce: do not overwrite no_way_out if mce_end() fails Paoloni, Gabriele
2020-11-20 17:07 ` Borislav Petkov
2020-11-20 17:31 ` Paoloni, Gabriele
2020-11-20 17:33 ` Borislav Petkov
2020-11-23 14:35 ` Borislav Petkov
2020-11-20 17:32 ` Borislav Petkov
2020-11-20 17:35 ` Paoloni, Gabriele
2020-11-18 15:15 ` [linux-safety] [PATCH 2/4] x86/mce: move the mce_panic() call and kill_it assignments at the right places Paoloni, Gabriele
2020-11-23 14:27 ` Borislav Petkov
2020-11-23 17:06 ` Paoloni, Gabriele
2020-11-23 17:19 ` Borislav Petkov [this message]
2020-11-23 17:40 ` Paoloni, Gabriele
2020-11-23 18:07 ` Borislav Petkov
2020-11-18 15:15 ` [linux-safety] [PATCH 3/4] x86/mce: for LMCE panic only if mca_cfg.tolerant < 3 Paoloni, Gabriele
2020-11-18 15:15 ` [linux-safety] [PATCH 4/4] x86/mce: remove redundant call to irq_work_queue() Paoloni, Gabriele
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=20201123171910.GF15044@zn.tnic \
--to=bp@alien8.de \
--cc=gabriele.paoloni@intel.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--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 NNTP newsgroup(s).