From: Balbir Singh <bsingharora@gmail.com>
To: Christopher Covington <cov@codeaurora.org>,
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: Mon, 2 May 2016 11:05:25 +1000 [thread overview]
Message-ID: <5726A7D5.7030305@gmail.com> (raw)
In-Reply-To: <1461856737-17071-2-git-send-email-cov@codeaurora.org>
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?
This patch does rename, but should it abstract via a function acesss to vmap field using arch_* operations? Not sure
Balbir Singh
--
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: Balbir Singh <bsingharora@gmail.com>
To: Christopher Covington <cov@codeaurora.org>,
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: Mon, 2 May 2016 11:05:25 +1000 [thread overview]
Message-ID: <5726A7D5.7030305@gmail.com> (raw)
Message-ID: <20160502010525.7e30rvg1im85Jdylc_NU9M65Yjhd3DjCHfrps3D9F_c@z> (raw)
In-Reply-To: <1461856737-17071-2-git-send-email-cov@codeaurora.org>
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?
This patch does rename, but should it abstract via a function acesss to vmap field using arch_* operations? Not sure
Balbir Singh
WARNING: multiple messages have this Message-ID (diff)
From: bsingharora@gmail.com (Balbir Singh)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/5] powerpc: Rename context.vdso_base to context.vdso
Date: Mon, 2 May 2016 11:05:25 +1000 [thread overview]
Message-ID: <5726A7D5.7030305@gmail.com> (raw)
In-Reply-To: <1461856737-17071-2-git-send-email-cov@codeaurora.org>
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?
This patch does rename, but should it abstract via a function acesss to vmap field using arch_* operations? Not sure
Balbir Singh
next prev parent reply other threads:[~2016-05-02 1:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:49 [PATCH] arm64: Support VDSO remapping Christopher Covington
2015-11-25 12:49 ` Christopher Covington
2015-12-02 12:19 ` Will Deacon
2015-12-02 12:19 ` Will Deacon
2015-12-03 18:05 ` Christopher Covington
2015-12-03 18:05 ` Christopher Covington
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 ` 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-04-28 15:18 ` Christopher Covington
2016-05-02 1:05 ` Balbir Singh [this message]
2016-05-02 1:05 ` Balbir Singh
2016-05-02 1:05 ` Balbir Singh
2016-05-04 21:21 ` Christopher Covington
2016-05-04 21:21 ` Christopher Covington
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 ` 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 ` 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 ` 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 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-28 18:53 ` Andy Lutomirski
2016-04-29 13:22 ` Christopher Covington
2016-04-29 13:22 ` Christopher Covington
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-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
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=5726A7D5.7030305@gmail.com \
--to=bsingharora@gmail.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.