public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Only flush the mm icache when setting an exec pte
Date: Wed, 20 Mar 2024 20:50:39 +0000	[thread overview]
Message-ID: <171096783946.6804.8158757772819473697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240202124711.256146-1-alexghiti@rivosinc.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri,  2 Feb 2024 13:47:11 +0100 you wrote:
> We used to emit a flush_icache_all() whenever a dirty executable
> mapping is set in the page table but we can instead call
> flush_icache_mm() which will only send IPIs to cores that currently run
> this mm and add a deferred icache flush to the others.
> 
> The number of calls to sbi_remote_fence_i() (tested without IPI
> support):
> 
> [...]

Here is the summary with links:
  - riscv: Only flush the mm icache when setting an exec pte
    https://git.kernel.org/riscv/c/01261e24cfab

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-03-20 20:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 12:47 [PATCH] riscv: Only flush the mm icache when setting an exec pte Alexandre Ghiti
2024-02-05 23:09 ` Charlie Jenkins
2024-03-20 20:50 ` patchwork-bot+linux-riscv [this message]
     [not found] <tencent_7721F6B72F58AA6154DFBDFF@qq.com>
2024-06-25 11:45 ` Alexandre Ghiti
2024-06-26  3:58   ` guibing
2024-07-01  1:50     ` guibing
2024-07-16 12:51     ` Alexandre Ghiti
2024-07-16 14:30       ` guibing
2024-07-17  9:20         ` Alexandre Ghiti
2024-07-17 14:23           ` guibing
2024-07-17 15:49             ` Alexandre Ghiti
2024-07-19  3:48               ` guibing
     [not found]               ` <5399B2FEDB648567+f2ded489-10da-4ce5-86d4-4ca8fb8d62e4@nucleisys.com>
2024-07-30 14:07                 ` Alexandre Ghiti

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=171096783946.6804.8158757772819473697.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --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