From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Mon, 11 May 2020 15:13:56 +0000 Subject: Re: sort out the flush_icache_range mess Message-Id: <20200511151356.GB28634@lst.de> List-Id: References: <20200510075510.987823-1-hch@lst.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Geert Uytterhoeven Cc: Christoph Hellwig , Andrew Morton , Arnd Bergmann , Roman Zippel , Linux-Arch , "open list:TENSILICA XTENSA PORT (xtensa)" , Michal Simek , Jessica Yu , "linux-ia64@vger.kernel.org" , linux-c6x-dev@linux-c6x.org, Linux-sh list , "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , linux-um , Linux Kernel Mailing List , "open list:BROADCOM NVRAM DRIVER" , Linux MM On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. 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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 873FDC54E8E for ; Mon, 11 May 2020 15:14:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6FBCD20746 for ; Mon, 11 May 2020 15:14:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730387AbgEKPOC (ORCPT ); Mon, 11 May 2020 11:14:02 -0400 Received: from verein.lst.de ([213.95.11.211]:36611 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729955AbgEKPOB (ORCPT ); Mon, 11 May 2020 11:14:01 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B6F0368BFE; Mon, 11 May 2020 17:13:56 +0200 (CEST) Date: Mon, 11 May 2020 17:13:56 +0200 From: Christoph Hellwig To: Geert Uytterhoeven Cc: Christoph Hellwig , Andrew Morton , Arnd Bergmann , Roman Zippel , Linux-Arch , "open list:TENSILICA XTENSA PORT (xtensa)" , Michal Simek , Jessica Yu , "linux-ia64@vger.kernel.org" , linux-c6x-dev@linux-c6x.org, Linux-sh list , "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , linux-um , Linux Kernel Mailing List , "open list:BROADCOM NVRAM DRIVER" , Linux MM , linux-m68k , Openrisc , alpha , sparclinux , Linux FS Devel , linux-riscv@lists.infradead.org, linuxppc-dev , Linux ARM Subject: Re: sort out the flush_icache_range mess Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: sort out the flush_icache_range mess Date: Mon, 11 May 2020 17:13:56 +0200 Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-m68k-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Christoph Hellwig , Andrew Morton , Arnd Bergmann , Roman Zippel , Linux-Arch , "open list:TENSILICA XTENSA PORT (xtensa)" , Michal Simek , Jessica Yu , "linux-ia64@vger.kernel.org" , linux-c6x-dev@linux-c6x.org, Linux-sh list , "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , linux-um , Linux Kernel Mailing List , "open list:BROADCOM NVRAM DRIVER" , Linux MM lin List-Id: linux-arch.vger.kernel.org On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 11 May 2020 17:13:56 +0200 From: Christoph Hellwig Subject: Re: sort out the flush_icache_range mess Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Geert Uytterhoeven Cc: Christoph Hellwig , Andrew Morton , Arnd Bergmann , Roman Zippel , Linux-Arch , "open list:TENSILICA XTENSA PORT (xtensa)" , Michal Simek , Jessica Yu , "linux-ia64@vger.kernel.org" , linux-c6x-dev@linux-c6x.org, Linux-sh list , "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , linux-um , Linux Kernel Mailing List , "open list:BROADCOM NVRAM DRIVER" , Linux MM , linux-m68k , Openrisc , alpha , sparclinux , Linux FS Devel , linux-riscv@lists.infradead.org, linuxppc-dev , Linux ARM List-ID: Message-ID: <20200511151356.5HQZbQ22tv1XKCWEFiz8YEW6v3zVxPurW4BZOf0Yj4k@z> On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. 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=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 F290DC47255 for ; Mon, 11 May 2020 15:14:14 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BE5A8206D5 for ; Mon, 11 May 2020 15:14:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="eK0CFrhK" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BE5A8206D5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Cc:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To :Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=b1L11x8S5CHP+Yl3bwgtZ2KpvMz6mPd3eUM9MOv57ZE=; b=eK0CFrhKT5WvZ671vd2XClufP y7TVWB9dZVBChBfvtj/QYEPj3YIOEVETsFpCwMqGYQQL3wgGD/1kwgF0Ylx/zHCVsLFPZrfcAnMiP 7BjrZW1BCjQMJ8/+0xQkUwigKXjQRPK+oGhI/t1FfeEa2pbqj5eu0HEwBsD/+kHAl4ujAnW9KbCa6 XSTjMTHyiPVRi8vyx2569oaC3ZyQmqF/CvK1eweUjUAK8ZzFEKjCerHPfV8N9OvBnHfR/U+OlYDQY 5y+OPzzERo5b9e+br27fqJekc+KLFIUBpIhYqv7Gnnx0rBF2lEV404pE9zqvv02i40VUTjJuPMQj9 7+34XN26g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYA8B-0001uF-3W; Mon, 11 May 2020 15:14:11 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYA7z-0001jy-PL; Mon, 11 May 2020 15:14:01 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id B6F0368BFE; Mon, 11 May 2020 17:13:56 +0200 (CEST) Date: Mon, 11 May 2020 17:13:56 +0200 From: Christoph Hellwig To: Geert Uytterhoeven Subject: Re: sort out the flush_icache_range mess Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200511_081359_970252_02A81D7E X-CRM114-Status: UNSURE ( 8.87 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "linux-ia64@vger.kernel.org" , Linux-sh list , Roman Zippel , "open list:BROADCOM NVRAM DRIVER" , Linux MM , sparclinux , linux-riscv@lists.infradead.org, Christoph Hellwig , Linux-Arch , linux-c6x-dev@linux-c6x.org, "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , "open list:TENSILICA XTENSA PORT \(xtensa\)" , Arnd Bergmann , Jessica Yu , linux-um , linux-m68k , Openrisc , Linux ARM , Michal Simek , Linux Kernel Mailing List , alpha , Linux FS Devel , Andrew Morton , linuxppc-dev Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. 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=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 0A8B0C47255 for ; Mon, 11 May 2020 15:14:04 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D3ACE2078E for ; Mon, 11 May 2020 15:14:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="iSeH1Oxk" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D3ACE2078E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=iON8hnB8jMTf+7WDvSI8Y3OucCaPn4kwJDXVxeJJiwg=; b=iSeH1OxkbZzTqK QPvxfTCdk/sHsJPrZWcdhhQqEAbUDbP9odrXNpISzYhKxM45AaEuXyxP0YouPziHIbS2G7rXmqItD A9utHjA/cRxtlL3cARMaUdSaZYn+n+/q/CmEx/tOn6YQgzU+S7GaWl/WWqqmJuS5k996h/t1RmxnA EfkC+D7IL5KDP2wpu+XBPxifYL300lCjp8Nb/HSEoOZ/SdZXduBmcFYXcOcpMUR5nTItCJnrp3yrq V75dxB744e5/1oS3IHEkIedhGBYLlgTIL20/39FiCsaRHy7RECPihRhHzxC2rFjPxjPY4HSLvj8dM G/WsYcXJSCrI/u6alO3Q==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYA83-0001lR-E6; Mon, 11 May 2020 15:14:03 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jYA7z-0001jy-PL; Mon, 11 May 2020 15:14:01 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id B6F0368BFE; Mon, 11 May 2020 17:13:56 +0200 (CEST) Date: Mon, 11 May 2020 17:13:56 +0200 From: Christoph Hellwig To: Geert Uytterhoeven Subject: Re: sort out the flush_icache_range mess Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200511_081359_970252_02A81D7E X-CRM114-Status: UNSURE ( 8.87 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "linux-ia64@vger.kernel.org" , Linux-sh list , Roman Zippel , "open list:BROADCOM NVRAM DRIVER" , Linux MM , sparclinux , linux-riscv@lists.infradead.org, Christoph Hellwig , Linux-Arch , linux-c6x-dev@linux-c6x.org, "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , "open list:TENSILICA XTENSA PORT \(xtensa\)" , Arnd Bergmann , Jessica Yu , linux-um , linux-m68k , Openrisc , Linux ARM , Michal Simek , Linux Kernel Mailing List , alpha , Linux FS Devel , Andrew Morton , linuxppc-dev Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Mon, 11 May 2020 17:13:56 +0200 Subject: [OpenRISC] sort out the flush_icache_range mess In-Reply-To: References: <20200510075510.987823-1-hch@lst.de> Message-ID: <20200511151356.GB28634@lst.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: openrisc@lists.librecores.org On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA at mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs.