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=-11.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,USER_AGENT_GIT autolearn=ham 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 70D1BC433ED for ; Thu, 22 Apr 2021 06:19:14 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id E4D5060E0C for ; Thu, 22 Apr 2021 06:19:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E4D5060E0C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 63C206B006C; Thu, 22 Apr 2021 02:19:13 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5D9996B006E; Thu, 22 Apr 2021 02:19:13 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 47A0E6B0070; Thu, 22 Apr 2021 02:19:13 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0106.hostedemail.com [216.40.44.106]) by kanga.kvack.org (Postfix) with ESMTP id 2BC946B006C for ; Thu, 22 Apr 2021 02:19:13 -0400 (EDT) Received: from smtpin28.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id D89FD1E07 for ; Thu, 22 Apr 2021 06:19:12 +0000 (UTC) X-FDA: 78059000544.28.A5C5CC1 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf14.hostedemail.com (Postfix) with ESMTP id D9BA4C0007D8 for ; Thu, 22 Apr 2021 06:19:00 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id E070661437; Thu, 22 Apr 2021 06:19:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1619072351; bh=aiNqPvrK3ZBf/RWLu2gvO3kob5vQAnJH+Nma7uJgE88=; h=From:To:Cc:Subject:Date:From; b=VL9qOvsr2nvFrKZcsGAOxDY7RsbjZfM7fSRRg5XWY0QXE1qOJhi6l/zAJeuHoiNSi 4n4fKL8s2YnZodz0Gvbb2OIH52szb02HxHgGZtSz7XVskjXqXynuHgA2BhAkjLZa9U SU3J7Nog+EbcP/IRKaM7VwUbdr3VVYBK7r+1Y0n+7TnNnBo8SndU9QbBiMCLqGkeaO VHwJvQuXnj3tCoBXjga6jvJtwuQ/GV28YpaNXP62Zo1QPeKtDqLSWh72VHivE451yo V+EubptW9xFki40ACOz+J06UIJG30vVc2AfikinF6P0FLp6pQ7AqEheYpFsXgnGPj8 nYuOW8KRCpkgA== From: Mike Rapoport To: linux-arm-kernel@lists.infradead.org Cc: Andrew Morton , Anshuman Khandual , Ard Biesheuvel , Catalin Marinas , David Hildenbrand , Marc Zyngier , Mark Rutland , Mike Rapoport , Mike Rapoport , Will Deacon , kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH v3 0/4] arm64: drop pfn_valid_within() and simplify pfn_valid() Date: Thu, 22 Apr 2021 09:18:58 +0300 Message-Id: <20210422061902.21614-1-rppt@kernel.org> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 X-Stat-Signature: g1tg1idqnhjysdinzbdyo9nof3x818jk X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: D9BA4C0007D8 Received-SPF: none (kernel.org>: No applicable sender policy available) receiver=imf14; identity=mailfrom; envelope-from=""; helo=mail.kernel.org; client-ip=198.145.29.99 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1619072340-172762 Content-Transfer-Encoding: quoted-printable 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: From: Mike Rapoport Hi, These patches aim to remove CONFIG_HOLES_IN_ZONE and essentially hardwire pfn_valid_within() to 1.=20 The idea is to mark NOMAP pages as reserved in the memory map and restore the intended semantics of pfn_valid() to designate availability of struct page for a pfn. With this the core mm will be able to cope with the fact that it cannot u= se NOMAP pages and the holes created by NOMAP ranges within MAX_ORDER blocks will be treated correctly even without the need for pfn_valid_within. The patches are only boot tested on qemu-system-aarch64 so I'd really appreciate memory stress tests on real hardware. If this actually works we'll be one step closer to drop custom pfn_valid(= ) on arm64 altogether. v3: * Fix minor issues found by Anshuman * Freshen up the declaration of pfn_valid() to make it consistent with pfn_is_map_memory() * Add more Acked-by and Reviewed-by tags, thanks Anshuman and David v2: Link: https://lore.kernel.org/lkml/20210421065108.1987-1-rppt@kernel.= org * Add check for PFN overflow in pfn_is_map_memory() * Add Acked-by and Reviewed-by tags, thanks David. v1: Link: https://lore.kernel.org/lkml/20210420090925.7457-1-rppt@kernel.= org * Add comment about the semantics of pfn_valid() as Anshuman suggested * Extend comments about MEMBLOCK_NOMAP, per Anshuman * Use pfn_is_map_memory() name for the exported wrapper for memblock_is_map_memory(). It is still local to arch/arm64 in the end because of header dependency issues. rfc: Link: https://lore.kernel.org/lkml/20210407172607.8812-1-rppt@kernel= .org Mike Rapoport (4): include/linux/mmzone.h: add documentation for pfn_valid() memblock: update initialization of reserved pages arm64: decouple check whether pfn is in linear map from pfn_valid() arm64: drop pfn_valid_within() and simplify pfn_valid() arch/arm64/Kconfig | 3 --- arch/arm64/include/asm/memory.h | 2 +- arch/arm64/include/asm/page.h | 3 ++- arch/arm64/kvm/mmu.c | 2 +- arch/arm64/mm/init.c | 16 ++++++++++++++-- arch/arm64/mm/ioremap.c | 4 ++-- arch/arm64/mm/mmu.c | 2 +- include/linux/memblock.h | 4 +++- include/linux/mmzone.h | 11 +++++++++++ mm/memblock.c | 28 ++++++++++++++++++++++++++-- 10 files changed, 61 insertions(+), 14 deletions(-) base-commit: e49d033bddf5b565044e2abe4241353959bc9120 --=20 2.28.0