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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id D2AE0C43334 for ; Tue, 21 Jun 2022 17:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc: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=Qc23CE6tvq35NptV9BAw7CgP3V73C0A4Mhjk2y60IDc=; b=zU39Sv/RhEo1mu u9PhPsinPIL50eicYeJNbyhZGyqOqWVZwaPesDwLHayaiLTlbAUfvIfWl2ziEjy54QmuVq2Ilzpnm JMMTcnzS+CYgYhsUT4ejlpZIJQbISaFyIIQVppzQfBYui1j46bPdj2lpFNDLXxh3QnaLix8oW3k1f VoK1kDmPjxN3sTwPyu4wh7UDh0HJ/OQC2zdox8KPcgYLVq2b+5+uFF73YtgYmPFPkNQZGs5QpyZYT LQYZJVl7Ly9FUMn5T0qlXDsWfWncsU2rBve8KXkUFZE68Asf0xQSrxr4PG2K2OBbJnjPdj0sMEgVS 5LrXgxgQl9KBgFPvj/aA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o3he0-006Y1u-SF; Tue, 21 Jun 2022 17:26:29 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o3hcy-006XVt-Rg for linux-arm-kernel@lists.infradead.org; Tue, 21 Jun 2022 17:25:26 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2B41461555; Tue, 21 Jun 2022 17:25:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94C94C341C5; Tue, 21 Jun 2022 17:25:22 +0000 (UTC) Date: Tue, 21 Jun 2022 18:25:17 +0100 From: Catalin Marinas To: Russell King Cc: Andre Mueller , Will Deacon , "linux-arm-kernel@lists.infradead.org" Subject: Re: [External] : Re: [PATCH] Documentation/arm64: update memory layout table. Message-ID: References: <20220621081651.61755-1-am@emlix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220621_102524_956786_58A465CF X-CRM114-Status: GOOD ( 20.20 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jun 21, 2022 at 02:47:30PM +0000, Russell King wrote: > From: Catalin Marinas > > On Tue, Jun 21, 2022 at 10:16:51AM +0200, Andre Mueller wrote: > > > Commit b89ddf4cca43("arm64/bpf: Remove 128MB limit for BPF JIT programs") > > > removes the bpf jit region from the memory layout of the Aarch64 > > > architecture. However, it forgets to update the documentation > > > accordingly. > > > > > > - Remove the bpf jit region. > > > - Fix the Start and End addresses of the modules region. > > > - Fix the Start address of the vmalloc region. > > > > > > Signed-off-by: Andre Mueller > > > > Acked-by: Catalin Marinas > > > > but I still wonder whether we should remove this table altogether. > > I've found the table particularly useful when wanting to know the > virtual address space layout, so it does seem to have some value. Yes but that's only one of the configurations and it keeps getting out of sync. We used to print the information at boot until commit 071929dbdd86 ("arm64: Stop printing the virtual memory layout"). I think we could bring some of that back, maybe even behind a debug command line option or config (or expose it via sysfs). We shouldn't print the info that has security implications like where stext is mapped or anything randomised, only the rough layout like in the doc. > (Replying from my work email as that's where it's been sent. Can't do > anything but top-post, which is why I use my armlinux.org.uk email for > kernel stuff - thanks Outlook web.) As a side-note, Arm uses outlook as well but mutt can connect via IMAP (if enabled; a bit of a pain with oauth2). For SMTP I use the kernel.org one since outlook tends to corrupt patches. -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel