From: Dave Hansen <[email protected]>

The comment says it all here.  The problem here is that the
X86_CR4_PGE bit affects all PCIDs in a way that is totally
obscure.

This makes it easier for someone to grep for PCID-related code
and documents the expected hardware behavior.

Signed-off-by: Dave Hansen <[email protected]>
Cc: Moritz Lipp <[email protected]>
Cc: Daniel Gruss <[email protected]>
Cc: Michael Schwarz <[email protected]>
Cc: Richard Fellner <[email protected]>
Cc: Andy Lutomirski <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Kees Cook <[email protected]>
Cc: Hugh Dickins <[email protected]>
Cc: [email protected]
---

 b/arch/x86/include/asm/tlbflush.h |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff -puN arch/x86/include/asm/tlbflush.h~kaiser-prep-document-cr4-pge-behavior 
arch/x86/include/asm/tlbflush.h
--- a/arch/x86/include/asm/tlbflush.h~kaiser-prep-document-cr4-pge-behavior     
2017-11-10 11:22:06.079244957 -0800
+++ b/arch/x86/include/asm/tlbflush.h   2017-11-10 11:22:06.082244957 -0800
@@ -257,10 +257,12 @@ static inline void __native_flush_tlb_gl
        WARN_ON_ONCE(!(cr4 & X86_CR4_PGE));
 
        /*
-        * Architecturally, any _change_ to X86_CR4_PGE will fully flush the
-        * TLB of all entries including all entries in all PCIDs and all
-        * global pages.  Make sure that we _change_ the bit, regardless of
+        * Architecturally, any _change_ to X86_CR4_PGE will fully flush
+        * all entries.  Make sure that we _change_ the bit, regardless of
         * whether we had X86_CR4_PGE set in the first place.
+        *
+        * Note that just toggling PGE *also* flushes all entries from all
+        * PCIDs, regardless of the state of X86_CR4_PCIDE.
         */
        native_write_cr4(cr4 ^ X86_CR4_PGE);
 
_

Reply via email to