diff options
author | Huang Ying <[email protected]> | 2018-04-20 14:55:38 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2018-04-20 17:18:35 -0700 |
commit | 88c28f2469151b031f8cea9b28ed5be1b74a4172 (patch) | |
tree | 267a1a70a86b441e1a7131996c0447acb5b8198e /tools/perf/scripts/python/bin/export-to-postgresql-report | |
parent | 8f175cf5c99dc0e3add2aac0ea1cd54e0f9ca87d (diff) |
mm, pagemap: fix swap offset value for PMD migration entry
The swap offset reported by /proc/<pid>/pagemap may be not correct for
PMD migration entries. If addr passed into pagemap_pmd_range() isn't
aligned with PMD start address, the swap offset reported doesn't
reflect this. And in the loop to report information of each sub-page,
the swap offset isn't increased accordingly as that for PFN.
This may happen after opening /proc/<pid>/pagemap and seeking to a page
whose address doesn't align with a PMD start address. I have verified
this with a simple test program.
BTW: migration swap entries have PFN information, do we need to restrict
whether to show them?
[[email protected]: fix typo, per Huang, Ying]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: "Huang, Ying" <[email protected]>
Cc: Michal Hocko <[email protected]>
Cc: "Kirill A. Shutemov" <[email protected]>
Cc: Andrei Vagin <[email protected]>
Cc: Dan Williams <[email protected]>
Cc: "Jerome Glisse" <[email protected]>
Cc: Daniel Colascione <[email protected]>
Cc: Zi Yan <[email protected]>
Cc: Naoya Horiguchi <[email protected]>
Cc: Alexey Dobriyan <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions