Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2127037ybb; Sat, 21 Mar 2020 13:30:27 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsR8KK5Fo1CDO1NAmSa3A/rscQJyhxu875QZapF7RIKWRTHUB2o0nCEsSv/JPjB1NtQ9UYs X-Received: by 2002:a9d:12d:: with SMTP id 42mr85641otu.2.1584822627851; Sat, 21 Mar 2020 13:30:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584822627; cv=none; d=google.com; s=arc-20160816; b=wLLGfXHx5rnuemSIHRWtV3SSmPKKVmXMw2bFKZ1graH6NYstieKnieAX/Xni+DPCjb 6RMEChT+4QBzhOcWNcSBq+xIhZ244e8ANy0dtQM+e6ITdNzbvNYGHAFXbuDQOOzZ8k9Y 2TB2ttj3k/DF5btaBRoXBaQQnyoKjTV87iKrxn6A+wa+x3T+qMrkyUKUGFwXX9cozYeq 847rvtcXMPy2T1ciFCtgtSOtgbRfjUepAfWZrSl49oeP85wqDfdwsWgrBmfaSqXgIEPI yq1dwhfsUJReqaX+jbIq88PxHCMo6bJDp3PKo6EGHVWxrOXlhAOOE3WvxhEIEMu89ZGA oVxw== 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:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=WW5o1pyalG30ClbZhbAg09cR2QEbOm6+hw2Xj1q5juE=; b=FlfmB5KiH/uLjLeGcbQw3hq3/GZhQB5W6rIyQzriOc/H6V0A6zHsquoext+UqlvptB PgLhZSd9ozyl26dIqGzI5n47joKO6aL3I5q9iZLrcrcz9OQVha7WoS7k/A7MeQfMNATl PiQI0pJLf3JXIoP49/ygyoBFUmpoul5RSCH7KtnXZG7dww4gmAveU8iobwNyyZI6ziCS yxKUNPzGQJ0LxhucrDS+fEBS6FmHCctlTTXtWEAFluEMzRgigAkUzhJVEn2K2bJzZbI1 /dO0ULIMcbG3jZDfSF6xPDFg67uac7VqYaCv6o3ycK2ul/wCaudkBHKlArDFqsdJOlnl CugQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=SpUDhAO4; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i19si5311670otp.177.2020.03.21.13.30.15; Sat, 21 Mar 2020 13:30:27 -0700 (PDT) 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=@gmail.com header.s=20161025 header.b=SpUDhAO4; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727286AbgCUU3p (ORCPT + 99 others); Sat, 21 Mar 2020 16:29:45 -0400 Received: from mail-wr1-f67.google.com ([209.85.221.67]:38917 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726146AbgCUU3p (ORCPT ); Sat, 21 Mar 2020 16:29:45 -0400 Received: by mail-wr1-f67.google.com with SMTP id h6so11722636wrs.6; Sat, 21 Mar 2020 13:29:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=WW5o1pyalG30ClbZhbAg09cR2QEbOm6+hw2Xj1q5juE=; b=SpUDhAO437ic3C0tq3/Tm2fjBEKNXFMgbD97zHI26nWMPMva3avf8LRsYEbSwKFvVA jVIuDSCyPXIGmUeoubYEkLcyo0MzMX5hKi3P9RgaKeaGj1nFzQKApwZDEKpi8Xw0XsDx K5ulklbGNODz4BdnIzwl/l9Xcxx7w11jCUjKu787MYCYCcLdedKeVhwyR1BPAjJJBSeT UOdPX32Ng/Q+a+1H77RqBEYx1m0nxOvWg+bzWfvVNesEjSZ+0ktqhaeIB4sBG0OR8Vzx JTjiDhiCQd2OstSqMouc/YL99qzngA7K5fMB3IwAKw4tpiafzD1Y09f6oD8qz86EX1p7 t92w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=WW5o1pyalG30ClbZhbAg09cR2QEbOm6+hw2Xj1q5juE=; b=C1qZVJXksBHxs3Ybnzh+3qjW4a0Or9FSu8VGu2N6725zeFtmtOoe6mGBf93eEiWky8 rroWRlAVlYfyA0WevjBKHC5cj9VmDOYDtQgpf0wJiknHTHt9qpxVNO34vpaamb4aDUit 7EZW8ryQDV56zg09ej/U7pFZE2Le7cK5z1YF1A2NHdbh1l4LyNh9FK3o/QVzXlSfpdry VN8iA/lEYB6K/gCXnNkm/5ktU5BgIy3XAKHtnQuT6aDxR2EFUMLv2XiUWpQfQmD0Bxzr dYV+SPbsIXUQ5HrqPkNNHAJKBCGtZTMmr9CESXFsFsoODi0P4eHz90QZ+ByRrm5oeQTc cHaA== X-Gm-Message-State: ANhLgQ0W1C9fUeBRoM8gxGaZKKRZRrcGrvmxQEgttQEmAzUbMVxWEtch +0a3VhgNqZ0MJajj1fbGMB7OW57u0d6Nv7lza0c= X-Received: by 2002:adf:ed8a:: with SMTP id c10mr19934547wro.423.1584822582022; Sat, 21 Mar 2020 13:29:42 -0700 (PDT) MIME-Version: 1.0 References: <20200224193436.26860-1-atish.patra@wdc.com> In-Reply-To: From: David Abdurachmanov Date: Sat, 21 Mar 2020 22:29:06 +0200 Message-ID: Subject: Re: [PATCH] RISC-V: Move all address space definition macros to one place To: Palmer Dabbelt Cc: Atish Patra , "linux-kernel@vger.kernel.org List" , Albert Ou , nickhu@andestech.com, Bjorn Topel , Anup Patel , stable@vger.kernel.org, Mike Rapoport , Thomas Gleixner , Paul Walmsley , Greentime Hu , akpm@linux-foundation.org, linux-riscv Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 6, 2020 at 2:20 AM Palmer Dabbelt wr= ote: > > On Mon, 24 Feb 2020 11:34:36 PST (-0800), Atish Patra wrote: > > If both CONFIG_KASAN and CONFIG_SPARSEMEM_VMEMMAP are set, we get the > > following compilation error. > > > > --------------------------------------------------------------- > > ./arch/riscv/include/asm/pgtable-64.h: In function =E2=80=98pud_page=E2= =80=99: > > ./include/asm-generic/memory_model.h:54:29: error: =E2=80=98vmemmap=E2= =80=99 undeclared > > (first use in this function); did you mean =E2=80=98mem_map=E2=80=99? > > #define __pfn_to_page(pfn) (vmemmap + (pfn)) > > ^~~~~~~ > > ./include/asm-generic/memory_model.h:82:21: note: in expansion of > > macro =E2=80=98__pfn_to_page=E2=80=99 > > > > #define pfn_to_page __pfn_to_page > > ^~~~~~~~~~~~~ > > ./arch/riscv/include/asm/pgtable-64.h:70:9: note: in expansion of macro > > =E2=80=98pfn_to_page=E2=80=99 > > return pfn_to_page(pud_val(pud) >> _PAGE_PFN_SHIFT); > > --------------------------------------------------------------- > > > > Fix the compliation errors by moving all the address space definition > > macros before including pgtable-64.h. > > > > Cc: stable@vger.kernel.org > > Fixes: 8ad8b72721d0 (riscv: Add KASAN support) > > > > Signed-off-by: Atish Patra > > --- > > arch/riscv/include/asm/pgtable.h | 78 +++++++++++++++++--------------- > > 1 file changed, 41 insertions(+), 37 deletions(-) > > > > diff --git a/arch/riscv/include/asm/pgtable.h b/arch/riscv/include/asm/= pgtable.h > > index 453afb0a570a..4f6ee48a42e8 100644 > > --- a/arch/riscv/include/asm/pgtable.h > > +++ b/arch/riscv/include/asm/pgtable.h > > @@ -19,6 +19,47 @@ > > #include > > #include > > > > +#ifdef CONFIG_MMU > > + > > +#define VMALLOC_SIZE (KERN_VIRT_SIZE >> 1) > > +#define VMALLOC_END (PAGE_OFFSET - 1) > > +#define VMALLOC_START (PAGE_OFFSET - VMALLOC_SIZE) > > + > > +#define BPF_JIT_REGION_SIZE (SZ_128M) > > +#define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) > > +#define BPF_JIT_REGION_END (VMALLOC_END) > > + > > +/* > > + * Roughly size the vmemmap space to be large enough to fit enough > > + * struct pages to map half the virtual address space. Then > > + * position vmemmap directly below the VMALLOC region. > > + */ > > +#define VMEMMAP_SHIFT \ > > + (CONFIG_VA_BITS - PAGE_SHIFT - 1 + STRUCT_PAGE_MAX_SHIFT) > > +#define VMEMMAP_SIZE BIT(VMEMMAP_SHIFT) > > +#define VMEMMAP_END (VMALLOC_START - 1) > > +#define VMEMMAP_START (VMALLOC_START - VMEMMAP_SIZE) > > + > > +/* > > + * Define vmemmap for pfn_to_page & page_to_pfn calls. Needed if kerne= l > > + * is configured with CONFIG_SPARSEMEM_VMEMMAP enabled. > > + */ > > +#define vmemmap ((struct page *)VMEMMAP_START) > > + > > +#define PCI_IO_SIZE SZ_16M > > +#define PCI_IO_END VMEMMAP_START > > +#define PCI_IO_START (PCI_IO_END - PCI_IO_SIZE) > > + > > +#define FIXADDR_TOP PCI_IO_START > > +#ifdef CONFIG_64BIT > > +#define FIXADDR_SIZE PMD_SIZE > > +#else > > +#define FIXADDR_SIZE PGDIR_SIZE > > +#endif > > +#define FIXADDR_START (FIXADDR_TOP - FIXADDR_SIZE) > > + > > +#endif > > + > > #ifdef CONFIG_64BIT > > #include > > #else > > @@ -90,31 +131,6 @@ extern pgd_t swapper_pg_dir[]; > > #define __S110 PAGE_SHARED_EXEC > > #define __S111 PAGE_SHARED_EXEC > > > > -#define VMALLOC_SIZE (KERN_VIRT_SIZE >> 1) > > -#define VMALLOC_END (PAGE_OFFSET - 1) > > -#define VMALLOC_START (PAGE_OFFSET - VMALLOC_SIZE) > > - > > -#define BPF_JIT_REGION_SIZE (SZ_128M) > > -#define BPF_JIT_REGION_START (PAGE_OFFSET - BPF_JIT_REGION_SIZE) > > -#define BPF_JIT_REGION_END (VMALLOC_END) > > - > > -/* > > - * Roughly size the vmemmap space to be large enough to fit enough > > - * struct pages to map half the virtual address space. Then > > - * position vmemmap directly below the VMALLOC region. > > - */ > > -#define VMEMMAP_SHIFT \ > > - (CONFIG_VA_BITS - PAGE_SHIFT - 1 + STRUCT_PAGE_MAX_SHIFT) > > -#define VMEMMAP_SIZE BIT(VMEMMAP_SHIFT) > > -#define VMEMMAP_END (VMALLOC_START - 1) > > -#define VMEMMAP_START (VMALLOC_START - VMEMMAP_SIZE) > > - > > -/* > > - * Define vmemmap for pfn_to_page & page_to_pfn calls. Needed if kerne= l > > - * is configured with CONFIG_SPARSEMEM_VMEMMAP enabled. > > - */ > > -#define vmemmap ((struct page *)VMEMMAP_START) > > - > > static inline int pmd_present(pmd_t pmd) > > { > > return (pmd_val(pmd) & (_PAGE_PRESENT | _PAGE_PROT_NONE)); > > @@ -452,18 +468,6 @@ static inline int ptep_clear_flush_young(struct vm= _area_struct *vma, > > #define __pte_to_swp_entry(pte) ((swp_entry_t) { pte_val(pte) }) > > #define __swp_entry_to_pte(x) ((pte_t) { (x).val }) > > > > -#define PCI_IO_SIZE SZ_16M > > -#define PCI_IO_END VMEMMAP_START > > -#define PCI_IO_START (PCI_IO_END - PCI_IO_SIZE) > > - > > -#define FIXADDR_TOP PCI_IO_START > > -#ifdef CONFIG_64BIT > > -#define FIXADDR_SIZE PMD_SIZE > > -#else > > -#define FIXADDR_SIZE PGDIR_SIZE > > -#endif > > -#define FIXADDR_START (FIXADDR_TOP - FIXADDR_SIZE) > > - > > /* > > * Task size is 0x4000000000 for RV64 or 0x9fc00000 for RV32. > > * Note that PGDIR_SIZE must evenly divide TASK_SIZE. > > While this isn't technically a fix, I'm inclined to target it for the RCs= just > to avoid conflicts. I've put it on for-next now so the builders have som= e time > to chew on things, as I don't want to put in a non-fix too quickly. I hit the same issue in Fedora/RISCV while building kernel-5.6.0-0.rc6, and we don't have KASAN selected. We do have CONFIG_SPARSEMEM_VMEMMAP selected. I will try this patch tomorrow. > > Thanks!