From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753241AbcD1PU0 (ORCPT ); Thu, 28 Apr 2016 11:20:26 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:36713 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753217AbcD1PUX (ORCPT ); Thu, 28 Apr 2016 11:20:23 -0400 From: Christopher Covington To: Catalin Marinas , criu@openvz.org, Laurent Dufour , Will Deacon , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Arnd Bergmann , 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: VDSO unmap and remap support for additional architectures Date: Thu, 28 Apr 2016 11:18:52 -0400 Message-Id: <1461856737-17071-1-git-send-email-cov@codeaurora.org> X-Mailer: git-send-email 2.8.1 In-Reply-To: <20151202121918.GA4523@arm.com> References: <20151202121918.GA4523@arm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 1. https://lkml.org/lkml/2016/3/2/225 2. https://lists.openvz.org/pipermail/criu/2015-March/019161.html 3. http://lists.openvz.org/pipermail/criu/attachments/20150318/f02ed9ea/attachment.bin Thanks, Christopher Covington