x86/mm: Remove the redundant conditional check
Subsystems (3)
PATCH v2 1/1 x86/mm: Remove the redundant conditional check
In commit f70029bbaacb ("mm, memory_hotplug: drop CONFIG_MOVABLE_NODE"), the dependency on CONFIG_MOVABLE_NODE was removed for N_MEMORY. Before commit f70029bbaacb, CONFIG_HIGHMEM && !CONFIG_MOVABLE_NODE could make (N_MEMORY == N_NORMAL_MEMORY) be true. After commit f70029bbaacb, N_MEMORY doesn't have any chance to be equal to N_NORMAL_MEMORY. So the conditional check in paging_init() doesn't make sense any more. Let's remove it.
---v1->v2:
Update patch log to make the description clearer per Michal's suggestion.
arch/x86/mm/init_64.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/x86/mm/init_64.c +1 -2
@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }
Signature · 1 line
2.17.2
Quoted 8 lines · Baoquan He
In commit
f70029bbaacb("mm,memory_hotplug: dropCONFIG_MOVABLE_NODE"), the dependency onCONFIG_MOVABLE_NODEwas removed forN_MEMORY. Before commitf70029bbaacb,CONFIG_HIGHMEM&& !CONFIG_MOVABLE_NODE could make (N_MEMORY==N_NORMAL_MEMORY) be true. After commitf70029bbaacb,N_MEMORYdoesn't have any chance to be equal toN_NORMAL_MEMORY. So the conditional check inpaging_init()doesn't make sense any more. Let's remove it.Signed-off-by Baoquan He <[email protected]>
Thanks!
Quoted 24 lines
---
v1->v2:
Update patch log to make the description clearer per Michal's suggestion.arch/x86/mm/init_64.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)arch/x86/mm/init_64.c +1
-2@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }Signature · 1 line
2.17.2
Signature · 2 lines
Michal Hocko SUSE Labs
Quoted 8 lines · Baoquan He
In commit
f70029bbaacb("mm,memory_hotplug: dropCONFIG_MOVABLE_NODE"), the dependency onCONFIG_MOVABLE_NODEwas removed forN_MEMORY. Before commitf70029bbaacb,CONFIG_HIGHMEM&& !CONFIG_MOVABLE_NODE could make (N_MEMORY==N_NORMAL_MEMORY) be true. After commitf70029bbaacb,N_MEMORYdoesn't have any chance to be equal toN_NORMAL_MEMORY. So the conditional check inpaging_init()doesn't make sense any more. Let's remove it.Signed-off-by Baoquan He <[email protected]>
The change looks good. While I have one question, we set default value for N_HIGH_MEMORY. Why we don't clear this too?
Quoted 24 lines
---
v1->v2:
Update patch log to make the description clearer per Michal's suggestion.
arch/x86/mm/init_64.c| 3 +--1 file changed, 1 insertion(+), 2 deletions(-)arch/x86/mm/init_64.c +1
-2@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }Signature · 1 line
2.17.2
Signature · 2 lines
Wei Yang Help you, Help me
Quoted 8 lines · Wei Yang
Quoted 7 lines · Baoquan He
In commit
f70029bbaacb("mm,memory_hotplug: dropCONFIG_MOVABLE_NODE"), the dependency onCONFIG_MOVABLE_NODEwas removed forN_MEMORY. Before commitf70029bbaacb,CONFIG_HIGHMEM&& !CONFIG_MOVABLE_NODE could make (N_MEMORY==N_NORMAL_MEMORY) be true. After commitf70029bbaacb,N_MEMORYdoesn't have any chance to be equal toN_NORMAL_MEMORY. So the conditional check inpaging_init()doesn't make sense any more. Let's remove it.
Quoted 4 lines
Quoted 1 line
Signed-off-by Baoquan He <[email protected]>The change looks good. While I have one question, we set default value for
N_HIGH_MEMORY. Why we don't clear this too?
This is for x86_64 only, there's no node_state for N_HIGH_MEMORY.
Quoted 32 lines
Reviewed-by Wei Yang <[email protected]>Quoted 24 lines
---
v1->v2:
Update patch log to make the description clearer per Michal's suggestion.
arch/x86/mm/init_64.c| 3 +--1 file changed, 1 insertion(+), 2 deletions(-)arch/x86/mm/init_64.c +1
-2@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }Signature · 1 line
2.17.2Signature · 2 lines
Wei Yang Help you, Help me
Quoted 9 lines · Baoquan He
Quoted 8 lines · Wei Yang
Quoted 7 lines · Baoquan He
In commit
f70029bbaacb("mm,memory_hotplug: dropCONFIG_MOVABLE_NODE"), the dependency onCONFIG_MOVABLE_NODEwas removed forN_MEMORY. Before commitf70029bbaacb,CONFIG_HIGHMEM&& !CONFIG_MOVABLE_NODE could make (N_MEMORY==N_NORMAL_MEMORY) be true. After commitf70029bbaacb,N_MEMORYdoesn't have any chance to be equal toN_NORMAL_MEMORY. So the conditional check inpaging_init()doesn't make sense any more. Let's remove it.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Signed-off-by Baoquan He <[email protected]>The change looks good. While I have one question, we set default value for
N_HIGH_MEMORY. Why we don't clear this too?This is for
x86_64only, there's nonode_stateforN_HIGH_MEMORY.
Thanks, I see it in arch/x86/Kconfig.
Signature · 2 lines
Wei Yang Help you, Help me
[tip: x86/mm] x86/mm: Remove the now redundant N_MEMORY check
In reply to Baoquan HeThe following commit has been merged into the x86/mm branch of tip:
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: aa61ee7b9ee3cb84c0d3a842b0d17937bf024c46 Gitweb: https://git.kernel.org/tip/aa61ee7b9ee3cb84c0d3a842b0d17937bf024c46 Author: Baoquan He <[email protected]> AuthorDate: Wed, 11 Mar 2020 09:18:23 +08:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Tue, 17 Mar 2020 19:12:39 +01:00
x86/mm: Remove the now redundant N_MEMORY check
In commit
f70029bbaacb ("mm, memory_hotplug: drop CONFIG_MOVABLE_NODE")
the dependency on CONFIG_MOVABLE_NODE was removed for N_MEMORY. Before, CONFIG_HIGHMEM && !CONFIG_MOVABLE_NODE could make (N_MEMORY == N_NORMAL_MEMORY) be true.
After that commit, N_MEMORY cannot be equal to N_NORMAL_MEMORY. So the conditional check in paging_init() is not needed anymore, remove it.
[ bp: Massage. ]
--- arch/x86/mm/init_64.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/x86/mm/init_64.c +1 -2
@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }
Re: [tip: x86/mm] x86/mm: Remove the now redundant N_MEMORY check
Hi,
Quoted 8 lines · On 03/17/20 at 06:20pm, tip-bot2 for Baoquan He wrote:
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: aa61ee7b9ee3cb84c0d3a842b0d17937bf024c46 Gitweb: https://git.kernel.org/tip/aa61ee7b9ee3cb84c0d3a842b0d17937bf024c46 Author: Baoquan He <[email protected]> AuthorDate: Wed, 11 Mar 2020 09:18:23 +08:00 Committer: Borislav Petkov <[email protected]> CommitterDate: Tue, 17 Mar 2020 19:12:39 +01:00
Just a soft reminder, I also got a notice from Andrew that this was picked into his -mm tree before. Maybe one can be dropped to avoid conflict when sending to Linus.
Thanks for taking care of this.
Quoted 40 lines
x86/mm: Remove the now redundant
N_MEMORYcheckIn commit
f70029bbaacb("mm,memory_hotplug: dropCONFIG_MOVABLE_NODE")the dependency on
CONFIG_MOVABLE_NODEwas removed forN_MEMORY. Before,CONFIG_HIGHMEM&& !CONFIG_MOVABLE_NODE could make (N_MEMORY==N_NORMAL_MEMORY) be true.After that commit,
N_MEMORYcannot be equal toN_NORMAL_MEMORY. So the conditional check inpaging_init()is not needed anymore, remove it.[ bp: Massage. ]
Signed-off-by Baoquan He <[email protected]>Signed-off-by Borislav Petkov <[email protected]>Reviewed-by Wei Yang <[email protected]>Acked-by Michal Hocko <[email protected]>--- arch/x86/mm/init_64.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)arch/x86/mm/init_64.c +1
-2@@ -818,8 +818,7 @@ void __init paging_init(void)* will not set it back. */ node_clear_state (0 ,N_MEMORY ); -if (N_MEMORY !=N_NORMAL_MEMORY ) -node_clear_state (0 ,N_NORMAL_MEMORY ); +node_clear_state (0 ,N_NORMAL_MEMORY );zone_sizes_init (); }