From: Liu Shixin <liushixin2@huawei.com> To: Jonathan Corbet <corbet@lwn.net>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: <linux-doc@vger.kernel.org>, <linux-riscv@lists.infradead.org>, Liu Shixin <liushixin2@huawei.com>, Kefeng Wang <wangkefeng.wang@huawei.com> Subject: [PATCH 0/2] riscv: Support HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC Date: Thu, 15 Sep 2022 14:50:25 +0800 [thread overview] Message-ID: <20220915065027.3501044-1-liushixin2@huawei.com> (raw) Since riscv64 has already support SATP_MODE_57 by default, it is time to support more hugepage-related features. These two patches will enable HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC. Liu Shixin (2): riscv: Enable HAVE_ARCH_HUGE_VMAP for 64BIT riscv: Enable HAVE_ARCH_HUGE_VMALLOC for 64BIT .../features/vm/huge-vmap/arch-support.txt | 2 +- arch/riscv/Kconfig | 2 + arch/riscv/include/asm/vmalloc.h | 18 ++++ arch/riscv/mm/Makefile | 1 + arch/riscv/mm/pgtable.c | 83 +++++++++++++++++++ 5 files changed, 105 insertions(+), 1 deletion(-) create mode 100644 arch/riscv/mm/pgtable.c -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Liu Shixin <liushixin2@huawei.com> To: Jonathan Corbet <corbet@lwn.net>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: <linux-doc@vger.kernel.org>, <linux-riscv@lists.infradead.org>, Liu Shixin <liushixin2@huawei.com>, Kefeng Wang <wangkefeng.wang@huawei.com> Subject: [PATCH 0/2] riscv: Support HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC Date: Thu, 15 Sep 2022 14:50:25 +0800 [thread overview] Message-ID: <20220915065027.3501044-1-liushixin2@huawei.com> (raw) Since riscv64 has already support SATP_MODE_57 by default, it is time to support more hugepage-related features. These two patches will enable HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC. Liu Shixin (2): riscv: Enable HAVE_ARCH_HUGE_VMAP for 64BIT riscv: Enable HAVE_ARCH_HUGE_VMALLOC for 64BIT .../features/vm/huge-vmap/arch-support.txt | 2 +- arch/riscv/Kconfig | 2 + arch/riscv/include/asm/vmalloc.h | 18 ++++ arch/riscv/mm/Makefile | 1 + arch/riscv/mm/pgtable.c | 83 +++++++++++++++++++ 5 files changed, 105 insertions(+), 1 deletion(-) create mode 100644 arch/riscv/mm/pgtable.c -- 2.25.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-09-15 6:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-15 6:50 Liu Shixin [this message] 2022-09-15 6:50 ` [PATCH 0/2] riscv: Support HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC Liu Shixin 2022-09-15 6:50 ` [PATCH 1/2] riscv: Enable HAVE_ARCH_HUGE_VMAP for 64BIT Liu Shixin 2022-09-15 6:50 ` Liu Shixin 2022-09-15 6:50 ` [PATCH 2/2] riscv: Enable HAVE_ARCH_HUGE_VMALLOC " Liu Shixin 2022-09-15 6:50 ` Liu Shixin 2022-10-08 2:18 ` Kefeng Wang 2022-10-08 2:18 ` Kefeng Wang 2022-10-01 19:00 ` [PATCH 0/2] riscv: Support HAVE_ARCH_HUGE_VMAP and HAVE_ARCH_HUGE_VMALLOC Conor Dooley 2022-10-01 19:00 ` Conor Dooley
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220915065027.3501044-1-liushixin2@huawei.com \ --to=liushixin2@huawei.com \ --cc=aou@eecs.berkeley.edu \ --cc=corbet@lwn.net \ --cc=linux-doc@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=wangkefeng.wang@huawei.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.