From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, bjorn@rivosinc.com,
guoren@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes] riscv: Implement flush_cache_vmap()
Date: Thu, 10 Aug 2023 19:50:22 +0000 [thread overview]
Message-ID: <169169702213.10459.2982861934492504882.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725132246.817726-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 25 Jul 2023 15:22:46 +0200 you wrote:
> The RISC-V kernel needs a sfence.vma after a page table modification: we
> used to rely on the vmalloc fault handling to emit an sfence.vma, but
> commit 7d3332be011e ("riscv: mm: Pre-allocate PGD entries for
> vmalloc/modules area") got rid of this path for 64-bit kernels, so now we
> need to explicitly emit a sfence.vma in flush_cache_vmap().
>
> Note that we don't need to implement flush_cache_vunmap() as the generic
> code should emit a flush tlb after unmapping a vmalloc region.
>
> [...]
Here is the summary with links:
- [-fixes] riscv: Implement flush_cache_vmap()
https://git.kernel.org/riscv/c/7e3811521dc3
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-08-10 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 13:22 [PATCH -fixes] riscv: Implement flush_cache_vmap() Alexandre Ghiti
2023-07-30 5:08 ` Guo Ren
2023-08-03 9:14 ` dylan
2023-08-03 9:24 ` Conor Dooley
2023-08-03 9:48 ` Alexandre Ghiti
2023-08-03 9:58 ` Alexandre Ghiti
2023-08-03 10:05 ` Conor Dooley
2023-08-04 7:48 ` Dylan Jhong
2023-08-08 11:23 ` Alexandre Ghiti
2023-08-08 23:55 ` Guo Ren
2023-08-10 16:00 ` Palmer Dabbelt
2023-08-10 16:22 ` Dylan Jhong
2023-08-10 19:39 ` Palmer Dabbelt
2023-08-08 23:47 ` Guo Ren
2023-08-10 19:50 ` 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=169169702213.10459.2982861934492504882.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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