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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 106F3C433EF for ; Fri, 18 Feb 2022 10:46:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233350AbiBRKq3 (ORCPT ); Fri, 18 Feb 2022 05:46:29 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:35370 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230315AbiBRKq3 (ORCPT ); Fri, 18 Feb 2022 05:46:29 -0500 Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0434A25AE56 for ; Fri, 18 Feb 2022 02:46:13 -0800 (PST) Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id B286C3F32C for ; Fri, 18 Feb 2022 10:46:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1645181171; bh=dGDRz61XRlmN2nrsI5bz0i1S0S+h5+fQGdDwmq0wB0k=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=s1N7881ofX1d93IOgsQ9T2rUSkVlXMJCRrUtvZM+/JAjkOdTK3ljkfaftjaS0qAIQ V1otuDOuNzlg9xgVSBVjzy/MtXP05jjCwFDUTyF8kdw1DMV3Gx7ErshZE3t3J6VyoG AteB3iAdCVf2leEkHZxB/98gWLxGV0bHnpg4gRM1+fF0f1uiodpoScdDcFFvqPA9C5 z+Tb9fchUdiPeaR6gqaRv2k7gCLUioJUCH5Z5s+BGRvnI/Oa/3dF92dR+uyZaSoGfJ jnV00glj9A2Ikc14OSvuHFnDMV1grEbkQJnMI6QQQ5JrbIIbx9pF2ki7SAVmG61uxM ANPswlTbriqNw== Received: by mail-wr1-f69.google.com with SMTP id p18-20020adfba92000000b001e8f7697cc7so1371509wrg.20 for ; Fri, 18 Feb 2022 02:46:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dGDRz61XRlmN2nrsI5bz0i1S0S+h5+fQGdDwmq0wB0k=; b=CiQOvhJua2qTm5/me1REwYnNKB9ExGEMJu8PcTxVctsRm52Q7xSzLBtl5pWGEppgCC Tph6xsF2WQ/8rbmklSzttJW44C3gocOstyRLlYufl3twtfsY54BA4EZh6mgrRV1dgxQj ogANqOMKCOrYblC0L4Bc994ecVxFsvLb7xwwlaPQgQW6P8+iNpl9f29EwLciLDGNAzbm g1oTrmhmiJ94vRU60gGoWDjJv/YrvYCgO6z+bwzm9yr/9MLiL7lEBHzjUonzcVxBkgxl fjHn2ZpRume8YjCOS2+ocXangAaDRRORyigJ6y/Zo6+TA6ruhopMDGSvPK8U1xJDIMZk X+sg== X-Gm-Message-State: AOAM530zDO1zIKzgTd9QE6LtzcURFv2stHKz8sJ/MGE0sKlk0fLB3g6a ND3T9Zs4AXras71+oWpxBiciHIaI5YC1lE3bztEGOm6RgtJ2roPGlJXhMVizMciB0QGF6ByUlfE XN7tGMqBOuvxO1xyCdpR3DRSGSHhvjb/OOd1kMiqGflHJo5ScMaAhuiU= X-Received: by 2002:aa7:d3d9:0:b0:410:7a81:c0cf with SMTP id o25-20020aa7d3d9000000b004107a81c0cfmr7414114edr.177.1645181160596; Fri, 18 Feb 2022 02:46:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJxQ+NAme7XzeWAZqBbGMYs1sQLjBbN9OgKux5J4SQWKa0WWJPX7Ydz76FgBA28E+tI3LAqAq09x/bebpkHqaFo= X-Received: by 2002:aa7:d3d9:0:b0:410:7a81:c0cf with SMTP id o25-20020aa7d3d9000000b004107a81c0cfmr7414090edr.177.1645181160350; Fri, 18 Feb 2022 02:46:00 -0800 (PST) MIME-Version: 1.0 References: <20211206104657.433304-1-alexandre.ghiti@canonical.com> In-Reply-To: From: Alexandre Ghiti Date: Fri, 18 Feb 2022 11:45:49 +0100 Message-ID: Subject: Re: [PATCH v3 00/13] Introduce sv48 support without relocatable kernel To: Palmer Dabbelt Cc: corbet@lwn.net, Paul Walmsley , aou@eecs.berkeley.edu, zong.li@sifive.com, anup@brainfault.org, Atish.Patra@rivosinc.com, Christoph Hellwig , ryabinin.a.a@gmail.com, glider@google.com, andreyknvl@gmail.com, dvyukov@google.com, ardb@kernel.org, Arnd Bergmann , keescook@chromium.org, guoren@linux.alibaba.com, heinrich.schuchardt@canonical.com, mchitale@ventanamicro.com, panqinglin2020@iscas.ac.cn, linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-efi@vger.kernel.org, linux-arch@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org Hi Palmer, On Thu, Jan 20, 2022 at 11:05 AM Alexandre Ghiti wrote: > > On Thu, Jan 20, 2022 at 8:30 AM Alexandre Ghiti > wrote: > > > > On Thu, Jan 20, 2022 at 5:18 AM Palmer Dabbelt wrote: > > > > > > On Mon, 06 Dec 2021 02:46:44 PST (-0800), alexandre.ghiti@canonical.com wrote: > > > > * Please note notable changes in memory layouts and kasan population * > > > > > > > > This patchset allows to have a single kernel for sv39 and sv48 without > > > > being relocatable. > > > > > > > > The idea comes from Arnd Bergmann who suggested to do the same as x86, > > > > that is mapping the kernel to the end of the address space, which allows > > > > the kernel to be linked at the same address for both sv39 and sv48 and > > > > then does not require to be relocated at runtime. > > > > > > > > This implements sv48 support at runtime. The kernel will try to > > > > boot with 4-level page table and will fallback to 3-level if the HW does not > > > > support it. Folding the 4th level into a 3-level page table has almost no > > > > cost at runtime. > > > > > > > > Note that kasan region had to be moved to the end of the address space > > > > since its location must be known at compile-time and then be valid for > > > > both sv39 and sv48 (and sv57 that is coming). > > > > > > > > Tested on: > > > > - qemu rv64 sv39: OK > > > > - qemu rv64 sv48: OK > > > > - qemu rv64 sv39 + kasan: OK > > > > - qemu rv64 sv48 + kasan: OK > > > > - qemu rv32: OK > > > > > > > > Changes in v3: > > > > - Fix SZ_1T, thanks to Atish > > > > - Fix warning create_pud_mapping, thanks to Atish > > > > - Fix k210 nommu build, thanks to Atish > > > > - Fix wrong rebase as noted by Samuel > > > > - * Downgrade to sv39 is only possible if !KASAN (see commit changelog) * > > > > - * Move KASAN next to the kernel: virtual layouts changed and kasan population * > > > > > > > > Changes in v2: > > > > - Rebase onto for-next > > > > - Fix KASAN > > > > - Fix stack canary > > > > - Get completely rid of MAXPHYSMEM configs > > > > - Add documentation > > > > > > > > Alexandre Ghiti (13): > > > > riscv: Move KASAN mapping next to the kernel mapping > > > > riscv: Split early kasan mapping to prepare sv48 introduction > > > > riscv: Introduce functions to switch pt_ops > > > > riscv: Allow to dynamically define VA_BITS > > > > riscv: Get rid of MAXPHYSMEM configs > > > > asm-generic: Prepare for riscv use of pud_alloc_one and pud_free > > > > riscv: Implement sv48 support > > > > riscv: Use pgtable_l4_enabled to output mmu_type in cpuinfo > > > > riscv: Explicit comment about user virtual address space size > > > > riscv: Improve virtual kernel memory layout dump > > > > Documentation: riscv: Add sv48 description to VM layout > > > > riscv: Initialize thread pointer before calling C functions > > > > riscv: Allow user to downgrade to sv39 when hw supports sv48 if !KASAN > > > > > > > > Documentation/riscv/vm-layout.rst | 48 ++- > > > > arch/riscv/Kconfig | 37 +- > > > > arch/riscv/configs/nommu_k210_defconfig | 1 - > > > > .../riscv/configs/nommu_k210_sdcard_defconfig | 1 - > > > > arch/riscv/configs/nommu_virt_defconfig | 1 - > > > > arch/riscv/include/asm/csr.h | 3 +- > > > > arch/riscv/include/asm/fixmap.h | 1 > > > > arch/riscv/include/asm/kasan.h | 11 +- > > > > arch/riscv/include/asm/page.h | 20 +- > > > > arch/riscv/include/asm/pgalloc.h | 40 ++ > > > > arch/riscv/include/asm/pgtable-64.h | 108 ++++- > > > > arch/riscv/include/asm/pgtable.h | 47 +- > > > > arch/riscv/include/asm/sparsemem.h | 6 +- > > > > arch/riscv/kernel/cpu.c | 23 +- > > > > arch/riscv/kernel/head.S | 4 +- > > > > arch/riscv/mm/context.c | 4 +- > > > > arch/riscv/mm/init.c | 408 ++++++++++++++---- > > > > arch/riscv/mm/kasan_init.c | 250 ++++++++--- > > > > drivers/firmware/efi/libstub/efi-stub.c | 2 > > > > drivers/pci/controller/pci-xgene.c | 2 +- > > > > include/asm-generic/pgalloc.h | 24 +- > > > > include/linux/sizes.h | 1 > > > > 22 files changed, 833 insertions(+), 209 deletions(-) > > > > > > Sorry this took a while. This is on for-next, with a bit of juggling: a > > > handful of trivial fixes for configs that were failing to build/boot and > > > some merge issues. I also pulled out that MAXPHYSMEM fix to the top, so > > > it'd be easier to backport. This is bigger than something I'd normally like to > > > take late in the cycle, but given there's a lot of cleanups, likely some fixes, > > > and it looks like folks have been testing this I'm just going to go with it. > > > > > > > Yes yes yes! That's fantastic news :) > > > > > Let me know if there's any issues with the merge, it was a bit hairy. > > > Probably best to just send along a fixup patch at this point. > > > > I'm going to take a look at that now, and I'll fix anything that comes > > up quickly :) > > I see in for-next that you did not take the following patches: > > riscv: Improve virtual kernel memory layout dump > Documentation: riscv: Add sv48 description to VM layout > riscv: Initialize thread pointer before calling C functions > riscv: Allow user to downgrade to sv39 when hw supports sv48 if !KASAN > > I'm not sure this was your intention. If it was, I believe that at > least the first 2 patches are needed in this series, the 3rd one is a > useful fix and we can discuss the 4th if that's an issue for you. Can you confirm that this was intentional and maybe explain the motivation behind it? Because I see value in those patches. Thanks, Alex > > I tested for-next on both sv39 and sv48 successfully, I took a glance > at the code and noticed you fixed the PTRS_PER_PGD error, thanks for > that. Otherwise nothing obvious has popped. > > Thanks again, > > Alex > > > > > Thanks! > > > > Alex > > > > > > > > Thanks!