diff options
| author | Matthew Wilcox (Oracle) <[email protected]> | 2024-03-26 17:10:23 +0000 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-04-25 20:56:13 -0700 |
| commit | f4b6680973d5f94845ca34dcc7126a769d48c0d4 (patch) | |
| tree | aa6b7a63bd48b12b11282ae61929542a6681368b /tools/perf/scripts/python/bin/task-analyzer-record | |
| parent | f002882ca369aba3eece5006f3346ccf75ede7c5 (diff) | |
sh: remove use of PG_arch_1 on individual pages
Patch series "Various page->flags cleanups".
The first two patches are bug fixes, although I'm not sure that either
architecture will have noticed. There aren't a lot of uses of page->flags
left! The big build-up here is to reworking stable_page_flags(), which
will definitely be a user-visible change. I think a welcome one, given
the special case we had to spread the Slab flag into all tail pages.
This patch (of 10):
Since switching to the new page table range API, we do not set the
PG_arch_1 (aka dcache clean) flag on tail pages, only on the folio. Test
it on the folio. Also use page_mapped() instead of page_mapcount() as it
is more efficient.
[[email protected]: fix folio_flags call]
Link: https://lkml.kernel.org/r/[email protected]
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Matthew Wilcox (Oracle) <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/task-analyzer-record')
0 files changed, 0 insertions, 0 deletions