From: Christopher Covington <cov@codeaurora.org> To: Andy Lutomirski <luto@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, criu@openvz.org, Dmitry Safonov <dsafonov@virtuozzo.com>, Will Deacon <Will.Deacon@arm.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Michael Ellerman <mpe@ellerman.id.au>, Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org, linux-mm@kvack.orgdsafonov@virtuozzo.com Subject: Re: VDSO unmap and remap support for additional architectures Date: Fri, 29 Apr 2016 09:22:11 -0400 [thread overview] Message-ID: <57236003.5060804@codeaurora.org> (raw) In-Reply-To: <2ce7203f-305c-6edf-0ef9-448c141cb103@kernel.org> Hi Andy, On 04/28/2016 02:53 PM, Andy Lutomirski wrote: > On 04/28/2016 08:18 AM, Christopher Covington wrote: >> Please take a look at the following prototype of sharing the PowerPC >> VDSO unmap and remap code with other architectures. I've only hooked >> up arm64 to begin with. If folks think this is a reasonable approach I >> can work on 32 bit ARM as well. Not hearing back from an earlier >> request for guidance [1], I simply dove in and started hacking. >> Laurent's test case [2][3] is a compelling illustration of whether VDSO >> remap works or not on a given architecture. > > I think there's a much nicer way: > > https://lkml.kernel.org/r/1461584223-9418-1-git-send-email-dsafonov@virtuozzo.com > > Could arm64 and ppc use this approach? These arch_xyz hooks are gross. Thanks for the pointer. Any thoughts on how to keep essentially identical definitions of vdso_mremap from proliferating into every architecture and variant? > Also, at some point, possibly quite soon, x86 will want a way for > user code to ask the kernel to map a specific vdso variant at a specific > address. Could we perhaps add a new pair of syscalls: > > struct vdso_info { > unsigned long space_needed_before; > unsigned long space_needed_after; > unsigned long alignment; > }; > > long vdso_get_info(unsigned int vdso_type, struct vdso_info *info); > > long vdso_remap(unsigned int vdso_type, unsigned long addr, unsigned int flags); > > #define VDSO_X86_I386 0 > #define VDSO_X86_64 1 > #define VDSO_X86_X32 2 > // etc. > > vdso_remap will map the vdso of the chosen type such at > AT_SYSINFO_EHDR lines up with addr. It will use up to > space_needed_before bytes before that address and space_needed_after > after than address. It will also unmap the old vdso (or maybe only do > that if some flag is set). > > On x86, mremap is *not* sufficient for everything that's needed, > because some programs will need to change the vdso type. I don't I understand. Why can't people just exec() the ELF type that corresponds to the VDSO they want? Thanks, Cov -- Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org> To: Andy Lutomirski <luto@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, criu@openvz.org, Dmitry Safonov <dsafonov@virtuozzo.com>, Will Deacon <Will.Deacon@arm.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Michael Ellerman <mpe@ellerman.id.au>, Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org, linux-mm@kvack.orgdsafonov@virtuozzo.com Subject: Re: VDSO unmap and remap support for additional architectures Date: Fri, 29 Apr 2016 09:22:11 -0400 [thread overview] Message-ID: <57236003.5060804@codeaurora.org> (raw) Message-ID: <20160429132211.KkbANDSJDwVeLZPathpikzrUbghXM1z1_uUlivtLj6M@z> (raw) In-Reply-To: <2ce7203f-305c-6edf-0ef9-448c141cb103@kernel.org> Hi Andy, On 04/28/2016 02:53 PM, Andy Lutomirski wrote: > On 04/28/2016 08:18 AM, Christopher Covington wrote: >> Please take a look at the following prototype of sharing the PowerPC >> VDSO unmap and remap code with other architectures. I've only hooked >> up arm64 to begin with. If folks think this is a reasonable approach I >> can work on 32 bit ARM as well. Not hearing back from an earlier >> request for guidance [1], I simply dove in and started hacking. >> Laurent's test case [2][3] is a compelling illustration of whether VDSO >> remap works or not on a given architecture. > > I think there's a much nicer way: > > https://lkml.kernel.org/r/1461584223-9418-1-git-send-email-dsafonov@virtuozzo.com > > Could arm64 and ppc use this approach? These arch_xyz hooks are gross. Thanks for the pointer. Any thoughts on how to keep essentially identical definitions of vdso_mremap from proliferating into every architecture and variant? > Also, at some point, possibly quite soon, x86 will want a way for > user code to ask the kernel to map a specific vdso variant at a specific > address. Could we perhaps add a new pair of syscalls: > > struct vdso_info { > unsigned long space_needed_before; > unsigned long space_needed_after; > unsigned long alignment; > }; > > long vdso_get_info(unsigned int vdso_type, struct vdso_info *info); > > long vdso_remap(unsigned int vdso_type, unsigned long addr, unsigned int flags); > > #define VDSO_X86_I386 0 > #define VDSO_X86_64 1 > #define VDSO_X86_X32 2 > // etc. > > vdso_remap will map the vdso of the chosen type such at > AT_SYSINFO_EHDR lines up with addr. It will use up to > space_needed_before bytes before that address and space_needed_after > after than address. It will also unmap the old vdso (or maybe only do > that if some flag is set). > > On x86, mremap is *not* sufficient for everything that's needed, > because some programs will need to change the vdso type. I don't I understand. Why can't people just exec() the ELF type that corresponds to the VDSO they want? Thanks, Cov -- Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-04-29 13:22 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20151202121918.GA4523@arm.com> 2016-04-28 15:18 ` VDSO unmap and remap support for additional architectures Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-04-28 15:18 ` [RFC 1/5] powerpc: Rename context.vdso_base to context.vdso Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-05-02 1:05 ` Balbir Singh 2016-05-02 1:05 ` Balbir Singh 2016-05-04 21:21 ` Christopher Covington 2016-04-28 15:18 ` [RFC 2/5] mm/powerpc: Make VDSO unmap generic Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-04-28 15:18 ` [RFC 3/5] mm/powerpc: Make VDSO remap generic Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-04-28 15:18 ` [RFC 4/5] arm64: Use unsigned long for vdso Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-04-28 15:18 ` [RFC 5/5] arm64: Gain VDSO unmap and remap powers Christopher Covington 2016-04-28 15:18 ` Christopher Covington 2016-04-28 18:53 ` VDSO unmap and remap support for additional architectures Andy Lutomirski 2016-04-28 18:53 ` Andy Lutomirski 2016-04-29 13:22 ` Christopher Covington [this message] 2016-04-29 13:22 ` Christopher Covington 2016-04-29 13:55 ` Dmitry Safonov 2016-04-29 13:55 ` Dmitry Safonov 2016-05-03 21:37 ` Christopher Covington 2016-05-03 21:37 ` Christopher Covington
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=57236003.5060804@codeaurora.org \ --to=cov@codeaurora.org \ --cc=Will.Deacon@arm.com \ --cc=arnd@arndb.de \ --cc=benh@kernel.crashing.org \ --cc=catalin.marinas@arm.com \ --cc=criu@openvz.org \ --cc=dsafonov@virtuozzo.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.orgdsafonov \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=luto@kernel.org \ --cc=mpe@ellerman.id.au \ --cc=paulus@samba.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).