summaryrefslogtreecommitdiff
path: root/arch/x86/kernel/time.c
diff options
context:
space:
mode:
authorDave Hansen <dave.hansen@linux.intel.com>2018-10-13 02:21:18 +0300
committerThomas Gleixner <tglx@linutronix.de>2018-10-14 12:11:22 +0300
commit16561f27f94e6193ee8f5b9b74801e1668c86efc (patch)
tree044d2cfaa1e2fe08feb08946233af179b05b2643 /arch/x86/kernel/time.c
parentb59167ac7bafd804c91e49ad53c6d33a7394d4c8 (diff)
downloadlinux-16561f27f94e6193ee8f5b9b74801e1668c86efc.tar.xz
x86/entry: Add some paranoid entry/exit CR3 handling comments
Andi Kleen was just asking me about the NMI CR3 handling and why we restore it unconditionally. I was *sure* we had documented it well. We did not. Add some documentation. We have common entry code where the CR3 value is stashed, but three places in two big code paths where we restore it. I put bulk of the comments in this common path and then refer to it from the other spots. Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: luto@kernel.org Cc: bp@alien8.de Cc: "H. Peter Anvin" <hpa@zytor.come Cc: Andy Lutomirski <luto@kernel.org> Cc: Borislav Petkov <bp@alien8.de> Link: https://lkml.kernel.org/r/20181012232118.3EAAE77B@viggo.jf.intel.com
Diffstat (limited to 'arch/x86/kernel/time.c')
0 files changed, 0 insertions, 0 deletions