From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: James Morse <james.morse@arm.com>,
Waiman Long <longman@redhat.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
SRINIVAS <srinivas.eeda@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Question about qspinlock nest
Date: Fri, 18 Jan 2019 11:24:27 +0100 [thread overview]
Message-ID: <20190118102427.GA622@zn.tnic> (raw)
In-Reply-To: <20190118100229.GB27931@hirez.programming.kicks-ass.net>
On Fri, Jan 18, 2019 at 11:02:29AM +0100, Peter Zijlstra wrote:
> Well, x86 too has multiple non-maskable vectors, and afaik only the
> actual NMI vector is covered in tricky. But our MCE vector is
> non-maskable too (and I have vague memories of there being more).
>
> Boris, Rostedt, WTH happens if our MCE code goes and hits a #BP ? (not
> unlikely with this proliferation of self-modifying code)
>
> Anyway, the idea is that they can indeed not interrupt themselves, but I
> would not be surprised if the whole MCE thing is riddled with fail (on
> x86).
As we talked on IRC: we'll apply a mixture of "So don't do that
then!" hints i.e., kprobing MCE code etc, and fix the issues like the
schedule_work() invocation.
In general, I'd like to make/keep the #MC handler as simple and
as idiot-proof as possible.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-18 10:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 8:02 Question about qspinlock nest Zhenzhong Duan
2019-01-10 14:43 ` Waiman Long
2019-01-10 18:25 ` James Morse
2019-01-10 19:23 ` Waiman Long
2019-01-10 20:12 ` Peter Zijlstra
2019-01-11 18:32 ` James Morse
2019-01-14 13:16 ` Peter Zijlstra
2019-01-14 13:54 ` James Morse
2019-01-14 21:07 ` Waiman Long
2019-01-18 10:02 ` Peter Zijlstra
2019-01-18 10:24 ` Borislav Petkov [this message]
2019-01-18 14:50 ` Waiman Long
2019-01-18 20:06 ` Peter Zijlstra
2019-01-18 21:30 ` Waiman Long
[not found] ` <2eca6f60-3e8b-a389-27cb-8adbd9676607@oracle.com>
2019-01-11 9:16 ` Peter Zijlstra
2019-01-11 17:36 ` Borislav Petkov
2019-01-11 16:59 ` Waiman Long
2019-01-10 20:03 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2019-01-14 9:25 Zhenzhong Duan
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=20190118102427.GA622@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srinivas.eeda@oracle.com \
--cc=zhenzhong.duan@oracle.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.