diff options
| author | Michal Hocko <[email protected]> | 2011-05-24 17:11:44 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2011-05-25 08:39:12 -0700 |
| commit | d05f3169c0fbca16132ec7c2be71685c6de638b5 (patch) | |
| tree | 37d82004869fa4e530617883f12cab7538dbd4a6 /tools/perf/scripts/python | |
| parent | 248ac0e1943ad1796393d281b096184719eb3f97 (diff) | |
mm: make expand_downwards() symmetrical with expand_upwards()
Currently we have expand_upwards exported while expand_downwards is
accessible only via expand_stack or expand_stack_downwards.
check_stack_guard_page is a nice example of the asymmetry. It uses
expand_stack for VM_GROWSDOWN while expand_upwards is called for
VM_GROWSUP case.
Let's clean this up by exporting both functions and make those names
consistent. Let's use expand_{upwards,downwards} because expanding
doesn't always involve stack manipulation (an example is
ia64_do_page_fault which uses expand_upwards for registers backing store
expansion). expand_downwards has to be defined for both
CONFIG_STACK_GROWS{UP,DOWN} because get_arg_page calls the downwards
version in the early process initialization phase for growsup
configuration.
Signed-off-by: Michal Hocko <[email protected]>
Acked-by: Hugh Dickins <[email protected]>
Cc: James Bottomley <[email protected]>
Cc: "Luck, Tony" <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions