From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0 of 1] Kexec alteration
Date: Thu, 6 Dec 2012 15:56:22 +0000 [thread overview]
Message-ID: <patchbomb.1354809382@andrewcoop.uk.xensource.com> (raw)
Hello,
Fixing the root reentrant NMI/MCE issues is quickly turning into a
substantially larger problem than initially thought.
As a result, I have decided to submit the fixes in smaller chunks, in
the hope that they are reviewed and integrated separately. The first
part is changes to the kexec path, from which I am now happy to drop the
RFC tag.
Please scrutinise carefully.
The vague decided plan going forwards is:
* Implement spin_{un,}lock_recursive_irq{save,restore}()
* Audit users of mixed regular/recursive calls on the same spinlock
* Swap recursive spinlocks to be a separate type
* Fix the semantics of console_force_unlock
* Continue audit of NMI and MCE paths, with console semantics fixed
* {Panic,NMI,MCE}-in-progress flags & reentrancy protection
* Ability to specify whether iret should be used on trap exit
* Implement "MCEs never iret, NMIs always iret" policy
The plan for "things I think needs to happen" is:
* Extend spinlock debugging to know about NMI and MCE contexts
* Implement strict ordering constraints for spinlock debugging
The "other things needing investigating" list includes:
* Interaction of paging changes and IDTs while purgatory is changing
processor modes
~Andrew
next reply other threads:[~2012-12-06 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 15:56 Andrew Cooper [this message]
2012-12-06 15:56 ` [PATCH 1 of 1] x86/kexec: Change NMI and MCE handling on kexec path Andrew Cooper
2012-12-06 17:17 ` Mats Petersson
2012-12-07 11:23 ` Jan Beulich
2012-12-06 16:01 ` [PATCH 0 of 1] Kexec alteration Andrew Cooper
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=patchbomb.1354809382@andrewcoop.uk.xensource.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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 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.