[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87oa1vn8lc.fsf@concordia.ellerman.id.au>
Date: Fri, 04 Nov 2016 15:59:43 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Christopher Covington <cov@...eaurora.org>, criu@...nvz.org,
Will Deacon <will.deacon@....com>, linux-mm@...ck.org,
Laurent Dufour <ldufour@...ux.vnet.ibm.com>
Cc: Christopher Covington <cov@...eaurora.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 6/7] mm/powerpc: Use generic VDSO remap and unmap functions
Christopher Covington <cov@...eaurora.org> writes:
> The PowerPC VDSO remap and unmap code was copied to a generic location,
> only modifying the variable name expected in mm->context (vdso instead of
> vdso_base) to match most other architectures. Having adopted this generic
> naming, drop the code in arch/powerpc and use the generic version.
>
> Signed-off-by: Christopher Covington <cov@...eaurora.org>
> ---
> arch/powerpc/Kconfig | 1 +
> arch/powerpc/include/asm/Kbuild | 1 +
> arch/powerpc/include/asm/mm-arch-hooks.h | 28 -------------------------
> arch/powerpc/include/asm/mmu_context.h | 35 +-------------------------------
> 4 files changed, 3 insertions(+), 62 deletions(-)
> delete mode 100644 arch/powerpc/include/asm/mm-arch-hooks.h
This looks OK.
Have you tested it on powerpc? I could but I don't know how to actually
trigger these paths, I assume I need a CRIU setup?
Can you flip the subject to "powerpc/mm: ...".
cheers
Powered by blists - more mailing lists