From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7302EC43603 for ; Thu, 5 Dec 2019 19:25:45 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 4425E206D9 for ; Thu, 5 Dec 2019 19:25:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4425E206D9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=libc.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id E3DB26B11CA; Thu, 5 Dec 2019 14:25:44 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id DEE066B11CB; Thu, 5 Dec 2019 14:25:44 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D04FF6B11CC; Thu, 5 Dec 2019 14:25:44 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0253.hostedemail.com [216.40.44.253]) by kanga.kvack.org (Postfix) with ESMTP id BD52C6B11CA for ; Thu, 5 Dec 2019 14:25:44 -0500 (EST) Received: from smtpin07.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with SMTP id 7B8F08248068 for ; Thu, 5 Dec 2019 19:25:44 +0000 (UTC) X-FDA: 76232067408.07.smell73_8956ace155c33 X-HE-Tag: smell73_8956ace155c33 X-Filterd-Recvd-Size: 3212 Received: from brightrain.aerifal.cx (216-12-86-13.cv.mvl.ntelos.net [216.12.86.13]) by imf27.hostedemail.com (Postfix) with SMTP for ; Thu, 5 Dec 2019 19:25:43 +0000 (UTC) Received: from dalias by brightrain.aerifal.cx with local (Exim 3.15 #2) id 1icwiY-0004sv-00; Thu, 05 Dec 2019 19:23:14 +0000 Date: Thu, 5 Dec 2019 14:23:14 -0500 From: Rich Felker To: Rob Landley Cc: Peter Zijlstra , Geert Uytterhoeven , Will Deacon , "Aneesh Kumar K.V" , Andrew Morton , Nicholas Piggin , Linux-Arch , Linux MM , Linux Kernel Mailing List , Russell King , Heiko Carstens , Rik van Riel , Yoshinori Sato , Linux-sh list , Guenter Roeck Subject: Re: [PATCH v6 10/18] sh/tlb: Convert SH to generic mmu_gather Message-ID: <20191205192314.GC16318@brightrain.aerifal.cx> References: <20190219103148.192029670@infradead.org> <20190219103233.443069009@infradead.org> <20191204104733.GR2844@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Dec 05, 2019 at 01:24:02PM -0600, Rob Landley wrote: > On 12/4/19 4:47 AM, Peter Zijlstra wrote: > > On Tue, Dec 03, 2019 at 12:19:00PM +0100, Geert Uytterhoeven wrote: > >> Hoi Peter, > >> > >> On Tue, Feb 19, 2019 at 11:35 AM Peter Zijlstra wrote: > >>> Generic mmu_gather provides everything SH needs (range tracking and > >>> cache coherency). > >>> > >>> Cc: Will Deacon > >>> Cc: "Aneesh Kumar K.V" > >>> Cc: Andrew Morton > >>> Cc: Nick Piggin > >>> Cc: Yoshinori Sato > >>> Cc: Rich Felker > >>> Signed-off-by: Peter Zijlstra (Intel) > >> > >> I got remote access to an SH7722-based Migo-R again, which spews a long > >> sequence of BUGs during userspace startup. I've bisected this to commit > >> c5b27a889da92f4a ("sh/tlb: Convert SH to generic mmu_gather"). > > > > Whoopsy.. also, is this really the first time anybody booted an SH > > kernel in over a year ?!? > > No, but most people running this kind of hardware tend not to upgrade to current > kernels on a regular basis. > > The j-core guys tested the 5.3 release. I can't find an email about 5.4 so I > dunno if that's been tested yet? Being that this code is about mmu, does it affect nommu machines? That's what we've got at present on the J-core side. Rich