From: Christopher Covington <cov@codeaurora.org>
To: Balbir Singh <bsingharora@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
criu@openvz.org, Laurent Dufour <ldufour@linux.vnet.ibm.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.org
Subject: Re: [RFC 1/5] powerpc: Rename context.vdso_base to context.vdso
Date: Wed, 4 May 2016 17:21:18 -0400 [thread overview]
Message-ID: <572A67CE.4010109@codeaurora.org> (raw)
In-Reply-To: <5726A7D5.7030305@gmail.com>
Hi Balbir,
On 05/01/2016 09:05 PM, Balbir Singh wrote:
> On 29/04/16 01:18, Christopher Covington wrote:
>> In order to share remap and unmap support for the VDSO with other
>> architectures without duplicating the code, we need a common name and type
>> for the address of the VDSO. An informal survey of the architectures
>> indicates unsigned long vdso is popular. Change the variable name in
>> powerpc from mm->context.vdso_base to simply mm->context.vdso.
>
> Could you please provide additional details on why the remap/unmap operations are required?
The goal is to make checkpointing and restoring processes work on
several different architectures and ABIs, in the face of Address Space
Layout Randomization (ASLR) and other factors that might change the VDSO
virtual address from one exec() to the next.
Here's the patch adding PowerPC support:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=83d3f0e90c6c8f833e3da91917c243a916fda69e
> This patch does rename, but should it abstract via a function acesss
> to vmap field using arch_* operations? Not sure
I'm sorry, but I don't understand this question. Are you saying ARM,
Power etc. need VDSO unmap and remap log that behave differently? So far
I've found the differences to be stylistic rather than really affecting
generated code behavior.
Thanks,
Christopher Covington
--
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-05-04 21:21 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 [this message]
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
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=572A67CE.4010109@codeaurora.org \
--to=cov@codeaurora.org \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=criu@openvz.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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: link
Be 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).