riscv: vdso: remove hardcoded 0x800 .text section start addr
RFC PATCH 1/1 riscv: vdso: remove hardcoded 0x800 .text section start addr
It seems the hardcoded 0x800 isn't necessary, but removing it brings a small vdso.so and aligns with other architectures.
--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)
arch/riscv/kernel/vdso/vdso.lds.S +1 -7
@@ -31,13 +31,7 @@ SECTIONS .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4); .text : { *(.text .text.*) } :text .data : {
Signature · 7 lines
2.37.2 _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 1 line · Jisheng Zhang
It seems the hardcoded
0x800isn't necessary, but removing it brings a
s/, but/and/
Quoted 1 line
small vdso.so and aligns with other architectures.
This commit message didn't really satisfy my desire to understand why the comment and '. = 0x800' were there in the first place and if its safe to remove now, so I tried to do some of my own digging. I found
commit 5b9304933730 ("x86 vDSO: generate vdso-syms.lds") commit f6b46ebf904f ("x86 vDSO: new layout")
which removes the comment and hard coding for x86 by changing the vdso Makefile. Then looking at
commit 9031fefde6f2 ("arm64: VDSO support")
we see that it starts with the new Makefile approach and doesn't bother with the hard coding from the start. As riscv also started with the new Makefile approach it also could have dropped the hard coding from the start (I guess).
Quoted 12 lines
Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)arch/riscv/kernel/vdso/vdso.lds.S +0
-0@@ -31,13 +31,7 @@ SECTIONS
arch/riscv/kernel/vdso/vdso.lds.S SECTIONS · line 34
Quoted 10 lines
arch/riscv/kernel/vdso/vdso.lds.S +1
-7.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4);
I realize 4 is used here now because I questioned the 16, but after doing my digging I think a larger alignment may be better. Loading the text may be done with 8 byte or larger reads, so having the section aligned to a larger size would be better reading it. We might as well use 16, like arm64 does, and like you had before?
Also, having enough separation between data and text seems to be important for cache reasons, based on the comment in ./arch/x86/entry/vdso/vdso-layout.lds.S and other vdso history. Maybe we should move .note, .eh_frame_hdr, and .eh_frame below .rodata like x86 has it?
Thanks,
drew
Quoted 6 lines
arch/riscv/kernel/vdso/vdso.lds.S +0
-0.text : { *(.text .text.*) } :text .data : {Signature · 1 line
2.37.2
Quoted 53 lines · Andrew Jones
Quoted 1 line · Jisheng Zhang
It seems the hardcoded
0x800isn't necessary, but removing it brings as/, but/and/
Quoted 1 line
small vdso.so and aligns with other architectures.
This commit message didn't really satisfy my desire to understand why the comment and '. =
0x800' were there in the first place and if its safe to remove now, so I tried to do some of my own digging. I foundcommit
5b9304933730("x86 vDSO: generatevdso-syms.lds") commitf6b46ebf904f("x86 vDSO: new layout")which removes the comment and hard coding for x86 by changing the vdso
Makefile. Then looking atcommit
9031fefde6f2("arm64: VDSO support")we see that it starts with the new
Makefileapproach and doesn't bother with the hard coding from the start. As riscv also started with the newMakefileapproach it also could have dropped the hard coding from the start (I guess).Quoted 12 lines
Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)arch/riscv/kernel/vdso/vdso.lds.S +0
-0@@ -31,13 +31,7 @@ SECTIONSarch/riscv/kernel/vdso/vdso.lds.S SECTIONS · line 34
Quoted 10 lines
arch/riscv/kernel/vdso/vdso.lds.S +1
-7.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4);I realize 4 is used here now because I questioned the 16, but after doing my digging I think a larger alignment may be better. Loading the text may be done with 8 byte or larger reads, so having the section aligned to a larger size would be better reading it. We might as well use 16, like arm64 does, and like you had before?
Quoted 6 lines
Also, having enough separation between data and text seems to be important for cache reasons, based on the comment in
./arch/x86/entry/vdso/vdso-layout.lds.Sand other vdso history. Maybe we should move .note, .eh_frame_hdr, and .eh_frame below .rodata like x86 has it?
Thank you so much for pointing out the two commits and above separation, new version will be sent out soon.
Quoted 61 lines · Jisheng Zhang
Quoted 53 lines · Andrew Jones
Quoted 1 line · Jisheng Zhang
It seems the hardcoded
0x800isn't necessary, but removing it brings as/, but/and/
Quoted 1 line
small vdso.so and aligns with other architectures.
This commit message didn't really satisfy my desire to understand why the comment and '. =
0x800' were there in the first place and if its safe to remove now, so I tried to do some of my own digging. I foundcommit
5b9304933730("x86 vDSO: generatevdso-syms.lds") commitf6b46ebf904f("x86 vDSO: new layout")which removes the comment and hard coding for x86 by changing the vdso
Makefile. Then looking atcommit
9031fefde6f2("arm64: VDSO support")we see that it starts with the new
Makefileapproach and doesn't bother with the hard coding from the start. As riscv also started with the newMakefileapproach it also could have dropped the hard coding from the start (I guess).Quoted 12 lines
Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)arch/riscv/kernel/vdso/vdso.lds.S +0
-0@@ -31,13 +31,7 @@ SECTIONSarch/riscv/kernel/vdso/vdso.lds.S SECTIONS · line 34
Quoted 10 lines
arch/riscv/kernel/vdso/vdso.lds.S +1
-7.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4);I realize 4 is used here now because I questioned the 16, but after doing my digging I think a larger alignment may be better. Loading the text may be done with 8 byte or larger reads, so having the section aligned to a larger size would be better reading it. We might as well use 16, like arm64 does, and like you had before?
Quoted 6 lines
Also, having enough separation between data and text seems to be important for cache reasons, based on the comment in
./arch/x86/entry/vdso/vdso-layout.lds.Sand other vdso history. Maybe we should move .note, .eh_frame_hdr, and .eh_frame below .rodata like x86 has it?
Quoted 2 lines
Thank you so much for pointing out the two commits and above separation, new version will be sent out soon.
After looking at the git history, besides your wonderful suggestion, I think we can do something more to clean up and make riscv vdso better, for example, Is the .data section read only, so could be merged with .rodata? or we can discard it as arm64 does? I need some time to dump the section then check and do some test.
Palmer Dabbelt
maintainerQuoted 61 lines · On Thu, 24 Nov 2022 08:11:05 PST (-0800), [email protected] wrote:
Quoted 53 lines · Andrew Jones
Quoted 1 line · Jisheng Zhang
It seems the hardcoded
0x800isn't necessary, but removing it brings as/, but/and/
Quoted 1 line
small vdso.so and aligns with other architectures.
This commit message didn't really satisfy my desire to understand why the comment and '. =
0x800' were there in the first place and if its safe to remove now, so I tried to do some of my own digging. I foundcommit
5b9304933730("x86 vDSO: generatevdso-syms.lds") commitf6b46ebf904f("x86 vDSO: new layout")which removes the comment and hard coding for x86 by changing the vdso
Makefile. Then looking atcommit
9031fefde6f2("arm64: VDSO support")we see that it starts with the new
Makefileapproach and doesn't bother with the hard coding from the start. As riscv also started with the newMakefileapproach it also could have dropped the hard coding from the start (I guess).Quoted 12 lines
Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)arch/riscv/kernel/vdso/vdso.lds.S +0
-0@@ -31,13 +31,7 @@ SECTIONSarch/riscv/kernel/vdso/vdso.lds.S SECTIONS · line 34
Quoted 10 lines
arch/riscv/kernel/vdso/vdso.lds.S +1
-7.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4);I realize 4 is used here now because I questioned the 16, but after doing my digging I think a larger alignment may be better. Loading the text may be done with 8 byte or larger reads, so having the section aligned to a larger size would be better reading it. We might as well use 16, like arm64 does, and like you had before?
Quoted 6 lines
Also, having enough separation between data and text seems to be important for cache reasons, based on the comment in
./arch/x86/entry/vdso/vdso-layout.lds.Sand other vdso history. Maybe we should move .note, .eh_frame_hdr, and .eh_frame below .rodata like x86 has it?
Quoted 2 lines
Thank you so much for pointing out the two commits and above separation, new version will be sent out soon.
Not sure if I missed the v2? I can't find one.
Quoted 62 lines · Palmer Dabbelt
Quoted 61 lines · On Thu, 24 Nov 2022 08:11:05 PST (-0800), [email protected] wrote:
Quoted 59 lines · Andrew Jones
Quoted 1 line · Jisheng Zhang
It seems the hardcoded
0x800isn't necessary, but removing it brings as/, but/and/
Quoted 1 line
small vdso.so and aligns with other architectures.
This commit message didn't really satisfy my desire to understand why the comment and '. =
0x800' were there in the first place and if its safe to remove now, so I tried to do some of my own digging. I foundcommit
5b9304933730("x86 vDSO: generatevdso-syms.lds") commitf6b46ebf904f("x86 vDSO: new layout")which removes the comment and hard coding for x86 by changing the vdso
Makefile. Then looking atcommit
9031fefde6f2("arm64: VDSO support")we see that it starts with the new
Makefileapproach and doesn't bother with the hard coding from the start. As riscv also started with the newMakefileapproach it also could have dropped the hard coding from the start (I guess).Quoted 12 lines
Signed-off-by Jisheng Zhang <[email protected]>--- arch/riscv/kernel/vdso/vdso.lds.S | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)arch/riscv/kernel/vdso/vdso.lds.S +0
-0@@ -31,13 +31,7 @@ SECTIONSarch/riscv/kernel/vdso/vdso.lds.S SECTIONS · line 34
Quoted 10 lines
arch/riscv/kernel/vdso/vdso.lds.S +1
-7.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) } - /* - * This linker script is used both with -r and with -shared. - * For the layouts to match, we need to skip more than enough - * space for the dynamic symbol table, etc. If this amount is - * insufficient, ld -shared will error; simply increase it here. - */ - . = 0x800; + . = ALIGN(4);I realize 4 is used here now because I questioned the 16, but after doing my digging I think a larger alignment may be better. Loading the text may be done with 8 byte or larger reads, so having the section aligned to a larger size would be better reading it. We might as well use 16, like arm64 does, and like you had before?
Also, having enough separation between data and text seems to be important for cache reasons, based on the comment in
./arch/x86/entry/vdso/vdso-layout.lds.Sand other vdso history. Maybe we should move .note, .eh_frame_hdr, and .eh_frame below .rodata like x86 has it?
Quoted 4 lines
Quoted 2 lines
Thank you so much for pointing out the two commits and above separation, new version will be sent out soon.
Not sure if I missed the v2? I can't find one.
When I want to sent a v2, I just knew that patches after rc7 won't be merged for next rc1. Sorry for not being earlier. Will send out v2 once new developement window is reopen.
Thanks