Skip to content

Use global pages with PTI

Dave Hansen lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3x86/mm: factor out conditional pageattr PTE bit setting codearch/x86/mm/pageattr.c+20 -450 replies
2/3x86/mm: introduce __PAGE_KERNEL_GLOBALarch/x86/include/asm/pgtable_types.h arch/x86/mm/init.c arch/x86/mm/pageattr.c+14 -120 replies
3/3x86/pti: enable global pages for shared areasarch/x86/mm/cpu_entry_area.c arch/x86/mm/pti.c+15 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] Use global pages with PTI

The later verions of the KAISER pathces (pre-PTI) allowed the user/kernel shared areas to be GLOBAL. The thought was that this would reduce the TLB overhead of keeping two copies of these mappings.

During the switch over to PTI, we seem to have lost our ability to have GLOBAL mappings. This adds them back.

Did we have some reason for leaving out global pages entirely? We _should_ have all the TLB flushing mechanics in place to handle these already since all of our kernel mapping changes have to know how to flush global pages regardless.

Cc Andy Lutomirski <[email protected]>
Cc Linus Torvalds <[email protected]>
Cc Kees Cook <[email protected]>
Cc Hugh Dickins <[email protected]>
Cc Juergen Gross <[email protected]>