From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by kanga.kvack.org (Postfix) with ESMTP id 1FBB76B0036 for ; Mon, 25 Aug 2014 22:41:12 -0400 (EDT) Received: by mail-ig0-f178.google.com with SMTP id uq10so3812766igb.5 for ; Mon, 25 Aug 2014 19:41:11 -0700 (PDT) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net. [2001:558:fe14:44:76:96:59:211]) by mx.google.com with ESMTP id we8si1516704icb.75.2014.08.25.19.41.11 for ; Mon, 25 Aug 2014 19:41:11 -0700 (PDT) Message-ID: <53FBF3C3.90509@gentoo.org> Date: Mon, 25 Aug 2014 22:41:07 -0400 From: Joshua Kinard MIME-Version: 1.0 Subject: Re: [PATCH v4 0/2] mm/highmem: make kmap cache coloring aware References: <1406941899-19932-1-git-send-email-jcmvbkbc@gmail.com> <20140825171600.GH25892@linux-mips.org> <53FBCD09.1050003@gentoo.org> <53FBD676.8080307@gmail.com> In-Reply-To: <53FBD676.8080307@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: David Daney Cc: Ralf Baechle , Max Filippov , linux-xtensa@linux-xtensa.org, Chris Zankel , Marc Gauthier , linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, David Rientjes , Andrew Morton , Leonid Yegoshin , Steven Hill On 08/25/2014 20:36, David Daney wrote: > On 08/25/2014 04:55 PM, Joshua Kinard wrote: >> On 08/25/2014 13:16, Ralf Baechle wrote: >>> On Sat, Aug 02, 2014 at 05:11:37AM +0400, Max Filippov wrote: >>> >>>> this series adds mapping color control to the generic kmap code, allowing >>>> architectures with aliasing VIPT cache to use high memory. There's also >>>> use example of this new interface by xtensa. >>> >>> I haven't actually ported this to MIPS but it certainly appears to be >>> the right framework to get highmem aliases handled on MIPS, too. >>> >>> Though I still consider increasing PAGE_SIZE to 16k the preferable >>> solution because it will entirly do away with cache aliases. >> >> Won't setting PAGE_SIZE to 16k break some existing userlands (o32)? I use a >> 4k PAGE_SIZE because the last few times I've tried 16k or 64k, init won't >> load (SIGSEGVs or such, which panicks the kernel). >> > > It isn't supposed to break things. Using "stock" toolchains should result > in executables that will run with any page size. > > In the past, some geniuses came up with some linker (ld) patches that, in > order to save a few KB of RAM, produced executables that ran only on 4K pages. > > There were some equally astute Debian emacs package maintainers that were > carrying emacs patches into Debian that would not work on non-4K page size > systems. > > That said, I think such thinking should be punished. The punishment should > be to not have their software run when we select non-4K page sizes. The > vast majority of prepackaged software runs just fine with a larger page size. Well, it does appear to mostly work now w/ 16k PAGE_SIZE. The Octane booted into userland with just a couple of "illegal instruction" errors from 'rm' and 'mdadm'. I wonder if that's tied to a hardcoded PAGE_SIZE somewhere. Have to dig around and find something that reproduces the problem on demand. -- Joshua Kinard Gentoo/MIPS kumba@gentoo.org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic -- 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: email@kvack.org