From patchwork Sat May 13 22:04:09 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Kirill A. Shutemov" X-Patchwork-Id: 13240342 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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id D32C8C77B7F for ; Sat, 13 May 2023 22:04:49 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E814F6B0071; Sat, 13 May 2023 18:04:48 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E31F86B0072; Sat, 13 May 2023 18:04:48 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CD2296B0074; Sat, 13 May 2023 18:04:48 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id BDFF16B0071 for ; Sat, 13 May 2023 18:04:48 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 7AC90411C2 for ; Sat, 13 May 2023 22:04:48 +0000 (UTC) X-FDA: 80786612256.19.A1B423A Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by imf07.hostedemail.com (Postfix) with ESMTP id F12B740006 for ; Sat, 13 May 2023 22:04:45 +0000 (UTC) Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=hRX6l4Sb; dmarc=pass (policy=none) header.from=intel.com; spf=none (imf07.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 192.55.52.43) smtp.mailfrom=kirill.shutemov@linux.intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1684015486; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:references:dkim-signature; bh=A4HABshlkdbCmkqYb9ksjKYD0zJP84cMDE/TcKktxTM=; b=W4D0UoDCYsVq0h0ZH6t0d4k1taNinkbZKbYn6XHqPB3yn8EcPzk/3ZxXHTi1FmGSz3qtgj H+qgiKIc8044YeQLl2BV3ycHQUiBe7jApwMDTgaFj0aGmY9HDZAgIfla4RF4YI6DHz3ZIU PgMrEKjdbjXjp8yz5kSvDIQTasoZiqE= ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=hRX6l4Sb; dmarc=pass (policy=none) header.from=intel.com; spf=none (imf07.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 192.55.52.43) smtp.mailfrom=kirill.shutemov@linux.intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1684015486; a=rsa-sha256; cv=none; b=GiPU6Tg0d8AUKUXh9eIt/96j935SNNk9S8GKtsuXq2bazGHlxlNWmYt4I3HBpSCgfVTJWc KiV+le0fpC6P++ZqoGDLSam2KqUKPFGWbf96xN4pKmha2XugoHf1xC1Gl4TcmDRR4Tp0+6 DdFX2HTirlSmphRh9XcyDmRcVpZgQjg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684015486; x=1715551486; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=rKrSTaFrImjBUWlGMSvJ5QC1+r56yn7XTD8IiVRb4yg=; b=hRX6l4SbWOcbjPjTbvL0c8wxXfo5JikbH335R6vLmrmKPms4dnoFKT6a cUfEh0dzufT1gWreDxIVynRMa29BekpWemNR9mnYivqa2g7pjV4IJXmOy APFEMbVmjrPUVWRSQ97sk9uhelXIARimCWVjmvDrwz22DZlLeNkpTuWvH 4p82TW0sQhleAXyZOLHq2tkAtGeEFUqiMIbblxJF2bzBqXBKHJMWg0DNm AqF7EB9ihKKCuO7xUX2CHl1fu20i/UONCnvcqLGgdwGScPlryhnJup29R 4kqX84nPC53bjN7wk7jDzeJ9fg1llYd1vwpVv/YD2yFnLt7RJpC1JJ6ns g==; X-IronPort-AV: E=McAfee;i="6600,9927,10709"; a="437325147" X-IronPort-AV: E=Sophos;i="5.99,273,1677571200"; d="scan'208";a="437325147" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2023 15:04:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10709"; a="790199647" X-IronPort-AV: E=Sophos;i="5.99,273,1677571200"; d="scan'208";a="790199647" Received: from sorinaau-mobl1.ger.corp.intel.com (HELO box.shutemov.name) ([10.252.62.145]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2023 15:04:36 -0700 Received: by box.shutemov.name (Postfix, from userid 1000) id CAF4E10CBB1; Sun, 14 May 2023 01:04:33 +0300 (+03) From: "Kirill A. Shutemov" To: Borislav Petkov , Andy Lutomirski , Dave Hansen , Sean Christopherson , Andrew Morton , Joerg Roedel , Ard Biesheuvel Cc: Andi Kleen , Kuppuswamy Sathyanarayanan , David Rientjes , Vlastimil Babka , Tom Lendacky , Thomas Gleixner , Peter Zijlstra , Paolo Bonzini , Ingo Molnar , Dario Faggioli , Mike Rapoport , David Hildenbrand , Mel Gorman , marcelo.cerri@canonical.com, tim.gardner@canonical.com, khalid.elmously@canonical.com, philip.cox@canonical.com, aarcange@redhat.com, peterx@redhat.com, x86@kernel.org, linux-mm@kvack.org, linux-coco@lists.linux.dev, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, "Kirill A. Shutemov" Subject: [PATCHv11 0/9] mm, x86/cc, efi: Implement support for unaccepted memory Date: Sun, 14 May 2023 01:04:09 +0300 Message-Id: <20230513220418.19357-1-kirill.shutemov@linux.intel.com> X-Mailer: git-send-email 2.39.3 MIME-Version: 1.0 X-Stat-Signature: 3hxf4aqacc8pd87p4a9q5h1w6x8r84qg X-Rspam-User: X-Rspamd-Queue-Id: F12B740006 X-Rspamd-Server: rspam07 X-HE-Tag: 1684015485-521371 X-HE-Meta: U2FsdGVkX1+ZqW9/Fc1l3dR/1ES6Xvof4phpL1HKBuSz3a+lQspXMUoPAScxHui9K1bdawPq3WaFW8You2TsYqWkhaD3K4pJMeREFkYav4beNcyjuQdKRKHlFAKIl7SLIeZIa4vJDFAtLEZAt3rLi4E2tOcmdsAiOJBYNgZJujkRdJzyC0XjXUvNEAzlauVebpIpVmY0dTa/WBgO+SeiM3ee3azErr5Zx6xNcqDm/27VWgxkazDzAdGojFV/uPL7NhW/RFzKHKYeRZ0S/8Js2YCKUuzbnntYr93TlwTTLgKyZ++z4nKqGoyFPjp0dHTHgBhG0DAYGex1gFGCQNJx+G68lfGejSUwXwq0GtU4bFaAtzi1miv7GiT55ty7JdxQ6xBWl13qe/+eA7nY9CvENHtTY/IzFXjFvKMCRzJpI5f//p7SF1U0vo7Db0lfE5SrPkKQfTKpwUUxPEBStlZsL5uARdm7vW70La9mvta7cTg4/tGZJzWIbbwiPKASKHpxaVA2fyJ5ve3kE1RYLmU3HE9WF5JAXIQqGtHDRCU7yRFMfhXi59HShnHu23OP/X2fzYh0VWd3iviPHCHakIBjq+T1O8aY3dCi5+mvloPDkwBfD6leR17BptdyGaB0uaFyY/lqMKnBq4IgdkrcmeWCJWwyIOBX7ipndpdG7xSl8Fp8lKa6e8nw5d25cNYGoGwxIEcgrwCWCMZtu8kJV9TWlYkXCkZ1GFMEeXKjEOVPeisCCHut4y3LA62qRfxcrCMOfbhu17+aj3WiCYRQYgk0zu87drdQGYcYl2Zc613il/glcMs8f8K99EszMTMQTlP2QFOmX5b/aBsQDCjqhd1pSqfPMb5wFXjcEHwHCXV7V0GltdaD8dUdr5j9Rj5x/9WBzKmFL2XbjOYtRgPwArsFqkA7PWPLq7Ke/nVynxzy5u+tMd3eMMKbbKt75tM54tyZSPE9KmlpPjybKF6SVNl AMUZMRxX 6uj07bnhNRk5WtO8aQNf5iKMnvCWpnllOongChev5lJaMnL9lrpcQLuhxEnlDd3iuu3Wvh+PqfARg9YpoJZ9eTWybGpLUh9eWSfh/Q1Lk7F+Kn/TX7WPS72pzOSlLlul8MHkZAq02rzONDycbDSb7+YD/OIxnAkK9H2q8fiv1QqPom90rT5nUuSg3YUjzovz2i8cyvbs7Y22CKY9ON2Vye914tG8+oh46oYSv 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: UEFI Specification version 2.9 introduces the concept of memory acceptance: some Virtual Machine platforms, such as Intel TDX or AMD SEV-SNP, requiring memory to be accepted before it can be used by the guest. Accepting happens via a protocol specific for the Virtual Machine platform. Accepting memory is costly and it makes VMM allocate memory for the accepted guest physical address range. It's better to postpone memory acceptance until memory is needed. It lowers boot time and reduces memory overhead. The kernel needs to know what memory has been accepted. Firmware communicates this information via memory map: a new memory type -- EFI_UNACCEPTED_MEMORY -- indicates such memory. Range-based tracking works fine for firmware, but it gets bulky for the kernel: e820 has to be modified on every page acceptance. It leads to table fragmentation, but there's a limited number of entries in the e820 table Another option is to mark such memory as usable in e820 and track if the range has been accepted in a bitmap. One bit in the bitmap represents 2MiB in the address space: one 4k page is enough to track 64GiB or physical address space. In the worst-case scenario -- a huge hole in the middle of the address space -- It needs 256MiB to handle 4PiB of the address space. Any unaccepted memory that is not aligned to 2M gets accepted upfront. The approach lowers boot time substantially. Boot to shell is ~2.5x faster for 4G TDX VM and ~4x faster for 64G. TDX-specific code isolated from the core of unaccepted memory support. It supposed to help to plug-in different implementation of unaccepted memory such as SEV-SNP. -- Fragmentation study -- Vlastimil and Mel were concern about effect of unaccepted memory on fragmentation prevention measures in page allocator. I tried to evaluate it, but it is tricky. As suggested I tried to run multiple parallel kernel builds and follow how often kmem:mm_page_alloc_extfrag gets hit. See results in the v9 of the patchset[1][2] [1] https://lore.kernel.org/all/20230330114956.20342-1-kirill.shutemov@linux.intel.com [2] https://lore.kernel.org/all/20230416191940.ex7ao43pmrjhru2p@box.shutemov.name --- The tree can be found here: https://github.com/intel/tdx.git guest-unaccepted-memory The patchset depends on MAX_ORDER changes in MM tree. v11: - Restructure the code to make it less x86-specific (suggested by Ard): + use EFI configuration table instead of zero-page to pass down bitmap; + do not imply 1bit == 2M in bitmap; + move bulk of the code under driver/firmware/efi; - The bitmap only covers unaccpeted memory now. All memory that is not covered by the bitmap assumed accepted; - Reviewed-by from Ard; v10: - Restructure code around zones_with_unaccepted_pages static brach to avoid unnecessary function calls (Suggested by Vlastimil); - Drop mentions of PageUnaccepted(); - Drop patches that add fake unaccepted memory support and sysfs handle to accept memory manually; - Add Reviewed-by from Vlastimil; v9: - Accept memory up to high watermark when kernel runs out of free memory; - Treat unaccepted memory as unusable in __zone_watermark_unusable_free(); - Per-zone unaccepted memory accounting; - All pages on unaccepted list are MAX_ORDER now; - accept_memory=eager in cmdline to pre-accept memory during the boot; - Implement fake unaccepted memory; - Sysfs handle to accept memory manually; - Drop PageUnaccepted(); - Rename unaccepted_pages static key to zones_with_unaccepted_pages; v8: - Rewrite core-mm support for unaccepted memory (patch 02/14); - s/UnacceptedPages/Unaccepted/ in meminfo; - Drop arch/x86/boot/compressed/compiler.h; - Fix build errors; - Adjust commit messages and comments; - Reviewed-bys from Dave and Borislav; - Rebased to tip/master. v7: - Rework meminfo counter to use PageUnaccepted() and move to generic code; - Fix range_contains_unaccepted_memory() on machines without unaccepted memory; - Add Reviewed-by from David; v6: - Fix load_unaligned_zeropad() on machine with unaccepted memory; - Clear PageUnaccepted() on merged pages, leaving it only on head; - Clarify error handling in allocate_e820(); - Fix build with CONFIG_UNACCEPTED_MEMORY=y, but without TDX; - Disable kexec at boottime instead of build conflict; - Rebased to tip/master; - Spelling fixes; - Add Reviewed-by from Mike and David; v5: - Updates comments and commit messages; + Explain options for unaccepted memory handling; - Expose amount of unaccepted memory in /proc/meminfo - Adjust check in page_expected_state(); - Fix error code handling in allocate_e820(); - Centralize __pa()/__va() definitions in the boot stub; - Avoid includes from the main kernel in the boot stub; - Use an existing hole in boot_param for unaccepted_memory, instead of adding to the end of the structure; - Extract allocate_unaccepted_memory() form allocate_e820(); - Complain if there's unaccepted memory, but kernel does not support it; - Fix vmstat counter; - Split up few preparatory patches; - Random readability adjustments; v4: - PageBuddyUnaccepted() -> PageUnaccepted; - Use separate page_type, not shared with offline; - Rework interface between core-mm and arch code; - Adjust commit messages; - Ack from Mike; Kirill A. Shutemov (9): mm: Add support for unaccepted memory efi/x86: Get full memory map in allocate_e820() efi/libstub: Implement support for unaccepted memory x86/boot/compressed: Handle unaccepted memory efi: Provide helpers for unaccepted memory efi/unaccepted: Avoid load_unaligned_zeropad() stepping into unaccepted memory x86/tdx: Make _tdx_hypercall() and __tdx_module_call() available in boot stub x86/tdx: Refactor try_accept_one() x86/tdx: Add unaccepted memory support arch/x86/Kconfig | 2 + arch/x86/boot/compressed/Makefile | 1 + arch/x86/boot/compressed/efi.h | 1 + arch/x86/boot/compressed/error.c | 19 ++ arch/x86/boot/compressed/error.h | 1 + arch/x86/boot/compressed/kaslr.c | 35 ++- arch/x86/boot/compressed/mem.c | 42 ++++ arch/x86/boot/compressed/misc.c | 6 + arch/x86/boot/compressed/misc.h | 6 + arch/x86/boot/compressed/tdx-shared.c | 2 + arch/x86/boot/compressed/tdx.c | 37 +++ arch/x86/coco/tdx/Makefile | 2 +- arch/x86/coco/tdx/tdx-shared.c | 95 ++++++++ arch/x86/coco/tdx/tdx.c | 118 +--------- arch/x86/include/asm/efi.h | 2 + arch/x86/include/asm/shared/tdx.h | 53 +++++ arch/x86/include/asm/tdx.h | 21 +- arch/x86/include/asm/unaccepted_memory.h | 23 ++ drivers/base/node.c | 7 + drivers/firmware/efi/Kconfig | 14 ++ drivers/firmware/efi/Makefile | 1 + drivers/firmware/efi/efi.c | 7 + drivers/firmware/efi/libstub/Makefile | 2 + drivers/firmware/efi/libstub/bitmap.c | 41 ++++ drivers/firmware/efi/libstub/efistub.h | 6 + drivers/firmware/efi/libstub/find.c | 43 ++++ .../firmware/efi/libstub/unaccepted_memory.c | 222 ++++++++++++++++++ drivers/firmware/efi/libstub/x86-stub.c | 39 +-- drivers/firmware/efi/unaccepted_memory.c | 138 +++++++++++ fs/proc/meminfo.c | 5 + include/linux/efi.h | 13 +- include/linux/mm.h | 19 ++ include/linux/mmzone.h | 8 + mm/internal.h | 1 + mm/memblock.c | 9 + mm/mm_init.c | 7 + mm/page_alloc.c | 173 ++++++++++++++ mm/vmstat.c | 3 + 38 files changed, 1060 insertions(+), 164 deletions(-) create mode 100644 arch/x86/boot/compressed/mem.c create mode 100644 arch/x86/boot/compressed/tdx-shared.c create mode 100644 arch/x86/coco/tdx/tdx-shared.c create mode 100644 arch/x86/include/asm/unaccepted_memory.h create mode 100644 drivers/firmware/efi/libstub/bitmap.c create mode 100644 drivers/firmware/efi/libstub/find.c create mode 100644 drivers/firmware/efi/libstub/unaccepted_memory.c create mode 100644 drivers/firmware/efi/unaccepted_memory.c