Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1444195imu; Wed, 16 Jan 2019 20:07:47 -0800 (PST) X-Google-Smtp-Source: ALg8bN4aSt3THnP414bWfE9YxnTWy5q59u36merinfK7vBojhoYwFQm73zoLTfNRk7RsfuptAYzc X-Received: by 2002:a63:5c22:: with SMTP id q34mr11960403pgb.417.1547698067373; Wed, 16 Jan 2019 20:07:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547698067; cv=none; d=google.com; s=arc-20160816; b=aqu8E7LCg2EmN3/Ah2SObBzV1sCdIqAazsL8zbdL80Ag53Y4L0iz/uSB6IV3zm89Yw uQb+IxmsSFrAzEVo+RHfe5D/71dAf5kRs0CJdAGUSKjxcbVYCHU/Bnu/YdD+9zmbPPYg w4dH5UJgs18kaWJxbYbYT3/30UyvvWg5Tugi51imByNr69Bq6uYw/jT1RPrc9+AEL/E/ RXUWm9BMTH4dw99T9jkgWWF3Iibu/f/WtoJlrcB62J7fHHIDgQChQrj276OM3PVcSX54 0wxHVqtVP3iNJ7Y3VCwwWaFhOUzcBXwxIJNcr3yYpqfTFHQ6QAbkKzL2CTDO6cufSRXO M5sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=RssY5jBIYO3kjcknWLVYqdukiqwxw9EeRFRnZmASpOA=; b=l5880uYXmGCo7WB9Uci8z8KPfwgpn7yqY2JIbzdnoG5YfxZuU54+hzKzZEC0mPczZB hxNulrpA3yOEhP4SDAxgyg9YzIDGNpZKx34wjPUJg3+Hw3tl6pB03I+zGveDrxCK9sD9 rjR6VA0oPf0/kQqyrWVI46AWyaNeqN7HmHRuSj8a8EU71VG+VjmYpR69d0AkjtR8kqzn I3HGskodVOnf3ez/mo8cDc7O6k2xbBrQdI6sRRPpyVhA99TB3NbpYSMCmQzastf1+OAS yELcVjnEdbIQTIMj0ckp4fX3HqVPqByp9mGJkg3FDr9hQcxgd6+uavQ8+M3Ss+afAS2g 0e9A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b="rsm/lq6Z"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q5si480136pgg.204.2019.01.16.20.07.31; Wed, 16 Jan 2019 20:07:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b="rsm/lq6Z"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393192AbfAPNe5 (ORCPT + 99 others); Wed, 16 Jan 2019 08:34:57 -0500 Received: from pegase1.c-s.fr ([93.17.236.30]:55688 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733118AbfAPNe5 (ORCPT ); Wed, 16 Jan 2019 08:34:57 -0500 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 43fp9967Bhz9vBKb; Wed, 16 Jan 2019 14:34:53 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=rsm/lq6Z; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id NFNnFJHY8mP1; Wed, 16 Jan 2019 14:34:53 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 43fp9954cNz9vBKS; Wed, 16 Jan 2019 14:34:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1547645693; bh=RssY5jBIYO3kjcknWLVYqdukiqwxw9EeRFRnZmASpOA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=rsm/lq6ZA5olwEoJxQDt/ToWNMnrfN3ak5QhIEMc+ZCQ9kLo6gCn+REjusF843lYl yPJCPCBAQPzY1FMBteBZerzxLA8EwbSAYW/FR0Qr9nA9CjRT2V3RQrAk5VmuitjaX8 ZYNr9pRJb5Q+KgxhL16Lv4V5s1++nkx92VQRUtTA= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 15B578B847; Wed, 16 Jan 2019 14:34:55 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 01cTsM86UASg; Wed, 16 Jan 2019 14:34:55 +0100 (CET) Received: from PO15451 (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 651688B830; Wed, 16 Jan 2019 14:34:54 +0100 (CET) Subject: Re: [PATCH v2 00/15] powerpc/32s: Use BATs/LTLBs for STRICT_KERNEL_RWX To: =?UTF-8?Q?Jonathan_Neusch=c3=a4fer?= Cc: Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org References: <20190113181621.GA22334@latitude> <714e78ba-1e92-a856-3dd6-a1fb96ad3785@c-s.fr> <20190113210227.GB22334@latitude> <334b1b02-b652-499c-904e-09e6f7164b8c@c-s.fr> <20190115003353.GD22334@latitude> <20190116003535.GE22334@latitude> <20190116131637.GF22334@latitude> From: Christophe Leroy Message-ID: <5051e5cb-89ea-b857-1288-1ac6bfe67872@c-s.fr> Date: Wed, 16 Jan 2019 14:34:53 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190116131637.GF22334@latitude> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 16/01/2019 à 14:16, Jonathan Neuschäfer a écrit : > On Wed, Jan 16, 2019 at 07:55:29AM +0100, Christophe Leroy wrote: >> Le 16/01/2019 à 01:35, Jonathan Neuschäfer a écrit : >>> Thinning the kernel down a bit actually makes it boot again. Ooops...! >>> Maybe enabling CONFIG_STRICT_KERNEL_RWX has made it just large enough to >>> fail the hash table allocation, but there may have been other factors >>> involved (I'm not sure exactly). Sorry for the confusion! >> >> Ok, that must be the reason. Thanks for testing. >> >> What about the following modification which maps a second 256Mb BAT, does it >> helps ? >> >> >> >> diff --git a/arch/powerpc/kernel/head_32.S b/arch/powerpc/kernel/head_32.S >> index c2f564690778..ea574596de37 100644 >> --- a/arch/powerpc/kernel/head_32.S >> +++ b/arch/powerpc/kernel/head_32.S >> @@ -1160,6 +1160,14 @@ initial_bats: >> mtspr SPRN_DBAT0U,r11 /* bit in upper BAT register */ >> mtspr SPRN_IBAT0L,r8 >> mtspr SPRN_IBAT0U,r11 >> +#ifdef CONFIG_WII >> + addis r11,r11,0x10000000@h >> + addis r8,r8,0x10000000@h >> + mtspr SPRN_DBAT2L,r8 >> + mtspr SPRN_DBAT2U,r11 >> + mtspr SPRN_IBAT2L,r8 >> + mtspr SPRN_IBAT2U,r11 >> +#endif >> isync >> blr >> >> diff --git a/arch/powerpc/mm/ppc_mmu_32.c b/arch/powerpc/mm/ppc_mmu_32.c >> index 3f4193201ee7..a334fd5210a8 100644 >> --- a/arch/powerpc/mm/ppc_mmu_32.c >> +++ b/arch/powerpc/mm/ppc_mmu_32.c >> @@ -259,6 +259,8 @@ void setup_initial_memory_limit(phys_addr_t >> first_memblock_base, >> /* 601 can only access 16MB at the moment */ >> if (PVR_VER(mfspr(SPRN_PVR)) == 1) >> memblock_set_current_limit(min_t(u64, first_memblock_size, 0x01000000)); >> + else if (IS_ENABLED(CONFIG_WII)) >> + memblock_set_current_limit(min_t(u64, first_memblock_size, 0x20000000)); >> else /* Anything else has 256M mapped */ >> memblock_set_current_limit(min_t(u64, first_memblock_size, 0x10000000)); >> } > > I haven't tested it, but this patch won't be enough, because we're only > looking at the first memblock, and the additional memory in the Wii > (MEM2) is the second memblock. > Yes right. Would the following work instead ? memblock_set_current_limit(0x20000000); Christophe