From: patchwork-bot+linux-riscv@kernel.org
To: Dylan Jhong <dylan@andestech.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
liushixin2@huawei.com, x5710999x@gmail.com, bjorn@rivosinc.com,
abrestic@rivosinc.com, peterx@redhat.com, hanchuanhua@oppo.com,
apopple@nvidia.com, hca@linux.ibm.com, aou@eecs.berkeley.edu,
palmer@dabbelt.com, paul.walmsley@sifive.com,
tim609@andestech.com, peterlin@andestech.com,
ycliang@andestech.com, alexghiti@rivosinc.com
Subject: Re: [RESEND PATCH v2] RISC-V: mm: Support huge page in vmalloc_fault()
Date: Wed, 15 Mar 2023 02:20:18 +0000 [thread overview]
Message-ID: <167884681819.17018.8848137969847408206.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230310075021.3919290-1-dylan@andestech.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 10 Mar 2023 15:50:21 +0800 you wrote:
> Since RISC-V supports ioremap() with huge page (pud/pmd) mapping,
> However, vmalloc_fault() assumes that the vmalloc range is limited
> to pte mappings. To complete the vmalloc_fault() function by adding
> huge page support.
>
> Fixes: 310f541a027b ("riscv: Enable HAVE_ARCH_HUGE_VMAP for 64BIT")
> Signed-off-by: Dylan Jhong <dylan@andestech.com>
> Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>
> [...]
Here is the summary with links:
- [RESEND,v2] RISC-V: mm: Support huge page in vmalloc_fault()
https://git.kernel.org/riscv/c/47dd902aaee9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-15 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 7:50 [RESEND PATCH v2] RISC-V: mm: Support huge page in vmalloc_fault() Dylan Jhong
2023-03-15 2:15 ` Palmer Dabbelt
2023-03-15 2:20 ` patchwork-bot+linux-riscv [this message]
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=167884681819.17018.8848137969847408206.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=abrestic@rivosinc.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=apopple@nvidia.com \
--cc=bjorn@rivosinc.com \
--cc=dylan@andestech.com \
--cc=hanchuanhua@oppo.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liushixin2@huawei.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=peterx@redhat.com \
--cc=tim609@andestech.com \
--cc=x5710999x@gmail.com \
--cc=ycliang@andestech.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox