Skip to content

x86/mm: fix cpu stuck issue in __change_page_attr_set_clr

Bin Yang lkml 3 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest5 patches 18 repliesIn review
  2. v21 patch 2 repliesSuperseded
  3. v11 patch 13 repliesSuperseded

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5x86/mm: avoid redundant checking if pgprot has no changearch/x86/mm/pageattr.c+16 -85 replies
2/5x86/mm: avoid static_protection() checking if not whole large page attr changearch/x86/mm/pageattr.c+16 -190 replies
3/5x86/mm: add help function to check specific protection flags in rangearch/x86/mm/pageattr.c+27 -92 replies
4/5x86/mm: optimize static_protection() by using overlap()arch/x86/mm/pageattr.c+33 -176 replies
5/5x86/mm: add WARN_ON_ONCE() for wrong large page mappingarch/x86/mm/pageattr.c+7 -15 replies

Reviews trailers per patch

None of the 5 patches has a Reviewed-by or Acked-by.

PatchThomas Gleixner
1/5
2/5
3/5
4/5
5/5Inspired-by

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v3 thread

Cover letter [PATCH v3 0/5] x86/mm: fix cpu stuck issue in __change_page_attr_set_clr

One problem is found when optimizing the x86 kernel boot time, that sometimes the free_initmem() will take about 600ms, which is way too much for fast boot.

When changing a 4K page attr inside the large page range, __change_page_attr() will call try_preserve_large_page() to decide to split the big page or not. And try_preserve_large_page() will call static_protections() to check all 4K pages inside the large page range one by one.

free_initmem() <-- free N pages
free_init_pages()

    set_memory_rw()
      change_page_attr_set()
        change_page_attr_set_clr()
	  __change_page_attr_set_clr()
	    __change_page_attr() <-- loop N times
	      try_preserve_large_page()
                static_protections() <-- worst case: loop (1G/4K = 262144) * N times

The problem is, most of the 256K * N times of call of static_proetections() is _not_ necessary at all, as pointed out by Thomas Gleixner :

"The current code does the static_protection() check loop _before_ checking:

1) Whether the new and the old pgprot are the same

2) Whether the address range which needs to be changed is aligned to and covers the full large mapping

It does the static_protections() loop before #1 and #2 which can be optimized."

The static_protections() check loop can be optimized to check for overlapping ranges and then check explicitly for those without any looping.

Here are 5 patches for these optimizations:

Patch 1: check whether new pgprot is same as old pgprot first to avoid
unnecessary static_protection() checking.

Patch 2: check whether it is whole large page attr change first to avoid
unnecessary static_protection() checking.

Patch 3: add help function to check specific protection flags in range

Patch 4: Optimize the static_protection() by using overlap() check instead
of within()

Patch 5: Add a check for catching a case where the existing mapping is wrong
already

The approach and some of the comments came from Thomas's email example for how to do this. Thanks again for Thomas's kind help.

Thanks,
Bin

Bin Yang (5):
x86/mm: avoid redundant checking if pgprot has no change x86/mm: avoid static_protection() checking if not whole large page
attr change
x86/mm: add help function to check specific protection flags in range x86/mm: optimize static_protection() by using overlap() x86/mm: add WARN_ON_ONCE() for wrong large page mapping

 arch/x86/mm/pageattr.c | 127 +++++++++++++++++++++++++++++++++----------------
 1 file changed, 86 insertions(+), 41 deletions(-)
Signature · 1 line
2.7.4