mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <linux-kernel@vger.kernel.org>
Subject: x86: NMI vs. MCE handling
Date: Fri, 20 Aug 2004 17:41:22 +0200	[thread overview]
Message-ID: <s12629a3.088@emea1-mh.id2.novell.com> (raw)

Currently, care is being taken to deal with the potential of an NMI
being signalled at the very moment when the debug fault is correcting
the stack for the sysenter path, or when in at the stack pointer load in
the sysenter path itself. The same care, however, is not taken in the
MCE code path, and since I'd consider this equally important (especially
when the event is correctable) I wonder whether this is an oversight or
I'm misunderstanding something.

Thanks for a clarification,
Jan

                 reply	other threads:[~2004-08-20 15:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=s12629a3.088@emea1-mh.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®